For investors, funds and corporate development

Check the footprint, not the pitch deck

Before you back a technology or SaaS company, count its real install base yourself. Market share, competitor position and adoption momentum across 406M live sites, as one file you can query. The technology set is €159 and a plain census starts at €29. A free 10,000-row sample needs no account.

Get a free 10K sample See the €159 technology set

What this signal is, and what it is not →

406Mlive sites you can check yourself
3,042technologies tracked across the web
€159full detection set, one payment
10Kfree sample rows, no account

Four checks you would run on a target

Real queries on the real schema. Answer them from the raw file instead of trusting a slide, or paying a research platform for the same count.

DomainTechnologiesCountry by IPTLDPR valueHarmonic valueDNS Status

How big is it, really

The headline number for a memo. How many live sites run one product, as a share of the web we track. Runs on the €159 technology set. The field ships in two shapes, so normalize it first, then it is safe to test.

bash + jq
zstdcat webatla-technologies-2026-07-10.jsonl.zst |
jq -r 'def techs: (.Technologies // []) | if type=="object" then keys else . end;
    if (techs | index("Shopify")) then "runs" else "no" end' |
sort | uniq -c

One product against its rivals

Competitive position on a single measure. Count every site running each competitor in the category, side by side, as a share of the web. The number the founder will not put on a slide.

duckdb
WITH t AS (
  SELECT CASE json_type("Technologies")
           WHEN 'ARRAY'  THEN json_extract_string("Technologies", '$[*]')
           WHEN 'OBJECT' THEN json_keys("Technologies")
           ELSE []::VARCHAR[] END AS techs
  FROM read_json('webatla-all-data-2026-07-10.jsonl.zst',
       format='newline_delimited', compression='zstd',
       columns={'Technologies':'JSON'})
), total AS (SELECT count(*) AS n FROM t)
SELECT tech, count(*) AS sites,
       round(100.0*count(*)/(SELECT n FROM total), 3) AS pct_of_web
FROM t, unnest(t.techs) AS u(tech)
WHERE tech IN ('Shopify','WooCommerce','Wix','Squarespace','BigCommerce')
GROUP BY tech ORDER BY sites DESC;

Which markets it owns

Reach and concentration for a TAM read. Where a product is actually deployed, by hosting country, from the resolved IP. Swap the name to profile any tool.

duckdb
SELECT "Country by IP" AS country, count(*) AS sites
FROM read_json('webatla-all-data-2026-07-10.jsonl.zst',
       format='newline_delimited', compression='zstd',
       columns={'Technologies':'JSON', 'Country by IP':'VARCHAR'})
WHERE country IS NOT NULL
  AND list_contains(
        CASE json_type("Technologies")
          WHEN 'ARRAY'  THEN json_extract_string("Technologies",'$[*]')
          WHEN 'OBJECT' THEN json_keys("Technologies")
          ELSE []::VARCHAR[] END, 'Shopify')
GROUP BY country ORDER BY sites DESC LIMIT 15;

Which way it is moving

Momentum, built from your own snapshots. Count adoption in two dated exports and diff them. The net change is the signal a single slide can never show you. Positive means it is winning new sites.

bash + jq
# count adoption in each monthly export, then diff
for f in webatla-all-data-2026-06-01 webatla-all-data-2026-07-01; do
  zstdcat "$f.jsonl.zst" |
  jq -r 'def techs: (.Technologies // []) | if type=="object" then keys else . end;
         techs[]' |
  LC_ALL=C sort | uniq -c |
  awk '{c=$1;$1="";sub(/^ /,"");print $0"\t"c}' |
  LC_ALL=C sort -t$'\t' -k1,1 > "$f.tsv"
done
# tech, june, july, net change (biggest gains first)
LC_ALL=C join -t$'\t' webatla-all-data-2026-06-01.tsv webatla-all-data-2026-07-01.tsv |
awk -F$'\t' '{printf "%s\t%d\t%d\t%+d\n",$1,$2,$3,$3-$2}' | sort -t$'\t' -k4 -rn

Every recipe runs on the free sample and on the full file with no change. Spot-check any row against the live site before you rely on it.

What this signal is, and what it is not

The candor a sophisticated buyer expects. Read it before you cite a number.

What the footprint proves

  • The real install base and market share, counted across the whole web
  • Competitive position, one product measured against its rivals the same way
  • Geographic reach, where a tool is actually deployed
  • Direction of travel, once you compare two dated snapshots

These are external facts you can recount from the raw file, so the number holds up in an investment memo instead of resting on trust.

Start with the technology set

What it is not

  • Not revenue, ARR or private financials. It sizes the footprint, not the P&L
  • Not the data room. It is the independent check you run against what the company tells you
  • Detection reads public-web technology. A purely internal or backend-only tool leaves no signature to count

Size the deployment, not the company's books. Used that way, it is one of the few diligence inputs you can verify without asking anyone's permission.

See how it is counted

Why a file beats a data subscription

For the kind of number you have to defend in a room.

Independent and verifiable

You count it yourself from the raw file. The figure in your memo is one you can reproduce and defend, not a black box you cite on someone else's word.

The whole market, not a panel

Every domain we track, so a market-share denominator is the real one. No sampled index to caveat when a partner asks how you got the number.

A whole category in one pass

Screen every competitor in a single query instead of buying one company profile at a time. Map the field before the first call.

Your own cadence

Buy two dated snapshots and diff them to build the exact adoption trend you need, on your schedule, not a vendor's release calendar.

One payment, you keep the file

€159 once for the technology set, not a yearly platform seat. The data sits on your own hardware with no per-query meter reading over your shoulder.

Board-safe by design

Public web, DNS and technology records. No contact PII: no names, emails or phone numbers. Nothing that complicates a compliance sign-off.

Questions from the investment committee

Answered without hedging.

Is this revenue or ARR data?

No. It is the external technology footprint: how many live sites run a given tool, where, and which way that number is moving. It is the install base you can verify yourself, the check you run against the revenue story, not the story itself.

Can I trust the detection?

It reads what a site exposes on the public web, the same client and server fingerprints a browser sees. It will not catch a purely internal tool with no web signature, and we say so rather than pad the count. What it reports, you can spot-check on any domain in the file.

Can I measure the trend, not just today?

Each file is one dated snapshot. Buy two, count the same technology in each, and the difference is your adoption momentum. We also publish a year-over-year read per technology on every technology page. The last recipe above builds the series from your own snapshots.

Can I use this in a memo or share it internally?

Yes. The numbers, charts and conclusions you compute are yours, to circulate in a memo or to your partners. Redistributing the raw rows themselves, whole or in large part, needs a written agreement. Selling what you made from it is fine, selling our file is the part to talk to us about.

How current is it?

The pipeline rebuilds and every export is dated in the filename. You are checking a footprint from a known date, not a cache of unknown age.

Run the check before the next call

10,000 real rows, no account. If the footprint holds up, the full technology set is €159 and every column joined is €599.