Web Tech Stack Detector avatar

Web Tech Stack Detector

Pricing

from $1.50 / 1,000 website analyzeds

Go to Apify Store
Web Tech Stack Detector

Web Tech Stack Detector

Find what any website is built with: CMS, e-commerce platform, JS framework, server, CDN and hosting, analytics and ad pixels, live chat, payments and cookie tools. Fast HTTP-only checks, one JSON row per site with evidence. Built for scripts and AI agents.

Pricing

from $1.50 / 1,000 website analyzeds

Rating

0.0

(0)

Developer

David Castellanos Cordova

David Castellanos Cordova

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Security

Limited permissions

Share

Website Tech Stack Detector

Find out what any public website is built with: CMS, e-commerce platform, JavaScript framework, web server, CDN and hosting, analytics and ad pixels, live chat, payments, captcha and cookie consent tools.

Built for scripts and AI agents: one compact JSON row per website, with a one-line summary, a flat techNames list, the technologies grouped by categories, and the evidence behind each detection.

Why this one

  • Simple pricing. From November 17, 2026: $1.50 per 1,000 websites analyzed, plus Apify's standard $0.00005 start fee per run. Platform usage is included. Errors, unreachable sites and pages blocked by robots.txt are never charged, and the run stops when it reaches the spending limit you set. Until then you only pay Apify platform usage.
  • Fast and light. HTTP only, no browser: a single request per website, so runs finish in seconds.
  • Polite. It reads each site's robots.txt and skips pages it disallows. It never logs in and collects no personal data.
  • Latin America ready. Besides the usual global tools, it detects VTEX, Tiendanube, Mercado Pago and Culqi.

Input

FieldDescription
urlsDomains or URLs, e.g. shopify.com or https://nextjs.org.
maxUrlsSafety cap per run (default 100).
timeoutSecsTimeout per website (default 15 s).

Output (one row per website)

{
"input": "nextjs.org",
"url": "https://nextjs.org/",
"finalUrl": "https://nextjs.org/",
"status": 200,
"ok": true,
"techNames": ["Next.js", "Vercel"],
"categories": { "framework": ["Next.js"], "hosting": ["Vercel"] },
"technologies": [{ "name": "Next.js", "category": "framework", "evidence": "html: /_next/static/" }],
"summary": "nextjs.org uses: Next.js, Vercel.",
"error": null,
"checkedAt": "2026-11-03T19:15:00.000Z"
}

(Illustrative example, not a real run.)

Limits

  • About 75 technologies. Tools that only load through client-side JavaScript after the page renders may be missed.
  • It analyzes the page you give it, not the whole site, and it does not search for websites that use a given technology.
  • Detections are signature-based and can be wrong. Check the evidence field.

Errors you may see

invalid-or-private-url, blocked-by-robots-txt, fetch-failed: ..., http-403 (and other HTTP codes), redirect-error-or-too-many-redirects.