OpenObserve
OpenObserve ships v1.0.0 GA after a five-RC stabilization run, making its enterprise observability play official.
A side-by-side editorial comparison of Amundsen and dbt Core — 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.
dbt 2.0 ships stable with an official OSS/proprietary split and agentic skill loading
dbt shipped its 2.0 stable release on September 16, the first generational version milestone in the project's history. The release formally renames the CLI: what was 'Fusion/dbt-core' becomes 'dbt' (proprietary) and 'dbt-oss' (open source)—a structural separation that existed in practice but now has an official name. New capabilities include native Databricks metric view materializations, a ClickHouse ADBC driver, and AgentSkill installation from dbt packages gated on a new ai_provider flag.
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.
dbt shipped its 2.0 stable release on September 16, the first generational version milestone in the project's history. The release formally renames the CLI: what was 'Fusion/dbt-core' becomes 'dbt' (proprietary) and 'dbt-oss' (open source)—a structural separation that existed in practice but now has an official name. New capabilities include native Databricks metric view materializations, a ClickHouse ADBC driver, and AgentSkill installation from dbt packages gated on a new ai_provider flag.
The OSS/proprietary split is the architectural move that matters most. dbt Labs is building a commercial product on top of dbt-oss, and 2.0 makes that boundary explicit to the ecosystem. The AgentSkills integration signals that dbt sees AI-assisted data transformation as a core product direction—not an add-on. The ai_provider flag is the gating mechanism through which commercial features will increasingly be differentiated.
Expect near-term differentiation between dbt (proprietary) and dbt-oss at the feature level, with AI-native capabilities—AgentSkills, model suggestions, lineage intelligence—landing exclusively in the commercial tier first.
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 dbt Core.
OpenObserve ships v1.0.0 GA after a five-RC stabilization run, making its enterprise observability play official.
Fulcrum ships MCP server and AI Toolkit to let AI assistants build and query field data forms
Holistics builds AI governance and docs-as-analytics in parallel, shipping both weekly
OpenHouse breaks ground on Iceberg views while tightening storage lifecycle and authorization
Lightdash is cutting its dbt dependency and building AI-powered authoring into every layer of its BI stack.
Keboola's Kai AI assistant hits GA, completing the pivot from data platform to AI-native pipeline orchestration layer.
See all Amundsen alternatives → · See all dbt Core alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 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. dbt Core is currently shipping more aggressively (velocity 7.5 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 dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.