Tech Stack Detector: Wappalyzer & BuiltWith Alternative

Find out what any website is built with: CMS, ecommerce platform, JavaScript framework, analytics and tag managers, CDN and hosting, payment providers, chat widgets and 7,600+ other technologies. Bulk, fast, one polite request per site. Or schedule it and hear only when a site's stack changes.

Why this one

• 7,600+ technology fingerprints from the open-source Wappalyzer community datasets (see Credits & licence).
• Cheap: $1.50 per 1,000 sites, and unreachable sites aren't charged.
• Stack-change monitor: a daily or weekly schedule in Changes only mode tells you when a prospect moves from WooCommerce to Shopify, adds Klaviyo, or drops Google Analytics.
• Handy summary columns (cms, ecommerce, framework, server, analytics, cdn, payment) for spreadsheets and CRMs, plus the full list with versions, categories and how each one was detected.

Use cases

• Lead generation and sales intelligence: filter a list of domains to those running Shopify, Magento, HubSpot, Intercom, etc.
• Competitor research and market sizing: what do the top sites in a niche use?
• Agencies: audit prospects' stacks before a pitch; spot outdated CMS versions.
• AI agents: call it through the Apify MCP server to answer "what is example.com built on?".

Input

{
  "startUrls": [{ "url": "https://www.allbirds.co.uk" }, { "url": "wordpress.org/news/" }],
  "mode": "all",
  "minConfidence": 50,
  "maxConcurrency": 5
}

Output (one row per site)

{
  "inputUrl": "https://www.allbirds.co.uk",
  "url": "https://www.allbirds.co.uk/",
  "statusCode": 200,
  "title": "Allbirds UK | Sustainable Shoes & Clothing",
  "cms": "Shopify",
  "ecommerce": "Shopify",
  "framework": null,
  "server": null,
  "analytics": null,
  "tagManager": ["Google Tag Manager"],
  "cdn": ["Cloudflare"],
  "payment": ["Apple Pay"],
  "technologyNames": ["Cloudflare", "Shopify", "Swiper", "HTTP/3", "Open Graph", "Apple Pay", "Priority Hints", "HSTS", "Google Tag Manager"],
  "technologies": [
    { "name": "Shopify", "version": null, "categories": ["Ecommerce", "CMS"], "confidence": 100, "detectedVia": ["cookies", "dom"], "website": "https://shopify.com" }
  ],
  "error": null,
  "checkedAt": "2026-10-26T18:45:00+00:00"
}

In Changes only mode rows also carry added and removed lists.

How it works and what it respects

• Fetches one public page per site (the URL you give) and reads its response headers, cookie names, HTML, script URLs, meta tags and simple DOM patterns. No login, no form submission, no personal data collected.
• Obeys robots.txt and identifies itself honestly in its user agent. Pages disallowed for it are reported, not fetched.

Limits (honest)

• No JavaScript execution. Technologies only detectable inside a running browser (some JS-variable or rendered-DOM fingerprints) can be missed, so results are a floor, not a ceiling. Server-side and HTML-visible tech (CMS, ecommerce, CDN, analytics tags, most frameworks) is detected well.
• Only the page you give is analysed: a blog or shop on a subdomain needs its own URL.
• Sites behind aggressive bot protection may return a challenge page (you'll see e.g. HTTP 403 in error and few detections). Enable a proxy for those.
• Confidence-based fingerprints can occasionally misfire; raise minConfidence to be stricter.

Pricing (pay per event)

• Site analysed (Detect mode): $0.0015 per site, i.e. $1.50 per 1,000 sites. Unreachable sites are free.
• Site checked (Changes only): $0.0005 per site.
• Stack change (Changes only): $0.003 per site whose stack changed.

Credits & licence

Technology fingerprints come from projectdiscovery/wappalyzergo's merged dataset, which is derived from enthec/webappanalyzer and HTTPArchive/wappalyzer, both licensed GPL-3.0. Accordingly this Actor's source code and data are released under the GPL-3.0 licence (see LICENSE). Not affiliated with Wappalyzer or BuiltWith.