Bulk Tech Stack Detector - BuiltWith/Wappalyzer Alternative

What is Bulk Tech Stack Detector - BuiltWith/Wappalyzer Alternative?

Website Tech Stack Detector takes a list of domains and tells you what each site is actually built with — the CMS, the e-commerce engine, the payment processor, the analytics and tag manager, the CDN, the framework — with categories, versions and a confidence score per finding.

It is a practical BuiltWith alternative for enrichment work: same job, priced per domain, and automatable from the Apify API or a schedule.

Alongside the raw stack, it derives buying signals — for example, a site running Shopify and a payment processor and a review platform is a very different prospect from a brochure site on WordPress with nothing attached. The signals object exposes those so you can segment without hand-writing the rules.

What can this Actor do?

• ✅ 235 technology signatures matched against HTML, headers, scripts, cookies and meta tags
• ✅ Categories — CMS, e-commerce, payment, analytics, CDN, framework, tag manager and more, as separate fields so you can filter directly
• ✅ Version detection for technologies that expose one (toggle with detectVersion)
• ✅ Confidence score per match, with a tunable floor (minConfidence) so you choose the precision/recall trade-off
• ✅ Buying signals derived from the combination of technologies found
• ✅ Meta and social link extraction (toggle with extractMeta)
• ✅ Optional Apify Proxy for targets that geo-block or rate-limit datacenter IPs
• ✅ Built on Apify: schedule it, webhook the results, or pull the dataset from the API — storage, monitoring and retries are handled by the platform

How to use it

1. Open the Input tab.
2. Add domains to domains, or paste a newline/CSV list into domainsCsv.
3. Set maxDomains to the ceiling you want (default 1000) and minConfidence to taste.
4. Click Start.
5. Open the Overview dataset view for a flat table of domain, tech count and categories.

{
  "domains": [{ "url": "https://example.com" }],
  "detectVersion": true,
  "minConfidence": 50,
  "maxDomains": 1000
}

Pricing

This Actor is pay-per-event, billed per domain analyzed.

Event	When it is charged	Price
Domain analyzed	A domain was successfully fetched and fingerprinted	$8 per 1,000 domains ( = $0.008 each )
Actor start	Once per run, per GB of memory	$0.00005 per GB

Domains that fail to fetch are not charged. Apify's BRONZE, SILVER, GOLD, PLATINUM and DIAMOND plans lower the unit price automatically.

Rough budgeting, assuming every domain resolves:

Domains in	Cost
1,000	$8
5,000	5 × $8
10,000	10 × $8

Input

Field	Type	Default	Notes
domains	array	empty	Domains or URLs as request objects
domainsCsv	string	empty	Same list as CSV or newline-separated text
maxConcurrency	integer	20	Parallel domain fetches
timeoutSec	integer	15	Per-domain timeout
maxDomains	integer	1000	Hard cap per run
detectVersion	boolean	true	Attempt version detection
minConfidence	integer	50	Minimum confidence to report a technology
extractMeta	boolean	true	Extract meta tags and social links
useApifyProxy	boolean	false	Route requests through Apify Proxy

Output

One dataset item per analyzed domain:

{
  "domain": "example.com",
  "title": "Example Domain",
  "httpStatus": 200,
  "techs": [
    { "name": "Cloudflare", "category": "cdn", "version": null, "confidence": 90 }
  ],
  "categories": {
    "cms": [],
    "ecommerce": [],
    "payment": [],
    "analytics": []
  },
  "signals": {
    "techCount": 1
  }
}

Other Actors you may like

• Bulk On-Page SEO Audit — 26 on-page checks plus tech detection, when you want an SEO score too.
• Bulk Email Verifier — verify the contacts you found on the site.
• ATS Job Board Feed Sync - Greenhouse, Lever, Ashby — convert a tech signal into a hiring signal.

FAQ

How is this different from BuiltWith? Same category of data, delivered as an Actor: priced per domain, scriptable through the Apify API, and schedulable without a separate subscription.

Why does a domain return an empty tech list? Either nothing matched above minConfidence, or the page is rendered entirely client-side. Lower minConfidence first; if that does not help, the site really is JS-only.

Do failed domains cost anything? No. Only successful fingerprints emit the billing event.

Can I detect versions? Yes, detectVersion is on by default. Not every technology exposes a version, so version is null in those cases.