# SaaS Subprocessor, AI Vendor & Backend Tech-Stack Radar (`signalcrafthq/saas-subprocessor-backend-tech-radar`) Actor

Discover public GDPR subprocessor pages and Trust Centers across B2B company domains to extract backend AI/LLM, cloud, data warehouse, CRM, billing, observability, and security vendors invisible to client-side script scanners.

- **URL**: https://apify.com/signalcrafthq/saas-subprocessor-backend-tech-radar.md
- **Developed by:** [YOUNSEOK Jang](https://apify.com/signalcrafthq) (community)
- **Categories:** Lead generation, AI, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 80.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $30.00 / 1,000 verified backend subprocessor stacks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does SaaS Subprocessor, AI Vendor & Backend Tech-Stack Radar do?

Traditional technographic tools (BuiltWith, Wappalyzer) only see browser-side JavaScript tags — leaving **90% of high-ticket B2B infrastructure** (`Snowflake`, `Databricks`, `OpenAI`, `Anthropic`, `AWS`, `GCP`, `Datadog`, `Salesforce`, `Okta`, `Stripe`, `Twilio`, `Pinecone`) completely invisible.

Under **GDPR Article 28**, B2B companies are legally required to publish a **Subprocessor List** disclosing the exact backend cloud, AI, data, support, and billing vendors processing customer data. **SaaS Subprocessor, AI Vendor & Backend Tech-Stack Radar** automatically discovers these public disclosures across any list of company domains, extracts **80+ verified backend vendors**, parses HTML vendor purpose/location tables, detects Trust Center platforms (`Vanta`, `Drata`, `SafeBase`, `Conveyor`), and tracks **newly added or removed subprocessors** across scheduled runs with **zero external API keys**.

***

### Key capabilities for Enterprise Sales, Clay & Competitive Intel

- **Multi-Tier Subprocessor & Trust Center Auto-Discovery:** Probes canonical paths (`/subprocessors`, `/legal/subprocessors`, `/security/subprocessors`, `/privacy/subprocessors`, `/legal/sub-processors`), crawls `/privacy` & `/security` footer links, checks `trust.<domain>`, and inspects `sitemap.xml` to maximize resolution rates.
- **80+ Backend Cloud, AI, Data & Enterprise SaaS Signatures:** Fingerprints **AI/LLM** (`OpenAI`, `Anthropic`, `Google Vertex AI`, `Cohere`, `Pinecone`, `Weaviate`), **Cloud & Data** (`AWS`, `Google Cloud`, `Microsoft Azure`, `Cloudflare`, `Snowflake`, `Databricks`, `BigQuery`, `MongoDB`, `ClickHouse`, `Supabase`), **Observability** (`Datadog`, `Sentry`, `New Relic`, `Grafana`, `Splunk`, `PagerDuty`), **GTM & Support** (`Salesforce`, `HubSpot`, `Marketo`, `Gong`, `Zendesk`, `Intercom`), **Billing** (`Stripe`, `Chargebee`, `Zuora`), and **Identity/GRC** (`Okta`, `Auth0`, `WorkOS`, `Vanta`, `Drata`, `SafeBase`, `Wiz`, `CrowdStrike`).
- **Structured Table Parsing (`structuredTableRows`):** Extracts vendor entity names, processing purposes, and hosting jurisdictions straight out of HTML `<table>` disclosures.
- **Weekly Vendor-Change Diffing (`trackVendorChanges` + `watchId`):** Alerts your Clay table, Slack channel, or n8n workflow the week a prospect or competitor adds **OpenAI**, **Anthropic**, **Snowflake**, or drops an incumbent vendor.
- **GDPR-Safe Corporate Contacts:** Extracts functional compliance, security, and commercial role addresses (`security@`, `privacy@`, `dpo@`, `legal@`, `sales@`) while strictly blocking personal employee emails.

***

### Pay-Per-Event (PPE) outcome-based pricing

| Event Name | When It Is Charged | Value Delivered |
| :--- | :--- | :--- |
| `apify-actor-start` | Once per Actor run | Startup initialization and first 5 seconds of compute. |
| `subprocessor-stack-resolved` | **Only when `subprocessorResolved: true`** | Verified subprocessor URL + backend AI/cloud/data vendor stack + parsed table rows + Trust Center & role emails. |
| `domain-probed` | When a domain has no public subprocessor page (`onlyResolvedStacks: false`) | Domain probe telemetry, Trust Center check, compliance mentions, and public role contacts. |

***

### Input configuration example

```json
{
  "domains": [
    "klaviyo.com",
    "retool.com",
    "posthog.com",
    "vercel.com"
  ],
  "targetVendors": [],
  "onlyResolvedStacks": false,
  "trackVendorChanges": true,
  "watchId": "enterprise-ai-subprocessors"
}
```

***

### Responsible data collection & compliance

- **Public Legal Disclosures Only:** Accesses unauthenticated `/subprocessors`, `/legal`, `/privacy`, and `/security` pages published specifically for public transparency, respecting `robots.txt` directives.
- **Strict Role-Inbox Filtering:** Emits only organizational role addresses (`privacy@`, `security@`, `dpo@`, `legal@`, `sales@`, `support@`) and blocks natural-person PII.

# Actor input Schema

## `domains` (type: `array`):

Company domains (e.g., klaviyo.com, retool.com, datadoghq.com, twilio.com), company names, or direct /subprocessors URLs.

## `targetVendors` (type: `array`):

Optional list of vendor names to hunt for (e.g., OpenAI, Anthropic, Snowflake, Databricks, Datadog, Zendesk, Intercom, Stripe, Okta). Leave empty to return all resolved vendor stacks.

## `onlyResolvedStacks` (type: `boolean`):

When enabled, skips domains where no public subprocessor disclosure or target vendor match was found.

## `trackVendorChanges` (type: `boolean`):

Persist each company's detected subprocessor vendor list in a Key-Value Store to highlight newlyAddedVendors and removedVendors on scheduled runs.

## `onlyChangedStacks` (type: `boolean`):

On scheduled runs after baseline initialization, emit only accounts whose subprocessor vendor list changed.

## `watchId` (type: `string`):

Identifier isolating historical vendor snapshots across separate scheduled tasks.

## `webhookUrl` (type: `string`):

Optional HTTPS webhook endpoint (Clay, n8n, Make, Slack) for backend tech-stack intelligence.

## `proxyConfiguration` (type: `object`):

Optional Apify Proxy configuration. Direct HTTP works out-of-the-box for standard legal & trust pages.

## Actor input object example

```json
{
  "domains": [
    "klaviyo.com",
    "retool.com",
    "datadoghq.com",
    "cloudflare.com"
  ],
  "targetVendors": [],
  "onlyResolvedStacks": false,
  "trackVendorChanges": true,
  "onlyChangedStacks": false,
  "watchId": "default",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Structured B2B account intelligence linking corporate domains to GDPR-disclosed AI, cloud, data, CRM, billing, and security vendors.

## `runSummary` (type: `string`):

JSON summary of domains probed, subprocessor pages resolved, top backend vendors, and PPE event counts.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "klaviyo.com",
        "retool.com",
        "datadoghq.com",
        "cloudflare.com"
    ],
    "targetVendors": [],
    "onlyResolvedStacks": false,
    "trackVendorChanges": true,
    "onlyChangedStacks": false,
    "watchId": "default"
};

// Run the Actor and wait for it to finish
const run = await client.actor("signalcrafthq/saas-subprocessor-backend-tech-radar").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "domains": [
        "klaviyo.com",
        "retool.com",
        "datadoghq.com",
        "cloudflare.com",
    ],
    "targetVendors": [],
    "onlyResolvedStacks": False,
    "trackVendorChanges": True,
    "onlyChangedStacks": False,
    "watchId": "default",
}

# Run the Actor and wait for it to finish
run = client.actor("signalcrafthq/saas-subprocessor-backend-tech-radar").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "klaviyo.com",
    "retool.com",
    "datadoghq.com",
    "cloudflare.com"
  ],
  "targetVendors": [],
  "onlyResolvedStacks": false,
  "trackVendorChanges": true,
  "onlyChangedStacks": false,
  "watchId": "default"
}' |
apify call signalcrafthq/saas-subprocessor-backend-tech-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,signalcrafthq/saas-subprocessor-backend-tech-radar"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/qqsnrU3KNlTkhT9d4/builds/cYYuyipzjgFCTqYa0/openapi.json
