Tech Stack Change Monitor — CMS, CDN & Analytics Delta Feed avatar

Tech Stack Change Monitor — CMS, CDN & Analytics Delta Feed

Pricing

from $10.00 / 1,000 results

Go to Apify Store
Tech Stack Change Monitor — CMS, CDN & Analytics Delta Feed

Tech Stack Change Monitor — CMS, CDN & Analytics Delta Feed

Detects the CMS, ecommerce platform, JS framework, CDN, analytics and marketing tags a website runs, and remembers the last result per domain so a scheduled run only returns and charges for domains whose tech stack actually changed since the last check.

Pricing

from $10.00 / 1,000 results

Rating

0.0

(0)

Developer

Marco Jakobsen

Marco Jakobsen

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

11 days ago

Last modified

Categories

Share

Website Tech Stack Change Monitor

What it does

Point this Actor at a list of websites and it fingerprints each one — CMS, ecommerce platform, JS framework, CDN/hosting, analytics tags, marketing/chat widgets, payment scripts, consent banners and backend server — from the page's HTML and response headers. No headless browser, no login, just one fast HTTP request per domain.

The part that matters for scheduling: this Actor remembers what it found last time. Run it daily or hourly on the same watch-list and by default it only returns (and only charges you for) a domain when its tech stack actually changed since the last check — a competitor switching from WooCommerce to Shopify, dropping Google Analytics for a self-hosted tool, moving behind Cloudflare, adding a new chat widget. A quiet day costs nothing. That is the point: build a feed you can leave running, not a one-off report you have to remember to re-run. Typical uses: sales and SEO teams tracking a prospect or competitor list, agencies auditing client sites for platform migrations, investors watching a portfolio company's stack for signs of a rebuild.

Input

FieldTypeDefaultNotes
domainsarray of strings— (required)Plain domains (example.com) or full URLs, one per item.
onlyChangesbooleantrueWhen true, a domain identical to its last check is skipped — no row, no charge. The very first check of any domain always returns a baseline row. Set to false to always get a full row for every domain on every run.
stateStoreNamestringTECH-STACK-MONITOR-STATEName of the memory that stores each domain's last-seen stack. Use a different name per independent watch-list if you run more than one.
requestTimeoutSecsinteger20Per-site fetch timeout, 5–60 seconds.

See test-input.json in this Actor for a working example.

Output

One dataset row per domain that is returned (see onlyChanges above). Example row:

{
"domain": "example.com",
"url": "https://example.com/",
"checkedAt": "2026-09-22T08:12:00.000Z",
"httpStatus": 200,
"technologies": [
{ "name": "WordPress", "category": "CMS" },
{ "name": "Cloudflare", "category": "CDN" },
{ "name": "Google Analytics", "category": "Analytics" }
],
"added": ["Cloudflare"],
"removed": [],
"changed": true,
"isFirstCheck": false
}

A row where a fetch failed instead carries an error field and the last known technologies list, so a failing site does not silently vanish from your feed.

Pricing

Pay-per-event. You are charged $0.03 per result row returned (roughly $30 per 1,000 rows) — not per domain checked. A run over 50 domains where nothing changed on any of them produces zero rows and costs you nothing beyond the Actor start event. Scheduling this hourly on a watch-list you care about is the intended way to use it; unlike a flat per-run price, your bill tracks how much actually changed, not how often you looked.