dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Comparison · Analytics
Fulcrum vs hubData
A side-by-side editorial comparison of Fulcrum and hubData — release velocity, themes, recent moves, and the top alternatives to consider.
Fulcrum vs hubData: at a glance
| Feature | Fulcrum | hubData |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | gis, esri-migration, offline-maps, field-data-capture | data-access, arrow, cloud-storage, hubverse |
| Last editorial update | 4h ago | 3d ago |
| Website | — | Visit → |
What is Fulcrum?
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.
What is hubData?
The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
Fulcrum vs hubData: editorial side-by-side
Fulcrum
6.3ANALYTICS
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
hubData
0.0ANALYTICS
The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.
◆ Current state
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
◆ Where it's heading
The package has largely finished adding surface and is now paying down the cost of sitting on top of Arrow and S3: ALTREP-backed columns escaping into user sessions, cloud hubs whose declared format differs from what is actually written, and metadata arrays parsing inconsistently. Each fix narrows the gap between what the storage layer does and what an R user expects. The performance-motivated default flip in 2.0.0 points the same way, prioritising large cloud hubs over conservative local behaviour.
◆ Prediction
Expect continued fixes at the Arrow and cloud boundary, particularly where declared hub configuration and actual stored format disagree, which has now produced defects twice.
Alternatives to Fulcrum and hubData
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 hubData.
Holistics
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
tulpa
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
AgencyAnalytics
AgencyAI got skills three weeks ago; everything since has been making them routine.
NocoDB
Interfaces gets the permissions layer it needed, one release after launching.
See all Fulcrum alternatives → · See all hubData alternatives →
Recent activity from Fulcrum and hubData
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoFulcrumiOS: async database queries, non-blocking Photo FastFill
- 5d agoFulcrumWeb fixes: shared-view exports, MBTiles popups, KML and ArcGIS layers
- 7d agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
- 8d agoFulcrumiOS fix: slow location resolution blocked record saves
- 13d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
- 14d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
- 1mo agohubDataCloud hubs declaring CSV no longer return an empty connection
- 3mo agohubDatacollect_hub() returns plain vectors instead of ALTREP views
- 3mo agohubDataArray-valued metadata fields now parse as list columns
- 7mo agohubDatadate_col parameter for oracle output schemas
- 9mo agohubDataconnect_hub() skips file validation by default (breaking)
- 11mo agohubDataArrow schema conversion and validation utilities
Frequently asked questions
What is the difference between Fulcrum and hubData?
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.
Is Fulcrum better than hubData?
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.
What are the best alternatives to Fulcrum?
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.
What are the best alternatives to hubData?
Top hubData alternatives in Analytics are ranked by recent ship velocity. Browse the "hubData alternatives" section above for the current picks, or visit /alternatives/hubdata for the full list with editorial commentary on each.