distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
A side-by-side editorial comparison of Fulcrum and Pinpoint — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | Pinpoint |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | gis, esri-migration, offline-maps, field-data-capture | apm, distributed-tracing, servermap, jvm-agents |
| Last editorial update | 9h ago | 13d ago |
| Website | — | Visit → |
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. The newest iOS build turns to app-level responsiveness - database queries moved off the main path and the record editor kept interactive while Photo FastFill works in the background.
ServerMap rebuilt and application names finally long enough to describe a service.
Pinpoint ships a minor roughly once a year with patch releases in between. The 3.1.0 release rebuilt ServerMap as V3 with a redesigned storage layout, a new query path and a new set of map tables, and raised the applicationName ceiling from 24 to 254 characters — gated behind an agent property that requires collector 3.1.0 or higher. The patch line before it is mostly backports and plugin compatibility: Java 26, Kafka Streams, Kafka 4.x, S3, nested Spring Boot JARs.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. The newest iOS build turns to app-level responsiveness - database queries moved off the main path and the record editor kept interactive while Photo FastFill works in the background.
The direction is a full consolidation onto Esri. The legacy Google Maps engine retires on September 1 with automatic migration for anyone who has not switched, and Esri now carries Google's satellite and street basemaps so the imagery argument is neutralized. Underneath, the mobile SDK moved to ArcGIS 300.0.0 and ONNX on-device inference gave way to a new INFERENCE format. Two capabilities are visibly staged behind early access rather than shipped: Photo FastFill, and a GPS integration still described as Alpha.
Expect the weeks before September 1 to stay dominated by migration-shaped fixes and Esri parity work, with Photo FastFill the nearer of the two early-access programs to general availability given it is already running in shipped builds.
Pinpoint ships a minor roughly once a year with patch releases in between. The 3.1.0 release rebuilt ServerMap as V3 with a redesigned storage layout, a new query path and a new set of map tables, and raised the applicationName ceiling from 24 to 254 characters — gated behind an agent property that requires collector 3.1.0 or higher. The patch line before it is mostly backports and plugin compatibility: Java 26, Kafka Streams, Kafka 4.x, S3, nested Spring Boot JARs.
The plugin surface expands continuously — each release absorbs another client library or runtime version — while the platform work arrives in rare, larger jumps that touch storage schema and require coordinated agent and collector upgrades. The 3.1.0 changes suggest the constraints being addressed are those of large deployments: structured naming schemes that no longer fit, and a topology view whose query path needed redesigning rather than tuning.
Expect the 3.1 line to spend its patches stabilising the ServerMap V3 storage path and backporting plugin updates, with the next set of runtime and client integrations arriving the same way they always have.
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 Pinpoint.
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all Fulcrum alternatives → · See all Pinpoint 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 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. Fulcrum is currently shipping more aggressively (velocity 6.3 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 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 Pinpoint alternatives in Analytics are ranked by recent ship velocity. Browse the "Pinpoint alternatives" section above for the current picks, or visit /alternatives/pinpoint for the full list with editorial commentary on each.