# Website Technology Stack Detector: CMS, Analytics, Frameworks (`physealabs/tech-stack-detector`) Actor

Type websites and see what they are built with: CMS, ecommerce platform, JS framework, analytics, ad pixels, CRM, chat, payments, CDN, hosting and server, with evidence and versions. Built by Physea Labs (Liminal). Launch Sale: 90% OFF for the first week. $0.002 per site.

- **URL**: https://apify.com/physealabs/tech-stack-detector.md
- **Developed by:** [jay casey](https://apify.com/physealabs) (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

$2.00 / 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.

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

## Website Technology Stack Detector: CMS, Analytics, Frameworks

Type a list of websites and see what each one runs on: CMS or site builder, ecommerce platform, JavaScript framework, analytics and tag managers, ad pixels, marketing automation, live chat, payments, CDN, hosting and web server. Every detection carries the evidence that triggered it.

🚀 **Launch Sale: 90% OFF for the first week!** Prices below are the regular rates; launch-week runs are billed at a tenth of them.

### What can it do?

| What you get | Features |
|---|---|
| 🧱 CMS, ecommerce, JS frameworks, UI libraries | ⚡ One HTTP request per site, no browser: hundreds of sites a minute |
| 📊 Analytics, tag managers, ad pixels, session recording | 🔍 Evidence string for every detection (header, asset URL, meta tag) |
| 💬 CRM, chat, payments, consent, CDN, hosting, server | 🏷️ Versions where the site exposes them (generator tag, server header) |

### Who this is for

- Sales prospecting: find Shopify stores, HubSpot users or sites without analytics
- Competitive research on a list of rivals
- Agencies qualifying leads by their current stack
- Security and compliance sweeps (HSTS, consent tools, outdated CMS versions)

### What you get back

| Field | Type | What you get | Example |
|---|---|---|---|
| `domain` | `string` | Final host | `vercel.com` |
| `technology_names` | `array` | Detected technology names | `["Next.js", "Vercel", "Tailwind CSS"]` |
| `technologies` | `array` | name, category, version, evidence | `[{"name": "Next.js", "category": "JS framework", ...}]` |
| `categories` | `object` | Category to technologies | `{"Hosting": ["Vercel"]}` |
| `technology_count` | `integer` | Number detected | `4` |
| `generator` | `string` | <meta generator> value | `WordPress 7.2` |
| `title` | `string` | Page title | `Agentic Infrastructure - Vercel` |
| `status` | `string` | `ok` or `error` | `ok` |

Every run also writes `RUN_SUMMARY.json` to the key-value store (counts, spend-limit flag, pricing).

### What you need to provide

| Field | Type | What it does | Example |
|---|---|---|---|
| `urls` | `array` | Homepages or any page. A bare domain like shopify.com works. | `[{"url": "https://www.shopify.com"}, {"url": "https://vercel.com"}, {"url": "https://wordpress.org/news/"}]` |
| `categories` | `array` | Keep only some categories, e.g. CMS, Analytics, Ecommerce, Advertising, Hosting. Leave empty for everything. | `-` |
| `maxConcurrency` | `integer` | Websites fetched at the same time. | `10` |

#### Quick start

1. Click **Try for free**.
2. Press **Start**: the sample input finishes in under a minute with no API keys or setup.
3. Replace the sample with your own values and run again.
4. Open the dataset, or export it as JSON, CSV or Excel.

### Pricing

🚀 **Launch Sale: 90% OFF for the first week!**

- `website-analyzed`: **$0.002** per website ($2 per 1,000 sites).
- Unreachable sites (DNS, timeout, 4xx/5xx error pages) are not charged.
- Set a max cost per run in the run options and the run stops cleanly when it hits it.
- Normal Apify platform usage applies.

### Limits and honest notes

- Detection reads one HTML response plus its headers and cookies. Tools loaded only after user interaction or deep inside a single-page app may not be seen.
- Signatures are maintained in the actor code (100+ technologies); niche tools outside that list are not reported.
- Sites behind a bot wall return what the wall shows (often just the CDN).
- No other Apify actor is called: everything is collected in-house over plain HTTP.

### Run it from code

Same input as the Console sample:

```json
{
  "urls": [
    {
      "url": "https://www.shopify.com"
    },
    {
      "url": "https://vercel.com"
    },
    {
      "url": "https://wordpress.org/news/"
    }
  ]
}
```

```sh
curl -X POST "https://api.apify.com/v2/acts/physealabs~tech-stack-detector/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" -d @input.json
```

```python
from apify_client import ApifyClient
items = ApifyClient("YOUR_APIFY_TOKEN").actor("physealabs/tech-stack-detector").call(run_input={"urls": [{"url": "https://www.shopify.com"}, {"url": "https://vercel.com"}, {"url": "https://wordpress.org/news/"}]})
```

It also works from Zapier, Make, n8n and Apify schedules.

### About Physea Labs · Liminal

Built and maintained by **Physea Labs**: the same extraction layer that feeds [Liminal](https://physea.ai), our grounded research and decision engine. If it is good enough to feed Liminal's citations, it is good enough for your pipeline.

# Actor input Schema

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

Homepages or any page. A bare domain like shopify.com works.

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

Keep only some categories, e.g. CMS, Analytics, Ecommerce, Advertising, Hosting. Leave empty for everything.

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

Websites fetched at the same time.

## Actor input object example

```json
{
  "urls": [
    {
      "url": "https://www.shopify.com"
    },
    {
      "url": "https://vercel.com"
    },
    {
      "url": "https://wordpress.org/news/"
    }
  ],
  "maxConcurrency": 10
}
```

# Actor output Schema

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

One row per item; error rows explain anything that was skipped and are never charged.

## `summary` (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": [
        {
            "url": "https://www.shopify.com"
        },
        {
            "url": "https://vercel.com"
        },
        {
            "url": "https://wordpress.org/news/"
        }
    ]
};

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

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

```

## MCP server setup

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