Omni
Omni ships weekly, and almost every week the headline item is an AI feature
A side-by-side editorial comparison of Amundsen and Axiom — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Axiom is rebuilding observability so an AI agent, not a human, can be the first user.
Axiom is a logs, traces and metrics platform that reached feature parity on the fundamentals earlier this year — metrics went generally available in March, dashboards got a full API, and Correlations tied the three data types together for investigations. The last two months have been spent thickening the console: collapsible dashboard sections, gauge elements, schema locking, Grafana as a query surface. Underneath that steady product work, a second track has been running the whole time, aimed at AI agents as operators rather than at humans.
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.
Axiom is a logs, traces and metrics platform that reached feature parity on the fundamentals earlier this year — metrics went generally available in March, dashboards got a full API, and Correlations tied the three data types together for investigations. The last two months have been spent thickening the console: collapsible dashboard sections, gauge elements, schema locking, Grafana as a query surface. Underneath that steady product work, a second track has been running the whole time, aimed at AI agents as operators rather than at humans.
That second track is now the main story. Metrics shipped queryable by agents through MCP and a dedicated skill, monitor management moved into the agent surface alongside the Grafana work, and evaluations arrived as both a live-traffic scoring feature and an agent-authored skill. The August release takes it to the account layer: an agent can now create its own Axiom organization and have a human claim it afterwards. Axiom is systematically removing the assumption that a person is present at each step.
The remaining human-gated surfaces are billing, access control, and dataset provisioning, and agent-created orgs makes those the obvious next targets. Expect the skills catalogue to keep growing into a set of task-shaped agent entry points rather than a single MCP endpoint.
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 Axiom.
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 Axiom alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Axiom 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. Axiom 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 Axiom alternatives in Analytics are ranked by recent ship velocity. Browse the "Axiom alternatives" section above for the current picks, or visit /alternatives/axiom for the full list with editorial commentary on each.