← Back to home
Comparison · Analytics

Amundsen vs Plotly

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

Amundsen vs Plotly: at a glance

FeatureAmundsenPlotly
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themesdata-catalog, metadata, maintenance-mode, monorepo-releasesai-app-building, plotly-cloud, metered-billing, custom-domains
Last editorial update8d ago1d 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 Plotly?

Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.

Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.

Read the full Plotly trajectory →

Amundsen vs Plotly: 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.

P
Plotly
ANALYTICS
6.3

Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.

◆ Current state

Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.

◆ Where it's heading

The Cloud releases are assembling the standard pieces of a hosting business in order — identity first (domain verification, explicitly framed as the step before SSO), then billing (viewer seats, then metered compute credits), and now production-grade serving (custom domains, automatic certificate renewal). Studio is being hardened as the authoring front end that feeds it: Universal Deployment pushed beyond Dash apps, credentials saved once and reused, a Winget channel to widen Windows installs, and in v0.0.86 a rebuilt session engine plus automatic retries so agent runs survive expired tokens. The two tracks converge on one funnel — author in Studio, deploy to Cloud, pay by compute consumed.

◆ Prediction

The Domain Verification entry names SSO as the next step and places it in the Enterprise tier, so single sign-on is the most likely Cloud release next. Studio should hold its one-to-two-week cadence, with the newly added app thumbnails pointing toward more work on browsing and organizing generated apps.

Alternatives to Amundsen and Plotly

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

See all Amundsen alternatives → · See all Plotly alternatives →

Recent activity from Amundsen and Plotly

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

  1. 15d agoPlotlyCustom Domains in Plotly Cloud
  2. 25d agoPlotlyPlotly Studio v0.0.85: Breadcrumbs & minor bug fixes
  3. 1mo agoPlotlyPlotly Studio v0.0.84: Faster AI, Saved Credentials, and Winget Support
  4. 1mo agoPlotlyCompute Modes and App Sizing in Plotly Cloud
  5. 1mo agoPlotlyPlotly Studio 0.0.83: Dash Update and macOS Fixes
  6. 2mo agoPlotlyPlotly Studio v0.0.82: Override for credential redaction, stability fixes
  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 Plotly?

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

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

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