Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Amundsen and RevenueCat — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Amundsen | RevenueCat |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | data-catalog, metadata, maintenance-mode, monorepo-releases | mobile-monetization, subscriptions, paywalls, ad-revenue |
| 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.
Stretching from subscription infrastructure into hybrid subs+ads revenue tracking, with paywalls getting smarter.
RevenueCat is broadening from subscription-only to subscription-plus-ads with in-app ad revenue tracking now in public beta — apps using AdMob or AppLovin can send ad events through the SDK and see ad and sub revenue side by side. Paywalls have gained meaningful logic depth (Paywall Rules to show/hide components by intro-offer eligibility or custom variables) and the iOS/Android fallback paywall now auto-styles using the app icon's dominant color. Operational tooling has caught up: archived offerings/products/entitlements, OAuth token visibility and revocation, predicted-LTV winners in Experiments.
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.
RevenueCat is broadening from subscription-only to subscription-plus-ads with in-app ad revenue tracking now in public beta — apps using AdMob or AppLovin can send ad events through the SDK and see ad and sub revenue side by side. Paywalls have gained meaningful logic depth (Paywall Rules to show/hide components by intro-offer eligibility or custom variables) and the iOS/Android fallback paywall now auto-styles using the app icon's dominant color. Operational tooling has caught up: archived offerings/products/entitlements, OAuth token visibility and revocation, predicted-LTV winners in Experiments.
The product is moving from 'subscription billing infra' to 'mobile monetization platform.' Ad revenue tracking is the headline because it changes who RevenueCat is for — every freemium app with mixed monetization, not just sub-driven apps. Paywall Rules suggest the company is going deeper on the merchandising layer rather than ceding it to MMP-adjacent tools. The Experiments-side LTV predictions and locale-aware paywalls signal continued investment in the optimization story.
Expect the in-app ad revenue beta to GA with deeper SDK support for more ad networks, more sophisticated Paywall Rules conditions (likely user-segment and behavioral triggers), and tighter Experiments + ad-revenue correlation as customers compare hybrid monetization mixes.
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 RevenueCat.
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 RevenueCat 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 RevenueCat 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 RevenueCat 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 RevenueCat alternatives in Analytics are ranked by recent ship velocity. Browse the "RevenueCat alternatives" section above for the current picks, or visit /alternatives/revenuecat for the full list with editorial commentary on each.