RStudio
RStudio's first October patch is a branch merge, extending a long run of release-train upkeep.
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.
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 locks down its column-defaults capability flag as default values near completion.
OpenHouse shipped eleven builds (v0.5.529 to v0.5.539) in a week. The substantive work is a pluggable pre-commit check framework inside doCommit, built so column-default rules run on every commit path, and the first wiring of OpenHouseCatalog to the Views service. v0.5.539 makes the required-capability.column-defaults property immutable, and earlier builds added a tableExists endpoint, opt-in Spark SQL ALTER TABLE ... UNLOCK, and validation that blocks RTAS combined with WAP or replication.
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 locks down its column-defaults capability flag as default values near completion.
◆ Current state
OpenHouse shipped eleven builds (v0.5.529 to v0.5.539) in a week. The substantive work is a pluggable pre-commit check framework inside doCommit, built so column-default rules run on every commit path, and the first wiring of OpenHouseCatalog to the Views service. v0.5.539 makes the required-capability.column-defaults property immutable, and earlier builds added a tableExists endpoint, opt-in Spark SQL ALTER TABLE ... UNLOCK, and validation that blocks RTAS combined with WAP or replication.
◆ Where it's heading
LinkedIn's table catalog is moving business rules into the commit itself, so defaults, property rules and commit policies all reject the same way with clear 400s. Views and column default values are being built in parallel, and both are now past plumbing into user-facing guards. The team favors small, reversible steps.
◆ Prediction
Expect column default values and the Views client API to become usable end to end within the next few builds, with more PreCommitCheck rules registered by the tables service.
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.
OpenReplay
OpenReplay moves its Go backend to pgx v5 and patches vulnerable deps across 1.25–1.27.
Basedash
Basedash automations can now attach scheduled CSV exports to Slack and email.
OpenPanel
OpenPanel tags three more note-free builds in one evening, reaching 3.16.4.
Fulcrum
Fulcrum turns on Insights, its AI assistant for field data, for every customer.
Holistics
Holistics lets admins put a key dashboard on everyone's Home page.
See all Amundsen alternatives → · See all OpenHouse alternatives →
Recent activity from Amundsen and OpenHouse
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoOpenHousev0.5.543: Add integration tests for snapshot expiration with refs (#492)
- 1d agoOpenHousev0.5.542: column-default checks enforced in doCommit
- 1d agoOpenHousev0.5.541: [default values] Gate tables on capabilities the client declares (#848)
- 2d agoOpenHousev0.5.540: Spark integration test for column initial defaults
- 2d agoOpenHousev0.5.539: column-defaults capability property made immutable
- 4d agoOpenHousev0.5.538: Fix Gradle Git hook installation in worktrees (#858)
- 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?
They serve adjacent needs but don't currently overlap on shipped themes. 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.