Tech Stack Detector (Lightweight Wappalyzer Alternative)
Pricing
from $50.00 / 1,000 results
Go to Apify Store
Tech Stack Detector (Lightweight Wappalyzer Alternative)
Input a website URL and get detected web technologies (CMS, analytics, frameworks, CDNs) based on HTML, headers and script patterns.
Pricing
from $50.00 / 1,000 results
Rating
0.0
(0)
Developer
tough_haircomb
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Security
Limited permissionsShare
Input a website URL and get detected web technologies (CMS, analytics, frameworks, CDNs) based on HTML, headers and script patterns.
Use cases
- Route leads to the right integration by quickly detecting WordPress/Shopify and common front-end frameworks.
- Add lightweight tech tags to a domain list before deeper audits.
- Verify analytics deployment (GA/GTM) across a set of owned sites by running once per URL.
Input
| Field | Type | Description |
|---|---|---|
url | string | Any public http(s) URL to analyze. |
timeoutSeconds | integer | Network timeout for each request. |
maxBytes | integer | Maximum HTML bytes to download from the final URL (to stay fast). |
maxRedirects | integer | Maximum number of redirects to follow. |
Output
One result per run.
| Field | Type | Description |
|---|---|---|
error | string | Null on success, otherwise an error message. |
url | string | The input URL. |
finalUrl | string | The final URL after following redirects. |
statusCode | integer | HTTP status code of the final response. |
title | string | Page title if found, otherwise null. |
technologies | array | List of detected technologies as strings. |
problems | array | Non-fatal problems encountered (e.g., truncated download). |
fetchedBytes | integer | Number of bytes read from the final response body. |
Example input
{"url": "https://example.com/","timeoutSeconds": 20,"maxBytes": 300000,"maxRedirects": 5}
Pricing
$0.05 per result. No subscription: you pay only for the runs you start.
Limits
- This is a lightweight detector with a small built-in signature set; it will miss niche technologies compared to full Wappalyzer/BuiltWith datasets.
- Detection is best-effort from HTML and response headers only; sites requiring JavaScript rendering may not expose their stack.