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

Detect the technology stack of any list of websites: CMS, ecommerce platform, analytics, frameworks, hosting, CDN, payment, ad tech and 7,600+ more, with versions and categories. Fast bulk lookups, pay per site.

- **URL**: https://apify.com/scraper-forge/tech-stack-detector.md
- **Developed by:** [Scraper Forge](https://apify.com/scraper-forge) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $100.00 / 1,000 websites

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, analytics, tag managers, JavaScript frameworks, hosting, CDN, payment providers, A/B testing, ad tech and **7,600+ technologies**, with versions when exposed. Paste a list of domains and get one clean row per site.

### Why this one

- 💳 **Simple pay-per-website pricing**: no subscription, no API key, pay only for sites analysed
- 🧠 **7,600+ technology fingerprints** in 108 categories (CMS, Ecommerce, Analytics, CDN, PaaS, Payment processors, Tag managers…)
- 🏷️ **Versions** when the site exposes them (e.g. WordPress 7.2, styled-components 6.1)
- 🔗 **Implied technologies**: WordPress → PHP + MySQL, Next.js → React + Node.js
- 📋 **Ready-made columns**: `cms`, `ecommerce`, `analytics`, `cdn`, `webServer`, `jsFrameworks`, `paas`, `tagManager`, plus every technology grouped by category
- 🔍 Optional **evidence** for every detection (which header, script or meta tag matched)
- ⚡ Fast: plain HTTP, no browser, 20 sites in parallel; dead domains never stop the run

### Use cases

- **Sales prospecting**: find every Shopify store or HubSpot user in a lead list
- **Competitor research**: see the analytics, A/B testing and personalisation tools rivals use
- **Market sizing**: technology share across thousands of domains
- **Agencies & security**: inventory client stacks and outdated versions

### Input example

```json
{
  "websites": ["allbirds.com", "vercel.com", "https://wordpress.org"],
  "minConfidence": 50,
  "includeEvidence": false
}
```

### Output example

```json
{
  "url": "allbirds.com",
  "finalUrl": "https://www.allbirds.com/",
  "domain": "allbirds.com",
  "statusCode": 200,
  "technologiesCount": 10,
  "technologyNames": ["Cloudflare", "Shopify", "Swiper", "HTTP/3", "Open Graph", "Apple Pay", "PayPal", "Priority Hints", "HSTS", "Google Tag Manager"],
  "cms": ["Shopify"],
  "ecommerce": ["Shopify"],
  "analytics": [],
  "cdn": ["Cloudflare"],
  "tagManager": ["Google Tag Manager"],
  "byCategory": { "Ecommerce": ["Shopify"], "Payment processors": ["Apple Pay", "PayPal"], "CDN": ["Cloudflare"] },
  "technologies": [{ "name": "Shopify", "version": null, "confidence": 100, "categories": ["Ecommerce"], "website": "https://shopify.com" }]
}
```

### How it works & limits

It loads each homepage over HTTP and matches headers, cookies, script URLs, meta tags, HTML and DOM patterns against an open fingerprint database. Technologies that only reveal themselves through JavaScript executed in a browser may be missed. Sites behind aggressive bot protection return less data (`blocked: true`); enable a proxy for those.

Fingerprint data: [projectdiscovery/wappalyzergo](https://github.com/projectdiscovery/wappalyzergo) (MIT).

# Actor input Schema

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

Domains or URLs, one per line (example.com, https://shop.example.com). Thousands per run are fine.

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

Only report technologies detected with at least this confidence.

## `includeEvidence` (type: `boolean`):

Show what triggered each detection (header, script URL, meta tag…). Useful for verification.

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

Usually not needed. Use for sites that block data-center traffic.

## Actor input object example

```json
{
  "websites": [
    "wordpress.org",
    "allbirds.com",
    "vercel.com"
  ],
  "minConfidence": 50,
  "includeEvidence": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `websites` (type: `string`):

One row per website with its technologies.

# 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": [
        "wordpress.org",
        "allbirds.com",
        "vercel.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scraper-forge/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": [
        "wordpress.org",
        "allbirds.com",
        "vercel.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("scraper-forge/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": [
    "wordpress.org",
    "allbirds.com",
    "vercel.com"
  ]
}' |
apify call scraper-forge/tech-stack-detector --silent --output-dataset

```

## MCP server setup

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