# Tech Stack Lookup and Change Alerts (`tan-solutions/tech-stack`) Actor

Website technology checker for up to 1,000 domains: CMS, e-commerce platform, analytics, marketing, payments, CDN and frameworks, with version and confidence. Monitor mode shows which technologies each site added or removed since your last run.

- **URL**: https://apify.com/tan-solutions/tech-stack.md
- **Developed by:** [Tan Solutions](https://apify.com/tan-solutions) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.80 / 1,000 domain delivereds

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/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 Lookup and Change Alerts

Tech stack lookup for up to 1,000 domains at once: a website technology checker that lists the CMS, e-commerce
platform, analytics, marketing tools, payments, CDN, hosting and frameworks of each site, with version and confidence.
Run it on a schedule and it tells you which technologies each site added or removed since the last run. A simple,
pay-per-result BuiltWith alternative for checking your own list of domains.

### Run it from the API or on a schedule

Get one row per domain back in one call (replace `<YOUR_API_TOKEN>` with your Apify API token from Console, **Settings**, **API & Integrations**):

```bash
curl -X POST "https://api.apify.com/v2/acts/tan-solutions~tech-stack/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"domains":["apify.com","example.com"],"mode":"lookup"}'
```

Send `{}` (no input) to try it on example.com.

Watch the same domains every Monday at 06:00 UTC and get only what changed (monitor mode is the default; the history
is kept in a key-value store in your account) with an Apify schedule:

```bash
curl -X POST "https://api.apify.com/v2/schedules?token=<YOUR_API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"name": "tech-stack-weekly", "cronExpression": "0 6 * * 1", "timezone": "UTC", "isEnabled": true, "isExclusive": true,
       "actions": [{"type": "RUN_ACTOR", "actorId": "IJ8G1BTdzhdiZubNY",
         "runInput": {"body": "{\"domains\":[\"apify.com\",\"example.com\"],\"mode\":\"monitor\"}", "contentType": "application/json"}}]}'
```

In Apify Console the same is: **Schedules**, **Create new**, cron `0 6 * * 1`, add this Actor with your input. Open
the **Changes since the last run** view of each run's dataset to see only the added and removed technologies.

### What it does

- Opens each domain's homepage once (https first, http if https cannot connect) and reads its headers, cookie names,
  meta tags, script and link URLs.
- Matches them against 167 technologies in 31 categories (list below) and gives each a confidence from 60 to 100.
- **Monitor mode** (default) remembers every domain between runs and reports `added` and `removed` technologies with
  `firstSeen` and `lastSeen` dates. The first run of a domain is its baseline.
- **Lookup mode** just lists what each site uses today, with no history.
- **Technology filter**: give names or categories (for example `Shopify`, `Klaviyo` or `Payments`) and only the
  matching domains are listed. In monitor mode a domain also matches when it just stopped using that technology.

### Who it is for

Agencies and freelancers checking prospects' websites, SaaS teams tracking which sites install or drop their own or a
rival's product, analysts sizing a market by platform, and site owners who want an alert when their stack changes.

### Quick start

1. Paste your domains (one per line; URLs are fine, only the domain is kept).
2. Keep **Monitor** mode to track changes, or pick **Lookup** for a one-off check.
3. Optional: add technologies or categories to the filter.
4. Run it, then open the **Technologies per domain** or **Changes since the last run** view.

### Input

| Field | Default | What it does |
| --- | --- | --- |
| `domains` | `["example.com"]` | Domains or URLs, up to 1,000 per run (`maxDomains`). Invalid entries and duplicates are skipped for free. |
| `mode` | `monitor` | `monitor` keeps a history and reports changes; `lookup` only lists today's technologies. |
| `stateKey` | `tech-stack-monitor` | Name of the key-value store in your account that keeps the history. Use one name per list you monitor. If the run has no permission for that store, it still delivers rows but warns that the history was not kept: pick another name. |
| `technologies` | `[]` | Optional filter: technology names or categories. Empty = every checked domain is listed. |
| `maxDomains` | 100 | How many domains to check at most (1-1,000). |
| `includeFailed` | `true` | Also list domains that could not be checked (free), with the reason. |
| `timeoutSecs` | 20 | Time limit per homepage request (5-60 s). |
| `maxConcurrency` | 4 | How many sites are checked at the same time (1-8). |

```json
{ "domains": ["shop-one.com", "wp-blog.com"], "mode": "monitor", "technologies": ["Shopify"] }
```

### Output example

One row per domain (second weekly run of a monitored store that just added HubSpot; technologies shortened):

```json
{
  "domain": "shop-one.com",
  "status": "ok",
  "checkedAt": "2026-11-13T19:50:00.664Z",
  "mode": "monitor",
  "httpStatus": 200,
  "technologyNames": ["Shopify", "HubSpot", "Klaviyo", "Google Tag Manager"],
  "technologies": [
    { "name": "Shopify", "category": "E-commerce", "version": null, "confidence": 100, "evidence": ["header:x-shopid", "url"],
      "firstSeen": "2026-11-06T06:00:10.535Z", "lastSeen": "2026-11-13T19:50:00.664Z" },
    { "name": "HubSpot", "category": "Marketing automation", "version": null, "confidence": 90, "evidence": ["url"],
      "firstSeen": "2026-11-13T19:50:00.664Z", "lastSeen": "2026-11-13T19:50:00.664Z" }
  ],
  "categories": { "E-commerce": ["Shopify"], "Marketing automation": ["HubSpot", "Klaviyo"], "Tag manager": ["Google Tag Manager"] },
  "added": ["HubSpot"],
  "removed": [],
  "firstCheck": false,
  "previousCheckAt": "2026-11-06T06:00:10.535Z",
  "matchedFilter": ["Shopify"],
  "error": null
}
```

`status` is `ok`, `blocked`, `rate_limited`, `robots_disallowed` or `failed`. Only `ok` rows cost money; the others are
free. An HTTP 401/403 refusal or a bot wall is `blocked`. When the wall is Cloudflare, Akamai or
Imperva, the row still names that service in `technologies`. robots.txt follows the robots.txt standard (RFC 9309): no
robots.txt (any 4xx answer) means no rules; a robots.txt that disallows TanForgeBot, answers with a server error (5xx)
or cannot be reached is `robots_disallowed` (try again on a later run). The **Run summary** record (SUMMARY)
counts checked, delivered, filtered and failed domains and lists every failed and invalid entry with the reason.

### Pricing

Pay per event. You pay for each domain delivered in the dataset:

| Plan | Price per 1,000 domains |
| --- | --- |
| Free | $3.00 |
| Bronze | $2.50 |
| Silver | $2.20 |
| Gold | $1.80 |
| Platinum and Diamond | $1.50 |

Domains your technology filter leaves out are not listed and cost $0.60 per 1,000 checks. Failed, blocked, invalid
and duplicate domains are free. Your spending limit always holds: the run stops cleanly when it is reached.

### Technologies detected

- **CMS:** WordPress, Drupal, Joomla, TYPO3, Ghost, Blogger, HubSpot CMS, Adobe Experience Manager, Sitecore
- **Headless CMS:** Contentful, Sanity
- **Site builder:** Wix, Squarespace, Webflow, Framer, Duda, GoDaddy Website Builder
- **E-commerce:** Shopify, Shopify Plus, WooCommerce, Magento, BigCommerce, PrestaShop, Salesforce Commerce Cloud, Shopware, Ecwid, OpenCart
- **Payments:** Stripe, PayPal, Klarna, Afterpay, Affirm, Braintree, Square, Adyen
- **Subscriptions and reviews:** Recharge, Yotpo, Judge.me, Okendo, Trustpilot
- **Marketing automation:** HubSpot, Mailchimp, Klaviyo, Marketo, Pardot, Salesforce Marketing Cloud, Attentive, Postscript, Omnisend, ActiveCampaign, Braze
- **CRM:** Salesforce
- **Analytics:** Google Analytics, Google Analytics 4, Adobe Analytics, Hotjar, Microsoft Clarity, Matomo, Plausible, Fathom, Cloudflare Web Analytics, Segment, Mixpanel, Heap, Amplitude, FullStory, Crazy Egg
- **Advertising:** Meta Pixel, Google Ads, LinkedIn Insight Tag, TikTok Pixel, Microsoft Advertising, Pinterest Tag, X (Twitter) Pixel, Snap Pixel, Reddit Pixel, Criteo
- **Tag manager:** Google Tag Manager, Adobe Experience Platform Tags
- **A/B testing:** Optimizely, VWO
- **Live chat:** Intercom, Drift, Zendesk, Crisp, Tawk.to, LiveChat, Freshchat, Gorgias, Tidio
- **Cookie consent:** OneTrust, Cookiebot, Usercentrics, TrustArc, Osano, CookieYes, Iubenda
- **CDN and cache:** Cloudflare, Fastly, Akamai, Amazon CloudFront, Bunny CDN, Azure Front Door, Varnish
- **Hosting:** Vercel, Netlify, GitHub Pages, Heroku, Render, Fly.io, Amazon S3, Google Cloud, WP Engine, Kinsta, Pantheon, Acquia
- **Security:** Sucuri, Imperva, reCAPTCHA, hCaptcha, Cloudflare Turnstile
- **Web server:** Nginx, Apache HTTP Server, Microsoft IIS, LiteSpeed, Caddy, OpenResty, Envoy
- **Web framework:** Next.js, Nuxt, Remix, SvelteKit, Astro, ASP.NET, Express, Laravel, Django, Ruby on Rails
- **JavaScript:** React, Vue.js, Angular, Svelte, Ember.js, Alpine.js, jQuery, htmx
- **Programming language:** PHP, Node.js, Java, Python, Ruby
- **Static site generator:** Hugo, Jekyll, Gatsby, Docusaurus
- **UI, fonts and media:** Bootstrap, Tailwind CSS, Font Awesome, Google Fonts, Adobe Fonts, YouTube, Vimeo, Google Maps
- **Search and monitoring:** Algolia, Sentry, New Relic, Datadog RUM

### Limits

- One page per domain: the homepage. Tools loaded only on other pages, after a login or by JavaScript after the page
  loads (no browser rendering) are not seen.
- Shopify Plus is a low-confidence hint: it can only be guessed from the public page.
- Sites behind a bot wall, a CAPTCHA or an HTTP 401/403 refusal are reported as `blocked` (free); the Actor never tries to get around them.
- The crawler is called TanForgeBot and obeys robots.txt: a homepage disallowed for it is reported as
  `robots_disallowed` (free).
- How many domains return technologies depends on your list. In our test of 500 well-known brand homepages
  (14 Nov 2026), 374 of 500 (74.8 %) returned technologies. The other 126 were free: 80 behind a bot wall, 33 refused
  by robots.txt or with an unreachable robots.txt, 6 rate-limited and 7 errors.
- Up to 1,000 domains per run; schedule several runs (one `stateKey` each) for bigger lists.

### FAQ

**How is this different from BuiltWith?** You bring your own list of domains and pay only for the domains checked, with
no subscription. It does not search the web for sites that use a technology.

**What does monitor mode cost?** The same as lookup: one domain event per delivered row. The history is free and lives
in your own key-value store.

**Why was a domain not listed?** See the SUMMARY record of the run: it lists every failed, blocked, invalid and
duplicate entry with the reason, and how many domains your filter left out.

**How do I reset the history?** Delete the key-value store named in `stateKey`, or use a new name.

### Related tools by Tan Solutions

- [Domain Intelligence: DNS, WHOIS/RDAP and SSL](https://apify.com/tan-solutions/domain-intel): DNS, email security, registration data and SSL for any list of domains.
- [SEO Audit Tool](https://apify.com/tan-solutions/seo-audit): on-page SEO checker with PageSpeed for any list of pages.
- [URL to Markdown](https://apify.com/tan-solutions/url-to-markdown): web pages to clean Markdown for LLMs, RAG pipelines and AI agents.
- [US Company Filings & Financials](https://apify.com/tan-solutions/company-filings): 10-K, 10-Q, 8-K filings and XBRL facts by ticker.

### More from Tan Solutions

- [Tech stack tool page](https://www.tansolutions.org/tools/tech-stack/): details and examples for this Actor on our site.
- [Guide: BuiltWith alternatives for website tech stack lookup](https://www.tansolutions.org/guides/builtwith-alternatives-tech-stack-lookup/)
- [All Tan Solutions data tools](https://www.tansolutions.org/tools/)

### Your responsibilities

You are responsible for lawful use of the results. In particular, the data may not be used for mass unsolicited
advertising. No personal data is collected: only technology names, versions and short evidence labels. Technology
data can be incomplete or wrong; the Actor is provided without warranty, and liability is capped at the fees you paid
in the last 12 months. Questions and issues are answered within 14 days through the Actor's Issues tab.

Not affiliated with BuiltWith, Wappalyzer, Shopify, Google, Cloudflare or any other product named here. All product
names belong to their owners.

Made by Tan Solutions.

# Actor input Schema

## `domains` (type: `array`):

One domain per line, for example example.com. Full URLs are fine: only the domain is used and its homepage is checked. Duplicates and invalid entries are skipped for free. Left out, example.com is checked as a quick demo.

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

Monitor: remember each domain's technologies and show what was added or removed since the last run (schedule it daily or weekly). Lookup: just list the technologies, nothing is stored.

## `stateKey` (type: `string`):

Name of the key-value store in your account that keeps the history (a-z, 0-9 and hyphens, up to 63 characters). Use a different name for each list you monitor.

## `technologies` (type: `array`):

Optional. Keep only domains that use (or, in monitor mode, just added or removed) one of these technologies or categories, for example Shopify, Klaviyo, HubSpot or E-commerce. Other domains are free and not listed. Leave empty for all domains.

## `maxDomains` (type: `integer`):

Stop after this many domains. The hard limit is 1,000 per run.

## `includeFailed` (type: `boolean`):

Also list domains that could not be checked (offline, blocked by a bot wall, robots.txt), with the reason. They are always free.

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

How long to wait for one homepage before giving up on it.

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

How many domains are checked at the same time. Each website still gets at most one request per second.

## Actor input object example

```json
{
  "domains": [
    "example.com"
  ],
  "mode": "monitor",
  "stateKey": "tech-stack-monitor",
  "technologies": [],
  "maxDomains": 100,
  "includeFailed": true,
  "timeoutSecs": 20,
  "maxConcurrency": 4
}
```

# Actor output Schema

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

No description

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

No description

## `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 = {
    "domains": [
        "example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tan-solutions/tech-stack").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 = { "domains": ["example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("tan-solutions/tech-stack").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 '{
  "domains": [
    "example.com"
  ]
}' |
apify call tan-solutions/tech-stack --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tan-solutions/tech-stack"
        }
    }
}
```

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/IJ8G1BTdzhdiZubNY/builds/rGSoY4dMSlroVmmjs/openapi.json
