Fulcrum
Fulcrum ships an MCP server for AI-managed form building while Photo FastFill pushes toward general availability.
Comparison · Analytics
Amundsen vs OpenHouse
A side-by-side editorial comparison of Amundsen and OpenHouse — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:data-catalog
Amundsen vs OpenHouse: 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 OpenHouse?
OpenHouse's Iceberg view support hits a production compatibility snag, pausing the first major scope expansion
OpenHouse is an open-source Iceberg table management service shipping at a rapid patch cadence — multiple releases per week. The visible window is a mix of infrastructure groundwork (post-commit operations framework, lock reason metadata), maintenance (Iceberg dependency bumps), and a production incident response: HTS on prod-ltx1 saturated and refused connections because a functional index required exact upper-case expression matching, which a handwritten query missed.
Amundsen vs OpenHouse: 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.
OpenHouse
5.0ANALYTICS
OpenHouse's Iceberg view support hits a production compatibility snag, pausing the first major scope expansion
◆ Current state
OpenHouse is an open-source Iceberg table management service shipping at a rapid patch cadence — multiple releases per week. The visible window is a mix of infrastructure groundwork (post-commit operations framework, lock reason metadata), maintenance (Iceberg dependency bumps), and a production incident response: HTS on prod-ltx1 saturated and refused connections because a functional index required exact upper-case expression matching, which a handwritten query missed.
◆ Where it's heading
The revert in v0.5.498 tells the story: the entityType discriminator from v0.5.490 — framed in that release as 'the first PR toward supporting Iceberg views in OpenHouse' — was reverted alongside the HTS predicate fix, likely because the two changes interacted in production. View support would be OpenHouse's first material scope expansion (tables + views vs. tables only), giving it a fuller data catalog surface. The revert-and-redo pattern suggests the work is ongoing, not abandoned.
◆ Prediction
The Iceberg view support work will be re-merged once the HTS predicate and discriminator compatibility issues are resolved separately. The generic lock reason and post-commit operations framework suggest governance features for views are already being designed in parallel.
Alternatives to Amundsen and OpenHouse
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 OpenHouse.
Holistics
Holistics connects to warehouse-native semantic layers, shifting from semantic owner to governed exploration layer.
Tinybird
Tinybird builds out MCP tooling for LLM-driven data access while hardening its ingestion pipeline
Basedash
Basedash makes its MCP server writable — AI agents can now author dashboards on your behalf
OpenObserve
OpenObserve hits v1.0 GA with first-class AI Observability and SLOs, then stabilizes fast.
Lightdash
Lightdash ships AI-described custom chart types and a content governance overhaul in one week
See all Amundsen alternatives → · See all OpenHouse alternatives →
Recent activity from Amundsen and OpenHouse
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoOpenHouseOpenHouse v0.5.499: Iceberg core dependency update
- 3d agoOpenHouseOpenHouse v0.5.498: revert view discriminator and HTS predicate fix
- 3d agoOpenHouseOpenHouse v0.5.497: generic lock reason metadata and action-type declarations
- 3d agoOpenHouseOpenHouse v0.5.496: Iceberg core dependency update
- 6d agoOpenHouseOpenHouse v0.5.495: HTS predicate case fix after production saturation incident
- 8d agoOpenHouseOpenHouse v0.5.494: optimizer commit-stats extraction
- 2y 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 OpenHouse?
Both compete on the same themes — data-catalog — within Analytics. OpenHouse is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 OpenHouse?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenHouse is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 OpenHouse?
Top OpenHouse alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenHouse alternatives" section above for the current picks, or visit /alternatives/openhouse for the full list with editorial commentary on each.