OpenDataDiscovery
Four ODD Platform releases in two weeks, and not one of them changes the product
Comparison · Analytics
Amundsen vs Omni
A side-by-side editorial comparison of Amundsen and Omni — release velocity, themes, recent moves, and the top alternatives to consider.
Amundsen vs Omni: at a glance
What is Amundsen?
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.
What is Omni?
Omni ships weekly, and almost every week the headline item is an AI feature
Omni publishes a dated weekly digest whose body is a single line listing that week's items, so each entry compresses several releases into a sentence. Across seven consecutive weeks the pattern is unmistakable: AI-powered semantic model generation reaching general availability, AI Routines creatable from chat and deliverable to Slack, AI model suggestion endpoints, AI credit controls scoped to embed entity groups and individual users, AI Evals support on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The non-AI items are steady BI plumbing — OAuth and GitHub App authentication for dbt connections, mobile dashboard settings, map legend positioning, presentation mode.
Amundsen vs Omni: editorial side-by-side
Amundsen
0.0ANALYTICS
Amundsen's last release was a config flag, and the feed has been silent for two years
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Omni
6.3ANALYTICS
Omni ships weekly, and almost every week the headline item is an AI feature
◆ Current state
Omni publishes a dated weekly digest whose body is a single line listing that week's items, so each entry compresses several releases into a sentence. Across seven consecutive weeks the pattern is unmistakable: AI-powered semantic model generation reaching general availability, AI Routines creatable from chat and deliverable to Slack, AI model suggestion endpoints, AI credit controls scoped to embed entity groups and individual users, AI Evals support on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The non-AI items are steady BI plumbing — OAuth and GitHub App authentication for dbt connections, mobile dashboard settings, map legend positioning, presentation mode.
◆ Where it's heading
Two things are happening in parallel and they are related. Omni is pushing AI into the modelling layer rather than only the query layer, which is what semantic model generation reaching GA signifies — the artifact that normally takes an analytics engineer weeks is being generated. At the same time it is building the commercial and access controls that AI features require: credit limits per user and per embed entity group arrived within weeks of the AI capabilities that consume them. The MCP work points at a third direction, exposing Omni's content to external agents rather than only serving its own chat.
◆ Prediction
Credit controls appearing so soon after the AI features suggests consumption limits will keep expanding to cover newer surfaces, and with searchDashboards shipped as an MCP tool, more of Omni's catalog is the obvious next thing to expose that way.
Alternatives to Amundsen and Omni
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 Omni.
Apache Baremaps
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ
Deequ ships GitHub tags whose release notes are one commit message long
Marquez
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
OpenHouse
LinkedIn's Iceberg control plane, shipping one pull request per release.
OR-Tools
Google's solver suite where nearly every release note is really about CP-SAT.
See all Amundsen alternatives → · See all Omni alternatives →
Recent activity from Amundsen and Omni
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18h agoOmniOmni adds presentation mode and a searchDashboards MCP tool
- 7d agoOmniOmni adds AI credit controls per user and embed entity group
- 14d agoOmniAI semantic model generation goes generally available in Omni ⚡
- 21d agoOmniOmni adds AI suggestion endpoints and OAuth for database connections
- 28d agoOmniOmni brings AI routines to Slack and adds in-app MCP settings
- 1mo agoOmniOmni adds AccessBoost for Apps and dbt deploy-token auth
- 1y agoAmundsenDatabuilder 7.5.1 adds implicit-transaction config for the neo4j extractor
- 2y agoAmundsenDatabuilder 7.5.0 is dependency bumps and a Python 3.10 matrix
- 2y agoAmundsenMetadata 3.13.0 adds aggregating alerts and a gremlin proxy lookup
- 2y agoAmundsenFrontend 4.3.0 republishes the same changelog under a second tag
- 2y agoAmundsenCommon 0.32.0 republishes the same changelog under a third tag
- 2y agoAmundsenMetadata 3.12.3 clears frontend dependency vulnerabilities
Frequently asked questions
What is the difference between Amundsen and Omni?
They serve adjacent needs but don't currently overlap on shipped themes. Omni 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.
Is Amundsen better than Omni?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Omni 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.
What are the best alternatives to Amundsen?
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.
What are the best alternatives to Omni?
Top Omni alternatives in Analytics are ranked by recent ship velocity. Browse the "Omni alternatives" section above for the current picks, or visit /alternatives/omni for the full list with editorial commentary on each.