★ Founding offer — sign up by Aug 16 and get Indie free for 30 days. No card. →
Competitive intelligence

Know if your competitor's launch actually landed.

Not just what shipped — whether anyone reacted. Every move scored against the reception it earned, cited to the source.

Start freeSee a live reportno credit card · free sector reports
Reception field — AI InfrastructureLAST 30D
LANDED LOUDSHIPPED TO SILENCEEACH DOT = ONE MOVE
TRACKING 0 COMPANIES · 0 SECTORS · 0+ REACTIONS COUPLED
AI infraFintechCloud securityDataDesignDevOpsAI coding
The product

Not a mockup. This is the dashboard.

Every competitor move scored as signals arrive — reception, momentum, and what shipped to silence, in one read.

ido.app / dashboard · engine live
IDØ dashboard — tracked competitors scored as signals arrive
What "landing" looks like

Everyone can see the move. Almost nobody measures the answer.

The same seven competitor moves, measured two ways. On the left, activity — a flat wall with no way to tell which mattered. On the right, the reception each one actually earned.

The same seven competitor moves shown twice: as an undifferentiated activity feed, and re-weighted by the public reception each earned — one landing with 214 reactions, and a high-significance move that drew zero, flagged as a quiet opening.
Fig. 1 — the same data, measured two ways
01How it works

Watch one move travel the whole engine.

A single competitor release goes from raw page to a ranked line in Friday's brief — diffed, scored, and weighed by how the market reacted. Nothing invented on the way.

fetch · supabase.com/changelog
# raw artifact captured
source: changelog  status: 200 ok
hash: 9f2a… (changed vs last snapshot)
diff · what's new
+ Introducing branching for every project
— normalised → ship event
score
significance Δ +1.42
magnitude
reaction · did it land
HN 214 pts · 96 comments  BSky 38
reception
● LANDED HARD — TOP 1% THIS QUARTER
friday brief
# this week, ranked by what landed
1. Supabase — branching · 214 rx
2. Neon — instant restore · 61 rx
3. Railway — pricing change · 0 rx (quiet)
The quiet opening

Two ships, identical significance. One earned an answer.

When a rival ships something real and the market says nothing, that silence isn't missing data — it's the opening. It's the line no other tracker can show you.

Two competitor ships scored identically at significance 1.98. The first draws 187 reactions across a 72-hour window and is marked landed; the second, swept over the same window and the same four sources, draws zero and is marked a quiet opening.
Fig. 2 — same score, same sweep, opposite answer
02The Landing Report

What shipped — and what landed.

One market report per sector. Every move scored against the reception it earned, ranked by what landed, cited to the source. Free to read.

03How we know it counts

Proving a reaction is about this launch — not merely this company.

Counting mentions is easy and useless. Every candidate has to be tied to the specific move that caused it — and the ones that don't belong get thrown out, by name.

334 candidate mentions from Hacker News, Bluesky, GitHub and press are tested against one launch. 214 couple to it; 120 are discarded and labelled by reason — 46 homonym, 31 self-promotion, 24 and 19 unrelated.
Fig. 3 — 214 coupled from 334 candidates; every discard named
Built for your stack

Point your AI agent at your competitive set.

A private MCP endpoint, coming to Pro — so Claude, Cursor, or your own agent can ask what a rival shipped and whether it landed, and get cited answers straight back. Coming soon on Pro.

agent · ido-mcp · competitor_reception
call competitor_reception("supabase")
# reactions coupled to each launch, cited
→ branching GA · 214 rx · landed hard
→ pricing change · 0 rx · quiet opening
cited news.ycombinator.com · bsky.app
04Where a move comes from

Two observations are all it takes.

We fetch the same page twice and diff it. The change is the move — no third-party archive, no dependency on anyone else's history.

Two snapshots of the same URL taken 28 days apart are overlaid. Four blocks are unchanged and one is new; that new block resolves into a typed ship event with significance 1.42, detected with no third-party archive.
Fig. 4 — change detection from our own snapshots
Build the better product

Every complaint the market already wrote.

When a rival ships, people say exactly what they didn't like. IDØ pulls the negative reactions coupled to each launch — so you can build what they didn't. New on Team.

HN · 96 comments

“The new pricing quietly tripled our bill.”

Coupled to a competitor's pricing change — 41 more in the same vein.

Bluesky

“Branching is great, but the docs are a maze.”

Coupled to their branching launch — a recurring theme, not a one-off.

GitHub · issue

“Cold starts are still 4s+ on the edge runtime.”

Coupled to the v3.2 release — 18 corroborating reports.

05Signal, not noise

Four things every brief tells you.

scored_event
Δ +1.42 significance
cited ↗ source

Scored moves

Every ship, hire, and price change scored — de-saturated, so big is rare.

reception
HN 214 · BSky 38
▓▓▓▓▓▓▓░ 88%

Did it land

Reactions coupled to the launch — the number nobody else measures.

quiet_openings
score 1.98 · 0 rx
shipped to silence

Quiet openings

Significant moves that landed silent — where the gap is.

friday_brief
ranked by reception
1 email, no dashboards

Weekly brief

The whole week, ranked by what landed, in one forwardable email.

06Under the hood
Deterministic by architecture

No LLM in the score. Nothing invented.

Public sources in, scored and cited moves out. The same read-only pipeline runs for every company you track — watch a move flow through it.

0 RX/CO

Reception is a targeting signal.

Loud sectors roar; quiet ones whisper. The report tells you which one you're actually competing in — so you stop guessing whether a launch mattered.

Your sector

Track your competitors. See what actually landed.

Start free and get the landing report for the space you compete in — built from live, cited data.