# 🔍 Tech Stack Detector - CMS, Ecommerce, Analytics & Ad Tech (`that_red_bird/tech-stack-detector`) Actor

⚡ Fingerprint what technology any website runs from a 120+ technology signature library: CMS, ecommerce platform, analytics, ad tech, CDN, payment, hosting, JS frameworks and marketing automation.

- **URL**: https://apify.com/that\_red\_bird/tech-stack-detector.md
- **Developed by:** [mohamed alaya](https://apify.com/that_red_bird) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Tech Stack Detector

Fingerprint what technology a website actually runs — CMS, ecommerce platform, analytics,
ad tech, CDN, payment provider, hosting, JS framework and marketing automation — with a
confidence score and the exact evidence that fired for every detection.

This is the tool behind "find me sites running Shopify + Klaviyo" or "which of our leads
are still on WordPress" — sales prospecting and competitive research where you need real
signal on hundreds of domains, not a manual "view source" per site.

### How detection works

The moat is the signature library in `src/signatures.js` — **148 technologies**, each with
several **independent** detection rules drawn from six kinds of evidence:

| Rule kind | What it checks |
|---|---|
| `header` | Response headers set by the platform itself (`cf-ray`, `x-shopid`, `x-powered-by`) |
| `cookie` | Cookie names the platform sets (`_shopify_s`, `__hstc`, `ak_bmsc`) |
| `script` | `<script src>` / `<link href>` URLs naming the vendor's own CDN |
| `meta` | `<meta name="generator">` and other named meta tags |
| `dom` | Class/id/data-attribute naming conventions in the markup |
| `global` | Inline (non-src) `<script>` text — JS globals and config objects |

A technology is reported only if at least one rule fires. Confidence is **not** a raw count
of matches — it's a noisy-OR combination of each matched rule's weight (`meta`/`global`
strongest, `dom` weakest alone), so five independent weak signals compound toward certainty
while a single strong signal still reports honestly on its own, and confidence visibly rises
as more independent rules agree. Version hints are extracted from capture groups where the
signature exposes one (e.g. `meta generator: WordPress 6.4.2`, jQuery's own filename).

### What it does per run

For each site: fetches the homepage (redirects followed, failures reported per-site rather
than crashing the run), optionally fetches one more page of the *same* site for extra
coverage (a discovered product/shop/pricing link, or a fixed path you specify), runs the
full signature library against the combined signals, and outputs technologies grouped by
category with confidence + evidence, plus a flat name list for filtering (`flatTechList`).

Because it only ever reads the target's own public pages — the same thing a browser does —
there's nothing on the other end trying to block it.

### Input

`websites` (required) — URLs or bare domains. `fetchSecondaryPage` (default on) — check a
second page too. `secondaryPagePath` — force which page. `minConfidence` (default 20) — drop
low-confidence noise. `concurrency`, `proxyConfiguration` — standard run tuning.

### Output

One dataset row per site: `technologies` (full detail with confidence/version/evidence),
`categories` (grouped), `flatTechList` (names only, for `contains` filtering), plus
`secondaryUrlChecked`. Unreachable or errored sites get `{ type: "error", url, error }`
instead of stopping the run.

### Honest limitations

- **Client-rendered stacks can hide.** A JS-framework SPA that builds its entire DOM (and
  injects its own script tags) after hydration may under-report if the initial HTML response
  is nearly empty. Server-rendered and static-generated sites fingerprint far more reliably.
- **Version detection is best-effort.** Only signatures with an explicit capture group
  (generator tags, versioned filenames) report a version; most report presence only.
- **Confidence is evidence-based, not certainty.** A single `dom` match (weight ~20) is a
  plausible lead, not proof — pair `minConfidence` with your own review for anything
  decision-critical (e.g. before a sales outreach claim).
- **Shared infrastructure looks like the vendor.** A site behind a reseller's Cloudflare or
  a WAF may report the WAF's CDN rather than the origin's true host.
- Detection quality depends on what the site's *first response* actually contains — a page
  that 403s a scraper UA, or requires JS execution to render anything, yields fewer or no
  detections rather than a false one.

# Actor input Schema

## `websites` (type: `array`):

URLs or bare domains to fingerprint. https:// is added automatically if missing, e.g. "shopify.com" or "https://www.allbirds.com".

## `fetchSecondaryPage` (type: `boolean`):

Fetch one more page per site (a discovered product/shop/pricing link, or secondaryPagePath if set) and combine its signals with the homepage's. Catches tech that only appears on inner pages, e.g. checkout payment providers.

## `secondaryPagePath` (type: `string`):

A specific path to use as the second page for every site, e.g. "/products" or "/pricing". Leave empty to auto-pick a same-origin link found on the homepage.

## `minConfidence` (type: `integer`):

Drop detections below this confidence score. Raise it to cut noisy single-rule guesses; lower it to see every weak hit.

## `concurrency` (type: `integer`):

How many sites to fingerprint in parallel.

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

Optional Apify proxy configuration, useful if a site's WAF blocks the platform's default IPs.

## Actor input object example

```json
{
  "websites": [
    "https://www.allbirds.com",
    "https://www.shopify.com"
  ],
  "fetchSecondaryPage": true,
  "minConfidence": 20,
  "concurrency": 5
}
```

# Actor output Schema

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

No description

## `downloadCsv` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `count` (type: `string`):

No description

# 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 = {
    "websites": [
        "https://www.allbirds.com",
        "https://www.shopify.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("that_red_bird/tech-stack-detector").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 = { "websites": [
        "https://www.allbirds.com",
        "https://www.shopify.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("that_red_bird/tech-stack-detector").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 '{
  "websites": [
    "https://www.allbirds.com",
    "https://www.shopify.com"
  ]
}' |
apify call that_red_bird/tech-stack-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,that_red_bird/tech-stack-detector"
        }
    }
}

```

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/uSAqcYO617S7xDb9o/builds/00PL5kissOuZbzhWW/openapi.json