← Back to home
Comparison · Analytics

Amundsen vs Whatagraph

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

Amundsen vs Whatagraph: at a glance

FeatureAmundsenWhatagraph
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesdata-catalog, metadata, maintenance-mode, monorepo-releasesmarketing-reporting, agencies, integrations, data-storage
Last editorial update15h ago12d ago
WebsiteVisit →

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 Whatagraph?

Marketing reporting quietly rebuilding itself around stored data instead of live API calls.

Whatagraph builds client reports for marketing agencies by pulling from dozens of ad, analytics, and call-tracking sources. The recent releases split into two groups. One keeps widening the source catalog — Snowflake as a warehouse source, WhatConverts lead data, and Ahrefs Rank Tracker as a keyword-level integration separate from the existing domain-level Ahrefs. The other attacks reliability: a Data Storage destination that pre-syncs data so widgets stop waiting on live APIs, the Basis integration rebuilt on that model, and automatic failover when the team member whose account owns a source loses access.

Read the full Whatagraph trajectory →

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

W
Whatagraph
ANALYTICS
5.0

Marketing reporting quietly rebuilding itself around stored data instead of live API calls.

◆ Current state

Whatagraph builds client reports for marketing agencies by pulling from dozens of ad, analytics, and call-tracking sources. The recent releases split into two groups. One keeps widening the source catalog — Snowflake as a warehouse source, WhatConverts lead data, and Ahrefs Rank Tracker as a keyword-level integration separate from the existing domain-level Ahrefs. The other attacks reliability: a Data Storage destination that pre-syncs data so widgets stop waiting on live APIs, the Basis integration rebuilt on that model, and automatic failover when the team member whose account owns a source loses access.

◆ Where it's heading

The reporting layer is being made boring in the good sense. Live-API reports break in ways an agency cannot explain to a client — a token expires, someone leaves, a widget goes blank mid-presentation — and the last few months answer each of those failure modes directly: store the data, align spend figures with the vendor's own billing totals, and silently switch to a colleague's credentials when one account stops working. The presentation work is following the same instinct, replacing per-metric threshold rules with automatic shading and consolidating scattered style settings into themes. Less configuration to maintain, fewer ways for a report to be wrong in front of a client.

◆ Prediction

Credential failover currently rescues a source when someone else on the team happens to have access; the gap it exposes is agency-owned connections that do not depend on an individual at all, which is where this thread points next.

Alternatives to Amundsen and Whatagraph

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

See all Amundsen alternatives → · See all Whatagraph alternatives →

Recent activity from Amundsen and Whatagraph

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

  1. 12d agoWhatagraphOne broken connection won't break your reports
  2. 13d agoWhatagraphClearer charts and tables, and a faster way to find the right template
  3. 18d agoWhatagraphTrack your keywords against competitors with Ahrefs Rank Tracker
  4. 1mo agoWhatagraphBasis rebuilt: faster data, cleaner numbers, per-client sources
  5. 1mo agoWhatagraphThemes settings, simplified
  6. 2mo agoWhatagraphWhatConverts data available on Whatagraph
  7. 1y 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 Whatagraph?

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

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

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