Tech Stack Detector – global stack + Salla, Zid & Arabic stores

A BuiltWith and Wappalyzer alternative that detects the tech stack behind any domain — the e-commerce platform, CMS, frameworks, CDN, analytics, chat and more — including the Gulf platforms other tools miss: Salla, Zid, Matajer and Arabic-first stores. Every detection carries the evidence it was based on, where that evidence was found, and a confidence level — so you can judge a result instead of trusting it.

{ "domains": ["example.com", "shop.example.sa"], "maxDomains": 100 }

What makes this one different

1. Evidence, not assertions. Most detectors hand you a bare list of names. Every row here says what matched:

{
  "name": "Salla",
  "category": "ecommerce-platform",
  "confidence": "high",
  "foundOn": "cookie",
  "evidence": "__said cookie: __said"
}

2. It tells you when it cannot know. If a site loads Google Tag Manager, ad pixels fired through it are invisible to any HTML-only scanner. Instead of reporting "no Meta Pixel", this Actor says so:

Google Tag Manager is present, so ad pixels fired through it are not visible in static HTML. Absence of a pixel here is not evidence it is missing.

3. Gulf platforms other tools miss. Salla, Zid and Matajer power a large share of Saudi and wider Gulf e-commerce and are poorly covered by global tools. All three are detected here, each verified against real storefronts, alongside Arabic locale and RTL signals.

4. It refuses to guess. Payment gateways are reported at medium confidence at best, because most only appear at checkout. Hosting location is not reported at all: a CDN edge code tells you where the crawler is, not where the site runs.

Output

One item per domain:

{
  "domain": "https://rashof.com",
  "finalUrl": "https://rashof.com/",
  "status": 200,
  "fetched": true,
  "platform": "Salla",
  "locale": { "lang": "ar", "dir": "rtl", "rtl": true, "arabic": true },
  "technologies": [
    { "name": "Salla", "category": "ecommerce-platform", "confidence": "high",
      "foundOn": "html", "evidence": "Salla CDN: cdn.salla.network" },
    { "name": "Cloudflare", "category": "cdn", "confidence": "high",
      "foundOn": "header", "evidence": "CF-RAY header: cf-ray: ..." }
  ],
  "notes": ["Google Tag Manager is present, so ad pixels ..."]
}

A domain that could not be fetched comes back with fetched: false and the reason — and is not charged.

Input

Field	Type	Default	What it does
domains	array	—	Domains or URLs to analyse (required). Only the homepage is fetched
maxDomains	integer	100	Hard ceiling on how many domains a run analyses
concurrency	integer	5	How many sites to fetch at once
requestTimeoutSecs	integer	20	Per-request timeout
maxRetries	integer	2	Retries with backoff on timeouts and 429/5xx
respectRobotsTxt	boolean	true	Skip homepages that robots.txt disallows

Pricing

$5 per 1,000 domains analysed ($0.005 each). A domain that could not be fetched is returned with the reason and is not charged, and maxDomains caps what a run can cost.

What it covers

Nearly 390 technologies across e-commerce platforms, CMS and site builders, JavaScript frameworks, UI and fonts, CDN and hosting, analytics and tag managers, ad pixels, consent tools, chat and support, marketing, reviews and search, monitoring, A/B testing, video, maps, auth, security and CAPTCHA, and payments — plus the Gulf layer: Salla, Zid, Matajer, Arabic web fonts, RTL markers and Hijri date libraries.

Honest limits

• Homepage only. Anything that loads at checkout is usually not visible, which is why payment gateways are capped at medium confidence.
• Tag managers hide things. When GTM is present, treat a missing pixel as unknown, not absent.
• Single-page apps hide more. A site that renders client-side may expose little in its HTML. A fetched: true with few technologies can mean a thin page, not a thin stack.
• Hosting location is not reported. It cannot be answered from HTML and headers.
• Anti-bot pages. If a site serves a challenge instead of its homepage, you get fetched: false and the reason, never a confident empty result.

Good for

• Sales prospecting: find every store on a given platform, with proof
• Market research: platform share across a country or a vertical, including the Gulf
• Competitive checks: what a rival's site actually runs
• Lead qualification: spot the stack before a call