Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Comparison · Analytics
Amundsen vs Sigma Computing
A side-by-side editorial comparison of Amundsen and Sigma Computing — release velocity, themes, recent moves, and the top alternatives to consider.
Amundsen vs Sigma Computing: 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 Sigma Computing?
Sigma is moving data modeling out of its own UI and into the terminal.
Sigma shipped a plugin for Claude Code that builds complete data models — metrics, relationships, columns, descriptions — from the terminal, alongside guidance on building Sigma Agents that handle schema discovery and model creation against Snowflake semantic views. Automated Actions landed for running reports, refreshing data, calling APIs, and triggering agents on a schedule, and embedded analytics gained bidirectional JavaScript events over postMessage.
Amundsen vs Sigma Computing: 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.
Sigma Computing
0.0ANALYTICS
Sigma is moving data modeling out of its own UI and into the terminal.
◆ Current state
Sigma shipped a plugin for Claude Code that builds complete data models — metrics, relationships, columns, descriptions — from the terminal, alongside guidance on building Sigma Agents that handle schema discovery and model creation against Snowflake semantic views. Automated Actions landed for running reports, refreshing data, calling APIs, and triggering agents on a schedule, and embedded analytics gained bidirectional JavaScript events over postMessage.
◆ Where it's heading
Two directions are converging on the same idea: Sigma as a system that runs without someone watching it. Automated Actions handles the scheduled half, the Claude Code plugin and agent guidance handle the authored half, and the embedding work makes Sigma a component inside someone else's application rather than a destination. The recurring argument in the writing — that read-only dashboards are no longer enough — is consistent across all three.
◆ Prediction
Expect the agent surface to extend from model creation into model maintenance, since schema drift is what makes hand-built models rot. The embedded and automation threads suggest write-back workflows will keep deepening.
Alternatives to Amundsen and Sigma Computing
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 Sigma Computing.
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 Sigma Computing alternatives →
Recent activity from Amundsen and Sigma Computing
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoSigma ComputingIntroducing the Sigma Plugin for Claude Code ⚡
- 3mo agoSigma ComputingHow to Build a Sigma Agent for Data Modeling in Your Warehouse
- 3mo agoSigma ComputingJavascript Events in Embedded Analytics with Sigma
- 3mo agoSigma ComputingIntroducing Automated Actions: Build Workflows that Run on Autopilot ⚡
- 3mo agoSigma ComputingIntroducing Automated Actions: Build Workflows that Run on Autopilot
- 3mo agoSigma ComputingWhy Your Customers Have Outgrown Read-Only Dashboards
- 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 Sigma Computing?
They serve adjacent needs but don't currently overlap on shipped themes. Amundsen and Sigma Computing are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Amundsen better than Sigma Computing?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Amundsen and Sigma Computing are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 Sigma Computing?
Top Sigma Computing alternatives in Analytics are ranked by recent ship velocity. Browse the "Sigma Computing alternatives" section above for the current picks, or visit /alternatives/sigma-computing for the full list with editorial commentary on each.