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

Detect the technology stack of any website in bulk: CMS, ecommerce platform, analytics, payments, CDN, frameworks, plus the SaaS tools a company uses from its DNS records. 7,600+ technologies with versions. $10 per 1,000 websites.

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

## Pricing

from $10.00 / 1,000 website analyseds

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. Paste a list of domains and get, for each one, the CMS, ecommerce platform, analytics and marketing tools, payment providers, CDN, frameworks and hosting — plus the SaaS products the company itself uses, read from its public DNS records.

A fast, affordable alternative to Wappalyzer and BuiltWith lookups for lead qualification, market research and competitor analysis.

- **7,600+ technologies** in 109 categories, with versions and confidence scores
- **Bulk**: thousands of websites per run, analysed in parallel
- **Beyond the page**: email provider and verified SaaS tools from DNS (Google Workspace, Microsoft 365, Atlassian, HubSpot, Stripe, OpenAI and hundreds more)
- **Evidence included**: every detection says what it was based on (headers, cookies, HTML, scripts, DNS…)
- **Fair billing**: websites that cannot be reached are listed separately and never charged

### Who uses it

- **Sales and lead generation** — qualify a prospect list by platform ("all Shopify stores using Klaviyo", "companies on Microsoft 365")
- **Agencies** — find sites on outdated or end-of-life versions
- **Market research** — measure technology adoption across an industry or a competitor set
- **Security and IT** — inventory the software exposed by your own domains

### Example output

```json
{
  "url": "https://allbirds.com",
  "finalUrl": "https://www.allbirds.com/",
  "statusCode": 200,
  "technologyCount": 13,
  "summary": "Shopify, Microsoft 365, Apple Pay, Cloudflare, Google Tag Manager, HSTS, Swiper, DocuSign, HTTP/3, Miro, Open Graph",
  "technologyNames": ["Shopify", "Microsoft 365", "Apple Pay", "Cloudflare", "Google Tag Manager"],
  "categories": {
    "Ecommerce": ["Shopify"],
    "Email": ["Microsoft 365"],
    "Payment processors": ["Apple Pay"],
    "CDN": ["Cloudflare"],
    "Tag managers": ["Google Tag Manager"]
  },
  "technologies": [
    {
      "name": "Shopify",
      "categories": ["Ecommerce"],
      "groups": ["Sales"],
      "version": null,
      "confidence": 100,
      "detectedBy": ["cookies", "meta", "scriptSrc"],
      "website": "https://shopify.com",
      "description": "Shopify is a subscription-based software that allows anyone to set up an online store…",
      "saas": true,
      "openSource": null,
      "pricing": ["low", "recurring"],
      "cpe": null
    }
  ],
  "analysedAt": "2026-09-20T15:41:12Z"
}
```

`summary` and `technologyNames` are there for spreadsheets; `technologies` carries the full detail.

### Input

```json
{
  "urls": ["shopify.com", "https://www.nike.com/de", "wordpress.org"],
  "includeDns": true,
  "minConfidence": 50,
  "categories": ["CMS", "Ecommerce", "Analytics"]
}
```

| Field | What it does |
|---|---|
| `urls` | Domains or full URLs, one per line. Duplicates are removed. |
| `includeDns` | Also read the domain's MX, TXT, NS and SOA records (on by default, no extra charge). |
| `minConfidence` | Hide detections below this confidence. 50 removes weak single-hint matches. |
| `categories` | Optional: keep only technologies in these categories. |
| `maxConcurrency`, `timeoutSecs` | Tuning for very large or very slow lists. |
| `proxyConfiguration` | Optional. Most websites answer without a proxy. |

### Pricing

| Event | Price |
|---|---|
| Website analysed | **$0.01** |
| Actor start | $0.00005 per run |

**$10 per 1,000 websites.** Invalid addresses and websites that could not be reached are not charged; they are listed under *Websites that could not be analysed* in the run's output. Set **Maximum cost per run** to cap your spend — the run stops cleanly at the limit and tells you how many websites are left.

### How detection works, and its limits

The Actor requests each website once, like a browser would, and matches the response — HTTP headers, cookies, HTML, meta tags, script URLs, inline scripts, page structure and the final URL — plus the domain's DNS records against open-source technology fingerprints.

Stated plainly:

- **No JavaScript is executed.** About 87% of the fingerprints (6,670 of 7,628) can be matched this way. Technologies that only reveal themselves through JavaScript variables in a running browser may be missed; frameworks on heavily client-rendered sites are the usual case.
- **One page per website.** The URL you give is the page that is analysed (the home page for a bare domain). Tools loaded only on checkout or login pages will not be seen — add those URLs if they matter.
- **Bot-protected sites still return results.** When a site answers with a block page (HTTP 403), you still get what its headers and DNS reveal — typically CDN, bot protection, email provider and verified SaaS tools — and `statusCode` tells you it happened.
- **DNS detections describe the company, not the page.** A `detectedBy: ["dns"]` entry such as Atlassian or DocuSign means the company verified its domain with that product.
- **Speed**: about 1,000 websites per hour at the default 1 GB of memory. Detection is CPU-bound, so raising the run's memory to 4 GB makes it roughly three times faster.

Fingerprints come from the community-maintained [webappanalyzer](https://github.com/enthec/webappanalyzer) project (the open continuation of Wappalyzer's rule set, GPL-3.0), refreshed regularly, with local corrections for rules that produce false positives.

### FAQ

**Can I run it on a schedule to track changes?**
Yes — add it to a [Schedule](https://docs.apify.com/platform/schedules) and compare `technologyNames` between runs.

**Can I use it from my own code or an AI agent?**
Yes. Use the API tab for ready-made JavaScript, Python and cURL snippets, or the MCP tab to give it to an AI agent.

**A technology is wrong or missing.**
Open an issue on the Issues tab with the website URL. False positives are fixed in the Actor's own rule corrections, which survive fingerprint updates.

# Actor input Schema

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

One per line. Domains (shopify.com) or full URLs (https://www.nike.com/de). Duplicates are removed.

## `includeDns` (type: `boolean`):

Reads the domain's public MX, TXT, NS and SOA records to find the email provider and the SaaS products the company has verified its domain with (Google Workspace, Microsoft 365, Atlassian, HubSpot, Stripe...). No extra charge.

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

Hide detections below this confidence (0-100). 50 removes weak single-hint matches.

## `categories` (type: `array`):

Optional. Keep only technologies in these categories, for example: CMS, Ecommerce, Analytics, Payment processors, CDN, JavaScript frameworks, Marketing automation.

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

How many websites are fetched at the same time. Lower it if your sites are all on the same host.

## `timeoutSecs` (type: `integer`):

Websites that do not answer within this time are skipped and not charged.

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

Optional. Most websites answer without a proxy. Turn one on if many of your sites block datacenter traffic.

## Actor input object example

```json
{
  "urls": [
    "shopify.com",
    "wordpress.org"
  ],
  "includeDns": true,
  "minConfidence": 50,
  "maxConcurrency": 20,
  "timeoutSecs": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

One item per analysed website: detected technologies with category, version, confidence and the evidence they were detected by.

## `failedUrls` (type: `string`):

Invalid or unreachable addresses with the reason. These are not charged.

# 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": [
        "shopify.com",
        "wordpress.org"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("blues_akg/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": [
        "shopify.com",
        "wordpress.org",
    ],
    "proxyConfiguration": { "useApifyProxy": False },
}

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

```

## MCP server setup

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