Omni
Omni ships weekly, and almost every week the headline item is an AI feature
A side-by-side editorial comparison of Amundsen and Hex — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Amundsen | Hex |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | data-catalog, metadata, maintenance-mode, monorepo-releases | agents, cli, mcp, model-routing |
| Last editorial update | 2h ago | 9h ago |
| Website | Visit → | — |
Amundsen's last release was a config flag, and the feed has been silent for two years
Amundsen ships as several separately versioned components — databuilder, metadata, frontend, common — cut from one repository, and the release feed shows the same changelog republished under three different component tags on the same afternoon. Reading past the tag names, the content is overwhelmingly dependabot bumps, Python compatibility-matrix maintenance and mypy upgrades, with real features appearing a couple of times a year. The final release, databuilder 7.5.1 in August 2024, contains exactly one change: a config option for implicit transactions in the neo4j extractor.
Hex is moving its agent out of the notebook and onto programmable surfaces.
Hex ships a fortnightly digest, and the through-line across the last ten is agent reach. The agent now runs from a CLI and API, appears inside Codex, acts as an MCP client against the user's own apps, can search the web, and can see the generative apps it builds. Alongside that, the model layer has become a customer-facing control: a picker, an admin-set default, Auto with visible attribution, and a rotating roster including Fable 5, Kimi K2.7, Claude Opus 5 and GPT-5.6.
Amundsen ships as several separately versioned components — databuilder, metadata, frontend, common — cut from one repository, and the release feed shows the same changelog republished under three different component tags on the same afternoon. Reading past the tag names, the content is overwhelmingly dependabot bumps, Python compatibility-matrix maintenance and mypy upgrades, with real features appearing a couple of times a year. The final release, databuilder 7.5.1 in August 2024, contains exactly one change: a config option for implicit transactions in the neo4j extractor.
The direction is contraction. Python 3.7 support was dropped and the matrix narrowed to 3.8 and 3.9 before 3.10 was cautiously added to everything except the metadata service, contributor names moved to emeritus status, and organisations were removed from the README's adopter list. What feature work exists is small and peripheral — a PowerBI logo, aggregated alerts, a gremlin proxy method — rather than anything touching how the catalog works. Nothing has been published since August 2024.
There is no signal in these entries of planned work, and a two-year silence following a single-flag release means the practical expectation is no further releases; the component version skew across databuilder, metadata and frontend is now frozen where it stopped.
Hex ships a fortnightly digest, and the through-line across the last ten is agent reach. The agent now runs from a CLI and API, appears inside Codex, acts as an MCP client against the user's own apps, can search the web, and can see the generative apps it builds. Alongside that, the model layer has become a customer-facing control: a picker, an admin-set default, Auto with visible attribution, and a rotating roster including Fable 5, Kimi K2.7, Claude Opus 5 and GPT-5.6.
Hex is positioning the agent as a component other systems call rather than a feature users visit. Governance is being built out in parallel — spend limits, credit usage controls, enterprise role-request controls, signed embedding — which is the pattern of a product preparing for programmatic usage it does not directly supervise. The generative-app surface is drifting the same way, from generated output toward editable, brandable, embeddable artifacts.
Expect the CLI and API surface to deepen before the notebook UI gains much, with more of Context Studio and app management reachable programmatically, and expect the spend and role controls to keep pace as headless usage grows.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Amundsen or Hex.
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
LinkedIn's Iceberg control plane, shipping one pull request per release.
See all Amundsen alternatives → · See all Hex alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hex is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Hex is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Amundsen alternatives in Analytics are ranked by recent ship velocity. Browse the "Amundsen alternatives" section above for the current picks, or visit /alternatives/amundsen for the full list with editorial commentary on each.
Top Hex alternatives in Analytics are ranked by recent ship velocity. Browse the "Hex alternatives" section above for the current picks, or visit /alternatives/hex for the full list with editorial commentary on each.