Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Comparison · Analytics
Amundsen vs Chord
A side-by-side editorial comparison of Amundsen and Chord — release velocity, themes, recent moves, and the top alternatives to consider.
Amundsen vs Chord: at a glance
| Feature | Amundsen | Chord |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | data-catalog, metadata, maintenance-mode, monorepo-releases | cdp, agent-native, audience-building, conversational-analytics |
| Last editorial update | 15h ago | 5d ago |
| Website | Visit → | — |
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 Chord?
Chord rebuilt Copilot, renamed it, and let it start building the audiences it used to describe
Chord has spent four months rebuilding its assistant and is now finishing the rename. Copilot Next appeared as a limited preview in late June, then gained persistent chat history, shareable conversations, answers grounded in the customer's own business definitions, and background detection of whether feedback was positive or negative. As of this release the Copilot name is retired in favour of Ask Chord.
Amundsen vs Chord: 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.
Chord
6.3ANALYTICS
Chord rebuilt Copilot, renamed it, and let it start building the audiences it used to describe
◆ Current state
Chord has spent four months rebuilding its assistant and is now finishing the rename. Copilot Next appeared as a limited preview in late June, then gained persistent chat history, shareable conversations, answers grounded in the customer's own business definitions, and background detection of whether feedback was positive or negative. As of this release the Copilot name is retired in favour of Ask Chord.
◆ Where it's heading
The rename is the least interesting part; what changed is what the assistant is allowed to do. Answering questions about data became building audiences from a conversation and naming them, which moves Chord AI out of the reporting layer and into the operational path of the CDP. The grounding in business definitions and the visible sources are the trust scaffolding that had to land first before users would let it write anything.
◆ Prediction
If audience building was the first write action, activation is the obvious next one — pushing an audience to a destination or scheduling it rather than handing it back for a human to send. These entries do not yet show that step, so it stays a read on direction rather than a certainty.
Alternatives to Amundsen and Chord
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 Chord.
Omni
Omni ships weekly, and almost every week the headline item is an AI feature
OpenDataDiscovery
Four ODD Platform releases in two weeks, and not one of them changes the product
Apache Baremaps
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ
Deequ ships GitHub tags whose release notes are one commit message long
Marquez
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all Amundsen alternatives → · See all Chord alternatives →
Recent activity from Amundsen and Chord
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoChordNaming updates: Copilot is now ‘Ask Chord’
- 14d agoChordChord AI builds and names audiences from a conversation ⚡
- 27d agoChordChord AI answers grounded in your own business definitions
- 1mo agoChordCopilot Next adds persistent history and shareable chats
- 1mo agoChordA first look at Copilot Next
- 1mo agoChordChord AI detects feedback sentiment in your messages
- 1y 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 Chord?
They serve adjacent needs but don't currently overlap on shipped themes. Chord 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.
Is Amundsen better than Chord?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Chord 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.
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 Chord?
Top Chord alternatives in Analytics are ranked by recent ship velocity. Browse the "Chord alternatives" section above for the current picks, or visit /alternatives/chord for the full list with editorial commentary on each.