Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Amundsen and PostHog — release velocity, themes, recent moves, and the top alternatives to consider.
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.
PostHog is filling in Logs and the mobile SDKs while quietly growing a support product.
PostHog ships weekly, and this week's batch is spread across four teams rather than concentrated in one product. Logs gets attribute filtering and a React Native capture path; the iOS SDK gains rage-click detection and a session-replay duration floor; Conversations picks up GitHub issues as an inbound support channel. Individually these are small, and the weekly digest bundles them into a single roundup entry.
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.
PostHog ships weekly, and this week's batch is spread across four teams rather than concentrated in one product. Logs gets attribute filtering and a React Native capture path; the iOS SDK gains rage-click detection and a session-replay duration floor; Conversations picks up GitHub issues as an inbound support channel. Individually these are small, and the weekly digest bundles them into a single roundup entry.
Two build-outs are running in parallel. The observability side — Logs plus the mobile SDKs — is being brought up to parity with what PostHog already offers on web, which is what makes the platform credible for mobile teams rather than web analytics with an SDK attached. The Conversations work is the more interesting thread: adding support channels moves PostHog past measuring users toward handling them, and it is being built out in the same incremental weekly rhythm as everything else.
Expect Logs and the mobile SDKs to keep receiving parity features on the weekly cadence, and expect Conversations to add further inbound channels beyond GitHub issues. The entries do not show whether Conversations is being positioned as a standalone product or a feature of the existing suite.
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 PostHog.
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 PostHog alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Amundsen and PostHog are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. Amundsen and PostHog are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 PostHog alternatives in Analytics are ranked by recent ship velocity. Browse the "PostHog alternatives" section above for the current picks, or visit /alternatives/posthog for the full list with editorial commentary on each.