← Back to home
Comparison · Analytics

Fulcrum vs hubEvals

A side-by-side editorial comparison of Fulcrum and hubEvals — release velocity, themes, recent moves, and the top alternatives to consider.

Fulcrum vs hubEvals: at a glance

FeatureFulcrumhubEvals
SectorAnalyticsAnalytics
Velocity score6.32.5
Sparks · 30d00
Top themesgis, esri-migration, offline-maps, field-data-captureforecast-evaluation, scoring, epidemiology, r-package
Last editorial update4h ago3d ago
WebsiteVisit →

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.

Read the full Fulcrum trajectory →

What is hubEvals?

Forecast-hub scoring that learned to handle joint, sample-based predictions.

hubEvals scores model output from collaborative forecasting hubs, wrapping scoringutils and translating hubverse formats into forecast objects it can evaluate. The package has moved quickly from a thin translation layer to something that handles every output type the hubverse defines — quantile, mean, median, nominal and ordinal pmf, and samples. The most recent releases are almost entirely about the failure modes of relative skill scoring rather than about new metrics.

Read the full hubEvals trajectory →

Fulcrum vs hubEvals: editorial side-by-side

F
Fulcrum
ANALYTICS
6.3

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.

H
hubEvals
ANALYTICS
2.5

Forecast-hub scoring that learned to handle joint, sample-based predictions.

◆ Current state

hubEvals scores model output from collaborative forecasting hubs, wrapping scoringutils and translating hubverse formats into forecast objects it can evaluate. The package has moved quickly from a thin translation layer to something that handles every output type the hubverse defines — quantile, mean, median, nominal and ordinal pmf, and samples. The most recent releases are almost entirely about the failure modes of relative skill scoring rather than about new metrics.

◆ Where it's heading

Two threads dominate. The first is coverage of output types, which reached its widest point with sample-based and compound scoring. The second, and the one occupying every recent release, is making relative skill degrade gracefully: single-model input, comparison groups with one model, and groups missing the requested baseline have each been converted from a cryptic upstream abort into a defined result. That pattern — inherited scoringutils errors being caught and given hub-specific meaning — is the clearest signal of where this package adds value.

◆ Prediction

Expect continued work smoothing scoringutils error surfaces into hub-aware behaviour, and performance attention on relative skill, which was explicitly optimised in the latest release.

Alternatives to Fulcrum and hubEvals

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 hubEvals.

See all Fulcrum alternatives → · See all hubEvals alternatives →

Recent activity from Fulcrum and hubEvals

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoFulcrumiOS: async database queries, non-blocking Photo FastFill
  2. 5d agoFulcrumWeb fixes: shared-view exports, MBTiles popups, KML and ArcGIS layers
  3. 7d agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
  4. 8d agoFulcrumiOS fix: slow location resolution blocked record saves
  5. 13d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
  6. 14d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
  7. 27d agohubEvalsScored-forecast counts and faster relative skill
  8. 1mo agohubEvalsDisaggregated relative skill no longer aborts the whole call
  9. 1mo agohubEvalsSingle-model scoring returns relative skill of 1 instead of erroring
  10. 5mo agohubEvalsSample output types and multivariate compound scoring
  11. 6mo agohubEvalsScoring on transformed scales via transform arguments
  12. 11mo agohubEvalsFirst release: score_model_out() and the scoringutils bridge

Frequently asked questions

What is the difference between Fulcrum and hubEvals?

They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 hubEvals?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 hubEvals?

Top hubEvals alternatives in Analytics are ranked by recent ship velocity. Browse the "hubEvals alternatives" section above for the current picks, or visit /alternatives/hubevals for the full list with editorial commentary on each.