# Tech Stack Detector – global stack + Salla, Zid & Arabic stores (`palgenius/tech-stack-detector`) Actor

BuiltWith / Wappalyzer alternative.
Detects CMS, frameworks, CDNs, analytics and e-commerce platforms with evidence and a confidence level for every hit. The only detector that recognises Salla, Zid, Matajer and Arabic/RTL stores.

- **URL**: https://apify.com/palgenius/tech-stack-detector.md
- **Developed by:** [Ali Alsaidi](https://apify.com/palgenius) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 domain analyseds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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.

```json
{ "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:

```json
{
  "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:

```json
{
  "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

# Actor input Schema

## `domains` (type: `array`):

Domains or URLs to analyse, e.g. example.com or https://shop.example.sa. Only the homepage is fetched.

## `maxDomains` (type: `integer`):

Stop after this many domains. Each domain analysed is one charged result; unreachable domains are not charged.

## `concurrency` (type: `integer`):

How many sites to fetch at once. Keep it polite.

## `requestTimeoutSecs` (type: `integer`):

How long to wait for a homepage before giving up and retrying.

## `maxRetries` (type: `integer`):

Retries with backoff on timeouts and 429/5xx responses.

## `respectRobotsTxt` (type: `boolean`):

Skip a homepage that robots.txt disallows. Leave this on unless you own the sites.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "wordpress.org"
  ],
  "maxDomains": 5,
  "concurrency": 5,
  "requestTimeoutSecs": 20,
  "maxRetries": 2,
  "respectRobotsTxt": true
}
```

# Actor output Schema

## `technologies` (type: `string`):

One item per domain, with the platform, the locale, every technology detected with its category, confidence and evidence, and notes about what could not be verified.

## `runSummary` (type: `string`):

Counts for this run: domains analysed and unreachable, fingerprint rules loaded, requests, retries and robots.txt blocks.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "apify.com",
        "wordpress.org"
    ],
    "maxDomains": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("palgenius/tech-stack-detector").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "domains": [
        "apify.com",
        "wordpress.org",
    ],
    "maxDomains": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("palgenius/tech-stack-detector").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "apify.com",
    "wordpress.org"
  ],
  "maxDomains": 5
}' |
apify call palgenius/tech-stack-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,palgenius/tech-stack-detector"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/vzCr8a4eqErN7mxXg/builds/IeqaSL9Vc1pyTqC23/openapi.json