Tech Stack Detector — Wappalyzer & BuiltWith API Alternative avatar

Tech Stack Detector — Wappalyzer & BuiltWith API Alternative

Pricing

from $26.80 / 1,000 website analyzeds

Go to Apify Store
Tech Stack Detector — Wappalyzer & BuiltWith API Alternative

Tech Stack Detector — Wappalyzer & BuiltWith API Alternative

Detect the technology stack behind any website — CMS, ecommerce, JS framework, web server, CDN, analytics, tag managers, payments and more — from its public response. One record per URL, pay-per-record. A pay-as-you-go Wappalyzer/BuiltWith API alternative.

Pricing

from $26.80 / 1,000 website analyzeds

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

18 hours ago

Last modified

Share

Give it a list of website URLs and get back the technology stack behind each one: CMS, ecommerce platform, JavaScript framework, web server, CDN, analytics, tag managers, payment providers, marketing/CRM tools, and more — every detection carrying the exact evidence that proved it. One structured tech_stack_record per URL, pay-per-record.

A drop-in, pay-as-you-go alternative to the Wappalyzer and BuiltWith APIs for sales prospecting, lead enrichment, competitive research, and market sizing.

What it reads

Only the target website's own public, logged-out HTTP response:

  • response headers (e.g. Server, X-Powered-By, X-Generator, CDN headers)
  • Set-Cookie NAMES — a standard technology fingerprint. Cookie values are never read or stored.
  • every resource URL the page references (script src, link href, form action)
  • page markup (the <meta name="generator"> tag, framework markers, data-* attributes)

No login, no API key, no CAPTCHA, no personal data. Technology names are factual identifications; no third-party page content is reproduced.

Input

fieldtypenotes
urlsstring listone or more website URLs; a scheme is added if you omit it
maxUrlsintegersafety cap per run (default 50, max 1000)

Output — one tech_stack_record per URL

Each record carries the requested url, the final_url after redirects, the status_code, the page title, the detected technologies (name, category, and the evidence for each), a categories roll-up, and technology_count. A URL the site refuses to serve is reported as blocked and is not billed.

Pricing

Pay-per-event. A flat $0.02 run start, then $0.04 per tech_stack_record (the URL analyzed) — volume tiers reduce the per-record price. You are billed only for URLs that were actually fetched and analyzed; blocked URLs cost nothing.

Detection coverage

The fingerprint set spans CMS (WordPress, Drupal, Shopify, Wix, Squarespace, Webflow …), JavaScript frameworks (React, Vue, Angular, Next.js, Nuxt, Gatsby …), web servers (Nginx, Apache, IIS, LiteSpeed), CDNs and PaaS (Cloudflare, CloudFront, Fastly, Akamai, Vercel, Netlify), analytics and tag managers (Google Analytics, GTM, Segment, Hotjar, Mixpanel …), marketing/CRM/support (HubSpot, Marketo, Intercom, Drift …), payments (Stripe, PayPal, Braintree), and common JS libraries and consent tools. Implied technologies (e.g. WordPress ⇒ PHP) are labeled as inferred so the evidence stays honest.