WHAT IT IS
A catalog of specs is a list. A knowledge graph is a set of relationships.
Most product sites store a spec sheet per model and stop there. We store two things and the link between them: a product-model record — one durable entry per model, its identity, protocols, subscription reality, and lifecycle — and a compatibility graph that connects each model to the ecosystems and hardware it actually works with.
That link is the asset. It's what lets the checker answer "will these work together in my home" instead of reciting what each box claims on its own. Every product is a node; every "works with Alexa," every "needs a Thread border router," every "cloud link removed" is an edge — and every edge carries a source.
It's built to be read by people and by machines — the same graph powers the human checker and a public feed for AI agents.
Nodes — the models
122 product records across 12 categories, each with a stable identity that survives renames, generations, and supersessions.
Edges — the compatibility
610 integration cells linking models to 5 ecosystems, plus protocol and hub-dependency edges — the "picks that work together" relationships.
Provenance — the trust
814 source entries. A claim without a citation isn't in the graph; an unknown we haven't confirmed says so plainly.
THE GRAPH TODAY · LIVE FIGURES
The graph, by the numbers.
Not a marketing snapshot — the actual shape of the catalog right now, including the parts we haven't finished confirming. These numbers are generated from the live data on every build.
Why we show the grey. "Unknown" and "confirmed none" are separate states here on purpose. A confident-looking guess is worse than an honest gap — so an edge we haven't verified is never dressed up as a "no."
PROVENANCE
Why every claim in the graph holds up.
Open any record and each fact traces to where it came from. Here's a real one from the catalog, annotated.
A source, or it doesn't ship
Every edge cites where it came from — a vendor spec, an ecosystem developer doc, a standards registry — not "our research."
Honest unknowns
We distinguish "we checked, it's a no" from "we haven't checked." The graph carries both, labeled.
Negatives are claims too
"Needs the Hue Bridge" or "no HomeKit support" is evidence we record and cite, not silence.
Made for agents
We're converting prose citations to structured, fetchable source URLs so an AI agent — and one day an automated watcher — can re-check our work.
WHAT'S LIVE · WHAT'S COMING
The catalog's promise is shifting from complete to true.
We're honest about what the machinery does today versus what it's built to do next.
Working today
- ✓Source-tracked records — 122 models, every claim cited
- ✓The compatibility graph — 610 model-to-ecosystem edges powering the checker
- ✓Honest unknowns & evidenced negatives — gaps and "no"s are labeled, not hidden
- ✓Machine-readable feed — the same graph, published for AI agents
Being built next
- →Automated change detection — a watcher that re-checks each cited source and flags what moved (designed, not yet running)
- →Graph health monitoring — coverage, staleness, and unknown-rate tracked over time
- →"Compatibility changed" alerts — the day a firmware update breaks a pairing, you'd hear it
Straight answer: today the graph is kept current by hand and by scheduled research — not by an automated system, and a "verified" date is a record of when we last looked, not a guarantee nothing has changed since. Change detection is our stated direction. The day it goes live, this page will say so.
Put a question to the graph.
Pick what you own, or what you're about to buy, and see whether it all works together — sourced, not guessed.
Want the methodology — including what we learned from the formal provenance standards and where they fall short for product truth? Read how we're building the Provenance Knowledge Graph →