Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Amundsen and Piwik PRO — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Amundsen | Piwik PRO |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | data-catalog, metadata, maintenance-mode, monorepo-releases | web-analytics, gdpr, scheduled-reports, google-ads-integration |
| Last editorial update | 15h ago | 3mo ago |
| Website | Visit → | — |
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.
Piwik PRO ships steady fortnightly fix releases with quiet integration improvements.
Recent releases (18.59 through 18.66) follow a tight bi-weekly cadence dominated by analytics bug fixes — chart tooltips, scheduled-report PDF rendering, sorting and pagination edge cases — interleaved with smaller integration improvements: Google Ads account-switching, expanded AI-referral domain detection, sequential-audience sort and filter, in-app contact form. No directional moves in this window.
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.
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.
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.
Recent releases (18.59 through 18.66) follow a tight bi-weekly cadence dominated by analytics bug fixes — chart tooltips, scheduled-report PDF rendering, sorting and pagination edge cases — interleaved with smaller integration improvements: Google Ads account-switching, expanded AI-referral domain detection, sequential-audience sort and filter, in-app contact form. No directional moves in this window.
The product is in maintenance-and-polish mode, focused on the edges where reports, exports, and integrations break. The most signal-bearing recent change is broader Google Ads account management plus more domains classified as AI-driven traffic — small hints at where buyers are asking for sharper analytics.
Expect Piwik PRO to keep shipping defect-density patches at this cadence, with what feature growth there is concentrated in AI-traffic attribution and Google Ads tooling rather than core analytics primitives.
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 Piwik PRO.
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all Amundsen alternatives → · See all Piwik PRO alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Piwik PRO 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Piwik PRO 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.
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.
Top Piwik PRO alternatives in Analytics are ranked by recent ship velocity. Browse the "Piwik PRO alternatives" section above for the current picks, or visit /alternatives/piwik-pro for the full list with editorial commentary on each.