Data Stack Index / v 02.06
Verified 2026·07·03
Send a correction
§ Coverage

Coverage.

What's indexed today, what's coming next, what's deliberately not indexed.

01
Currently indexed

The live roster.

Verticals

1

Clusters

3

Tools

24

Verified < 60d

10 / 24

Tool Cluster Status Last verified
Acceldata Quality & testing active 2026·05·30
Alation Catalog & discovery active 2026·07·03
Amundsen Catalog & discovery active 2026·07·03
Anomalo Quality & testing active 2026·05·08
Apache Atlas Catalog & discovery active 2026·07·03
Atlan Catalog & discovery active 2026·05·08
Bigeye Quality & testing active 2026·05·08
Cloudera Data Lineage (Octopai) Lineage & metadata acquired 2026·05·08
Collibra Catalog & discovery active 2026·07·03
Datafold Quality & testing active 2026·04·25
DataHub Catalog & discovery active 2026·05·08
dbt-expectations Quality & testing active 2026·05·30
Elementary Quality & testing active 2026·04·25
Great Expectations Quality & testing acquired 2026·05·08
IBM Manta Data Lineage Lineage & metadata acquired 2026·05·08
Marquez Lineage & metadata active 2026·05·08
Metaplane Quality & testing acquired 2026·05·30
Monte Carlo Quality & testing active 2026·04·25
OpenMetadata Catalog & discovery active 2026·05·08
Secoda Catalog & discovery acquired 2026·05·30
Select Star Catalog & discovery acquired 2026·07·03
Sifflet Quality & testing active 2026·05·30
Soda Quality & testing active 2026·05·08
Unity Catalog Catalog & discovery active 2026·05·08
02
Next up

The queue.

Tool entries the maintainer is actively writing or queued to write. No promised dates — these land when their schema can be fully populated from documentation. Anything already indexed above is filtered out at build time, so nothing appears here and in the live roster at once.

Quality & testing

Complete

Catalog & discovery

  • Castor

Lineage & metadata

Complete

03
Verticals being scoped

Beyond observability.

"Scoped" means the cluster taxonomy for the vertical is being drafted — what the sub-clusters are, what fields the schema needs, what counts as a legitimate entry. Tool entries are not yet imminent.

04
Deliberately out of scope

What we won't index.

Why coverage looks the way it does.

Coverage is built breadth-first within a vertical before moving to the next one. The bet: a complete data observability vertical is more useful than three half-populated verticals. The constraint: this is a one-person project, so depth comes faster than breadth, and breadth comes faster than horizontal expansion.

If you'd like a tool indexed sooner, send a note via corrections — though placement requests don't change the queue, awareness of teams actively evaluating a tool informs prioritization.