# Tech Stack Detector — Wappalyzer & BuiltWith API Alternative (`nexgenwatch/tech-stack-detector`) Actor

Detect the technology stack behind any website — CMS, ecommerce, JS framework, web server, CDN, analytics, tag managers, payments and more — from its public response. One record per URL, pay-per-record. A pay-as-you-go Wappalyzer/BuiltWith API alternative.

- **URL**: https://apify.com/nexgenwatch/tech-stack-detector.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Developer tools, Lead generation, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $26.80 / 1,000 website analyzeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 — Wappalyzer & BuiltWith API Alternative

Give it a list of website URLs and get back the technology stack behind each one:
CMS, ecommerce platform, JavaScript framework, web server, CDN, analytics, tag
managers, payment providers, marketing/CRM tools, and more — every detection
carrying the exact evidence that proved it. One structured `tech_stack_record`
per URL, pay-per-record.

A drop-in, pay-as-you-go alternative to the Wappalyzer and BuiltWith APIs for
sales prospecting, lead enrichment, competitive research, and market sizing.

### What it reads

Only the target website's **own public, logged-out HTTP response**:

- response **headers** (e.g. `Server`, `X-Powered-By`, `X-Generator`, CDN headers)
- **Set-Cookie NAMES** — a standard technology fingerprint. Cookie **values are
  never read or stored.**
- every **resource URL** the page references (script `src`, link `href`, form `action`)
- page **markup** (the `<meta name="generator">` tag, framework markers, `data-*`
  attributes)

No login, no API key, no CAPTCHA, no personal data. Technology names are factual
identifications; no third-party page content is reproduced.

### Input

| field | type | notes |
|---|---|---|
| `urls` | string list | one or more website URLs; a scheme is added if you omit it |
| `maxUrls` | integer | safety cap per run (default 50, max 1000) |

### Output — one `tech_stack_record` per URL

Each record carries the requested `url`, the `final_url` after redirects, the
`status_code`, the page title, the detected `technologies` (name, category, and
the evidence for each), a `categories` roll-up, and `technology_count`. A URL the
site refuses to serve is reported as blocked and **is not billed**.

### Pricing

Pay-per-event. A flat `$0.02` run start, then `$0.04` per `tech_stack_record`
(the URL analyzed) — volume tiers reduce the per-record price. You are billed only
for URLs that were actually fetched and analyzed; blocked URLs cost nothing.

### Detection coverage

The fingerprint set spans CMS (WordPress, Drupal, Shopify, Wix, Squarespace,
Webflow …), JavaScript frameworks (React, Vue, Angular, Next.js, Nuxt, Gatsby …),
web servers (Nginx, Apache, IIS, LiteSpeed), CDNs and PaaS (Cloudflare,
CloudFront, Fastly, Akamai, Vercel, Netlify), analytics and tag managers (Google
Analytics, GTM, Segment, Hotjar, Mixpanel …), marketing/CRM/support (HubSpot,
Marketo, Intercom, Drift …), payments (Stripe, PayPal, Braintree), and common JS
libraries and consent tools. Implied technologies (e.g. WordPress ⇒ PHP) are
labeled as inferred so the evidence stays honest.

# Actor input Schema

## `urls` (type: `array`):

One or more website URLs to analyze. A scheme is added automatically if you omit it (example.com becomes https://example.com).

## `maxUrls` (type: `integer`):

Safety cap on how many URLs are analyzed in one run.

## Actor input object example

```json
{
  "urls": [
    "https://www.shopify.com"
  ],
  "maxUrls": 10
}
```

# Actor output Schema

## `results` (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 = {
    "urls": [
        "https://www.apify.com",
        "https://www.python.org"
    ],
    "maxUrls": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/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 = {
    "urls": [
        "https://www.apify.com",
        "https://www.python.org",
    ],
    "maxUrls": 10,
}

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

```

## MCP server setup

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