Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of Amundsen and OpenObserve — 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.
After its largest release, OpenObserve is patching the seams.
v0.92.0 landed on 7 August with 836 commits and three new product surfaces - synthetic monitoring, Workflows v1, and an expanded AI observability set - after a long RC series. The two releases since are small: v0.92.1 fixed alert HAVING clause typing and put the MCP server setup page on the OSS build, and v0.92.2 adds a compactor delay setting and backports an MCP 404 fix for deployments running under a base URI. The 0.91 line is still receiving its own backports.
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.
v0.92.0 landed on 7 August with 836 commits and three new product surfaces - synthetic monitoring, Workflows v1, and an expanded AI observability set - after a long RC series. The two releases since are small: v0.92.1 fixed alert HAVING clause typing and put the MCP server setup page on the OSS build, and v0.92.2 adds a compactor delay setting and backports an MCP 404 fix for deployments running under a base URI. The 0.91 line is still receiving its own backports.
OpenObserve is trying to become the whole monitoring stack rather than the storage layer under one. Synthetic checks, incident workflows, and SLO measurement each replace a separate tool, and incident ingestion from external alert sources hedges the migration path for teams that cannot switch all at once. The MCP work running alongside - open sourced, then given a setup page in the OSS build, then fixed for base-URI deployments - shows the same data being aimed at agent clients rather than dashboards.
The post-GA patches are still landing on the new surfaces, so expect another 0.92.x before feature work resumes - most likely hardening synthetic monitoring and Workflows, which are the two least-exercised additions.
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 OpenObserve.
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all Amundsen alternatives → · See all OpenObserve alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenObserve 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. OpenObserve 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 OpenObserve alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenObserve alternatives" section above for the current picks, or visit /alternatives/openobserve for the full list with editorial commentary on each.