Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Amundsen and Sprig — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Amundsen | Sprig |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 3.8 |
| Sparks · 30d | 0 | 0 |
| Top themes | data-catalog, metadata, maintenance-mode, monorepo-releases | user-research, ai-agents, surveys, personalization |
| Last editorial update | 13h ago | 3mo ago |
| Website | Visit → | — |
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.
Sprig is layering AI agents on top of every step of the survey pipeline.
Sprig has spent six months turning surveys into an AI-augmented research pipeline. November opened with Conversational Surveys and MaxDiff. Q1 added Attribute Piping for personalization, Display Logic on Enterprise, AI Follow-up Question for adaptive probes, and prototype testing improvements. April delivered AI Dynamic Questions and the Synthesize Agent's AI Study Report. Two distinct threads run in parallel: classic survey-tooling depth, and named AI agents that handle the parts humans used to.
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.
Sprig has spent six months turning surveys into an AI-augmented research pipeline. November opened with Conversational Surveys and MaxDiff. Q1 added Attribute Piping for personalization, Display Logic on Enterprise, AI Follow-up Question for adaptive probes, and prototype testing improvements. April delivered AI Dynamic Questions and the Synthesize Agent's AI Study Report. Two distinct threads run in parallel: classic survey-tooling depth, and named AI agents that handle the parts humans used to.
The product is moving from a survey runner to an end-to-end research workflow with agents at the question, response, and analysis layers. Enterprise gating shows up consistently on the AI features, signaling that AI is the upsell. Expect more named agents (segmentation, recommendation, trend tracking) and tighter ties between agent outputs and product analytics.
The next directional move likely connects agent insights back into product surfaces and growth experiments, closing the research-to-action loop. AI Dynamic Questions and Display Logic should converge into a single adaptive-flow primitive available beyond Enterprise.
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 Sprig.
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all Amundsen alternatives → · See all Sprig alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Sprig is currently shipping more aggressively (velocity 3.8 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Sprig is currently shipping more aggressively (velocity 3.8 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.
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 Sprig alternatives in Analytics are ranked by recent ship velocity. Browse the "Sprig alternatives" section above for the current picks, or visit /alternatives/sprig for the full list with editorial commentary on each.