Omni
Omni ships weekly, and almost every week the headline item is an AI feature
A side-by-side editorial comparison of Fulcrum and Pirsch Analytics — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | Pirsch Analytics |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 3.8 |
| Sparks · 30d | 0 | 0 |
| Top themes | field-data-collection, esri-arcgis, offline-maps, mobile-releases | privacy analytics, bot filtering, maintenance, dashboards |
| Last editorial update | 2h ago | 3mo ago |
| Website | — | — |
Fulcrum is consolidating on Esri, with Google Maps gone September 1
The mapping stack is the whole story right now: ArcGIS SDK 300.0.0 on iOS, the latest ArcGIS and deck.gl on web, and a hard cutover date after which any organization still defaulting to Google Maps is switched to Esri automatically. The mobile releases in this window are almost entirely map and location fixes — basemap loading, offline symbol styling, location resolution that blocked saves. On-device inference quietly changed format, dropping ONNX.
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.
The mapping stack is the whole story right now: ArcGIS SDK 300.0.0 on iOS, the latest ArcGIS and deck.gl on web, and a hard cutover date after which any organization still defaulting to Google Maps is switched to Esri automatically. The mobile releases in this window are almost entirely map and location fixes — basemap loading, offline symbol styling, location resolution that blocked saves. On-device inference quietly changed format, dropping ONNX.
One platform bet runs through everything: Esri as the single map engine, with Google's satellite, hybrid, and street imagery retained as basemap options so the migration costs users imagery choice, not capability. The current release cadence is stabilization work paying down that migration rather than new ground.
Expect map and location fixes to keep dominating releases through the September 1 cutover, with the Esri-only capabilities already listed — snapping, ArcGIS Feature Service connectivity, offline basemaps — becoming the default surface rather than the alternative one.
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.
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.
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.
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 Fulcrum or Pirsch Analytics.
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
Amundsen's last release was a config flag, and the feed has been silent for two years
See all Fulcrum alternatives → · See all Pirsch Analytics alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 3.8), 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. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 3.8), 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 Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.
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.