Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Comparison · Analytics
Amundsen vs Pirsch Analytics
A side-by-side editorial comparison of Amundsen and Pirsch Analytics — release velocity, themes, recent moves, and the top alternatives to consider.
Amundsen vs Pirsch Analytics: at a glance
| Feature | Amundsen | Pirsch Analytics |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 3.8 |
| Sparks · 30d | 0 | 0 |
| Top themes | data-catalog, metadata, maintenance-mode, monorepo-releases | privacy analytics, bot filtering, maintenance, dashboards |
| Last editorial update | 11h ago | 3mo ago |
| Website | 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.
What is Pirsch Analytics?
Pirsch ships a tight maintenance cadence — bot filtering, dashboard polish, and dependency hygiene.
Pirsch is releasing every few days with very small payloads. The April cluster centers on bot detection — improved filters in 2.14.10 and 2.14.12, plus a referrer-parameter bot fix in 2.14.11. March added dashboard creation settings, an option to hide the UTM panel, expiration times on access links, and a referrer blacklist update. Earlier in February, email reports gained a start date and the Fathom Analytics importer was updated.
Amundsen vs Pirsch Analytics: 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.
Pirsch Analytics
3.8ANALYTICS
Pirsch ships a tight maintenance cadence — bot filtering, dashboard polish, and dependency hygiene.
◆ Current state
Pirsch is releasing every few days with very small payloads. The April cluster centers on bot detection — improved filters in 2.14.10 and 2.14.12, plus a referrer-parameter bot fix in 2.14.11. March added dashboard creation settings, an option to hide the UTM panel, expiration times on access links, and a referrer blacklist update. Earlier in February, email reports gained a start date and the Fathom Analytics importer was updated.
◆ Where it's heading
Pirsch is in steady operational mode — defending against bots, polishing dashboard surfaces, and keeping dependencies current. The Fathom importer updates and email-report work are the only signs of growth-oriented investment; otherwise the cadence is custodial. The product feels like it's competing on reliability and privacy rather than feature surface.
◆ Prediction
Expect bot-filter work to continue (this is an arms race for any analytics provider) and the Fathom importer to keep getting attention as Fathom users churn. Larger directional moves aren't visible in the feed; the next signal would be a real new product surface — funnels v2, server-side eventing, or an AI insights panel.
Alternatives to Amundsen and Pirsch Analytics
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 Pirsch Analytics.
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 Pirsch Analytics alternatives →
Recent activity from Amundsen and Pirsch Analytics
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoPirsch Analyticsv2.14.12: improved bot filters
- 3mo agoPirsch Analyticsv2.14.11: fix bot filtering by referrer parameter
- 3mo agoPirsch Analyticsv2.14.10: bot filter improvements and graph fix
- 5mo agoPirsch Analyticsv2.14.9: referrer blacklist update
- 5mo agoPirsch Analyticsv2.14.8: fix account deletion with pinned dashboards
- 5mo agoPirsch Analyticsv2.14.7: dashboard settings, UTM panel toggle, link expiration
- 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 Pirsch Analytics?
They serve adjacent needs but don't currently overlap on shipped themes. Pirsch Analytics 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.
Is Amundsen better than Pirsch Analytics?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pirsch Analytics 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.
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 Pirsch Analytics?
Top Pirsch Analytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Pirsch Analytics alternatives" section above for the current picks, or visit /alternatives/pirsch for the full list with editorial commentary on each.