# Tech Stack Detector: Wappalyzer & BuiltWith Alternative (`mercury_ops/tech-stack-detector`) Actor

Find the CMS, ecommerce platform, frameworks, analytics, CDN, payments and 7,600+ other technologies any website uses, in bulk, from one polite request per site. Or monitor sites and get only stack changes. Open-source (GPL-3.0) fingerprints. No login.

- **URL**: https://apify.com/mercury_ops/tech-stack-detector.md
- **Developed by:** [Mercury](https://apify.com/mercury_ops) (community)
- **Categories:** Developer tools, Lead generation, SEO tools
- **Security:** Limited permissions
- **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/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

## Tech Stack Detector: Wappalyzer & BuiltWith Alternative

**Find out what any website is built with: CMS, ecommerce platform, JavaScript framework, analytics and tag managers, CDN and hosting, payment providers, chat widgets and 7,600+ other technologies.** Bulk, fast, one polite request per site. Or schedule it and hear only when a site's stack changes.

### Why this one

- **7,600+ technology fingerprints** from the open-source Wappalyzer community datasets (see *Credits & licence*).
- **Cheap:** $1.50 per 1,000 sites, and unreachable sites aren't charged.
- **Stack-change monitor:** a daily or weekly schedule in *Changes only* mode tells you when a prospect moves from WooCommerce to Shopify, adds Klaviyo, or drops Google Analytics.
- **Handy summary columns** (`cms`, `ecommerce`, `framework`, `server`, `analytics`, `cdn`, `payment`) for spreadsheets and CRMs, plus the full list with versions, categories and how each one was detected.

### Use cases

- **Lead generation and sales intelligence:** filter a list of domains to those running Shopify, Magento, HubSpot, Intercom, etc.
- **Competitor research and market sizing:** what do the top sites in a niche use?
- **Agencies:** audit prospects' stacks before a pitch; spot outdated CMS versions.
- **AI agents:** call it through the Apify MCP server to answer "what is example.com built on?".

### Input

```json
{
  "startUrls": [{ "url": "https://www.allbirds.co.uk" }, { "url": "wordpress.org/news/" }],
  "mode": "all",
  "minConfidence": 50,
  "maxConcurrency": 5
}
```

### Output (one row per site)

```json
{
  "inputUrl": "https://www.allbirds.co.uk",
  "url": "https://www.allbirds.co.uk/",
  "statusCode": 200,
  "title": "Allbirds UK | Sustainable Shoes & Clothing",
  "cms": "Shopify",
  "ecommerce": "Shopify",
  "framework": null,
  "server": null,
  "analytics": null,
  "tagManager": ["Google Tag Manager"],
  "cdn": ["Cloudflare"],
  "payment": ["Apple Pay"],
  "technologyNames": ["Cloudflare", "Shopify", "Swiper", "HTTP/3", "Open Graph", "Apple Pay", "Priority Hints", "HSTS", "Google Tag Manager"],
  "technologies": [
    { "name": "Shopify", "version": null, "categories": ["Ecommerce", "CMS"], "confidence": 100, "detectedVia": ["cookies", "dom"], "website": "https://shopify.com" }
  ],
  "error": null,
  "checkedAt": "2026-10-26T18:45:00+00:00"
}
```

In *Changes only* mode rows also carry `added` and `removed` lists.

### How it works and what it respects

- Fetches **one public page per site** (the URL you give) and reads its response headers, cookie names, HTML, script URLs, meta tags and simple DOM patterns. No login, no form submission, no personal data collected.
- **Obeys robots.txt** and identifies itself honestly in its user agent. Pages disallowed for it are reported, not fetched.

### Limits (honest)

- **No JavaScript execution.** Technologies only detectable inside a running browser (some JS-variable or rendered-DOM fingerprints) can be missed, so results are a floor, not a ceiling. Server-side and HTML-visible tech (CMS, ecommerce, CDN, analytics tags, most frameworks) is detected well.
- Only the page you give is analysed: a blog or shop on a subdomain needs its own URL.
- Sites behind aggressive bot protection may return a challenge page (you'll see e.g. `HTTP 403` in `error` and few detections). Enable a proxy for those.
- Confidence-based fingerprints can occasionally misfire; raise `minConfidence` to be stricter.

### Pricing (pay per event)

- **Site analysed** (Detect mode): $0.0015 per site, i.e. **$1.50 per 1,000 sites**. Unreachable sites are free.
- **Site checked** (Changes only): $0.0005 per site.
- **Stack change** (Changes only): $0.003 per site whose stack changed.

### Credits & licence

Technology fingerprints come from [projectdiscovery/wappalyzergo](https://github.com/projectdiscovery/wappalyzergo)'s merged dataset, which is derived from [enthec/webappanalyzer](https://github.com/enthec/webappanalyzer) and [HTTPArchive/wappalyzer](https://github.com/HTTPArchive/wappalyzer), both licensed **GPL-3.0**. Accordingly this Actor's source code and data are released under the **GPL-3.0** licence (see `LICENSE`). Not affiliated with Wappalyzer or BuiltWith.

# Actor input Schema

## `startUrls` (type: `array`):

Homepages or any page URLs, one per line (up to 5,000). Each URL is fetched once.

## `mode` (type: `string`):

'Detect' outputs every site's stack (one billable row per site analysed). 'Changes only' compares each site's stack with the previous run of the same monitor and outputs only sites where technologies were added or removed; the first run saves a baseline.

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

Hide detections below this confidence. Most fingerprints are 100%; some weak signals are 25-50%.

## `maxConcurrency` (type: `integer`):

How many different sites to fetch at once (each site still gets just one page request).

## `monitorName` (type: `string`):

Changes only: snapshots are kept per monitor name in a key-value store named 'tech-stack-detector-state' in your account.

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

Optional. Enable if some sites block datacenter traffic.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.allbirds.co.uk"
    },
    {
      "url": "https://wordpress.org/news/"
    }
  ],
  "mode": "all",
  "minConfidence": 50,
  "maxConcurrency": 5,
  "monitorName": "default",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `sites` (type: `string`):

No description

## `changes` (type: `string`):

No description

## `full` (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 = {
    "startUrls": [
        {
            "url": "https://www.allbirds.co.uk"
        },
        {
            "url": "https://wordpress.org/news/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mercury_ops/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 = { "startUrls": [
        { "url": "https://www.allbirds.co.uk" },
        { "url": "https://wordpress.org/news/" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("mercury_ops/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 '{
  "startUrls": [
    {
      "url": "https://www.allbirds.co.uk"
    },
    {
      "url": "https://wordpress.org/news/"
    }
  ]
}' |
apify call mercury_ops/tech-stack-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mercury_ops/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/sOymT8h3JauMC82qs/builds/BLcMKOi3XlvkeMWWE/openapi.json