← Back to home
Comparison · Analytics

Amundsen vs Dagster

A side-by-side editorial comparison of Amundsen and Dagster — release velocity, themes, recent moves, and the top alternatives to consider.

Amundsen vs Dagster: at a glance

FeatureAmundsenDagster
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesdata-catalog, metadata, maintenance-mode, monorepo-releasesorchestration, mcp, dbt-fusion, dagster-plus
Last editorial update3mo ago6h ago
WebsiteVisit →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.

Read the full Amundsen trajectory →

What is Dagster?

Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.

Dagster's 1.13 line ships weekly and follows two threads. dagster-dbt no longer installs dbt-core and gained a dbt v2 extra for the Fusion engine, while the UI keeps getting phone layouts and faster search and catalog pages. 1.13.30 on November 12 makes Python 3.11 the minimum and widens the Dagster+ MCP server to reading and toggling schedules and sensors and managing partitions.

Read the full Dagster trajectory →

Amundsen vs Dagster: editorial side-by-side

A
Amundsen
ANALYTICS
0.0

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.

D
Dagster
ANALYTICS
5.0

Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.

◆ Current state

Dagster's 1.13 line ships weekly and follows two threads. dagster-dbt no longer installs dbt-core and gained a dbt v2 extra for the Fusion engine, while the UI keeps getting phone layouts and faster search and catalog pages. 1.13.30 on November 12 makes Python 3.11 the minimum and widens the Dagster+ MCP server to reading and toggling schedules and sensors and managing partitions.

◆ Where it's heading

The Dagster+ MCP server has grown release by release, from launching runs without a code location in September to controlling schedules, sensors and partitions now. Combined with the dbt split, Dagster is trimming legacy dependencies while making the orchestrator something an agent can operate, not just a person in the UI.

◆ Prediction

The MCP server still lacks write access to things like backfills and alert policies, so expanding it there is the most visible next step; further Python and dbt version floors are likely to follow the 3.10 cut.

Alternatives to Amundsen and Dagster

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 Dagster.

See all Amundsen alternatives → · See all Dagster alternatives →

Recent activity from Amundsen and Dagster

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoDagster1.13.30: Python 3.11 minimum, more Dagster+ MCP tools
  2. 8d agoDagster1.13.29: more mobile layouts, faster search and catalog
  3. 14d agoDagster1.13.28: dbt v2 extra and retries for failed code locations
  4. 18d agoDagster1.13.27: mobile run details, bounded BigQuery Insights scans
  5. 1mo agoDagster1.13.26: dagster-dbt stops installing dbt-core
  6. 1mo agoDagster1.13.25: phone layout for the Dagster UI, ECS run resumes
  7. 2y agoAmundsenDatabuilder 7.5.1 adds implicit-transaction config for the neo4j extractor
  8. 2y agoAmundsenDatabuilder 7.5.0 is dependency bumps and a Python 3.10 matrix
  9. 2y agoAmundsenMetadata 3.13.0 adds aggregating alerts and a gremlin proxy lookup
  10. 2y agoAmundsenFrontend 4.3.0 republishes the same changelog under a second tag
  11. 2y agoAmundsenCommon 0.32.0 republishes the same changelog under a third tag
  12. 2y agoAmundsenMetadata 3.12.3 clears frontend dependency vulnerabilities

Frequently asked questions

What is the difference between Amundsen and Dagster?

They serve adjacent needs but don't currently overlap on shipped themes. Dagster 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 Dagster?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dagster 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 Dagster?

Top Dagster alternatives in Analytics are ranked by recent ship velocity. Browse the "Dagster alternatives" section above for the current picks, or visit /alternatives/dagster for the full list with editorial commentary on each.