← Back to home
Comparison · Analytics

Fulcrum vs mlr3mbo

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

Fulcrum vs mlr3mbo: at a glance

FeatureFulcrummlr3mbo
SectorAnalyticsAnalytics
Velocity score6.32.5
Sparks · 30d00
Top themesfield-data-collection, esri-arcgis, offline-maps, on-device-inferencebayesian-optimization, mlr3, hyperparameter-tuning, r-stats
Last editorial update18h ago1h ago
WebsiteVisit →

What is Fulcrum?

Fulcrum's mobile train is all Esri migration cleanup, with on-device inference quietly changing format.

Fulcrum ships iOS, Android, and web releases on a near-weekly cadence, and this stretch is dominated by mapping work following the Google Maps retirement announced for September. Recent builds upgraded to ArcGIS SDK 300.0.0, moved the web map engine to current ArcGIS and deck.gl versions, and worked through the resulting stability issues — basemap loading, location resolution, black map screens, panning and zooming performance. The most consequential change is easy to miss: ONNX support for on-device machine learning inference was removed in favor of a new INFERENCE format that reads labels from an uploaded labels.txt.

Read the full Fulcrum trajectory →

What is mlr3mbo?

mlr3mbo picked its defaults from a benchmark study, not from taste

mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.

Read the full mlr3mbo trajectory →

Fulcrum vs mlr3mbo: editorial side-by-side

F
Fulcrum
ANALYTICS
6.3

Fulcrum's mobile train is all Esri migration cleanup, with on-device inference quietly changing format.

◆ Current state

Fulcrum ships iOS, Android, and web releases on a near-weekly cadence, and this stretch is dominated by mapping work following the Google Maps retirement announced for September. Recent builds upgraded to ArcGIS SDK 300.0.0, moved the web map engine to current ArcGIS and deck.gl versions, and worked through the resulting stability issues — basemap loading, location resolution, black map screens, panning and zooming performance. The most consequential change is easy to miss: ONNX support for on-device machine learning inference was removed in favor of a new INFERENCE format that reads labels from an uploaded labels.txt.

◆ Where it's heading

This is a platform consolidation being paid down one point release at a time. Having committed to Esri, Fulcrum is absorbing the instability that came with it, and each release reads as fixes to symptoms of the same migration. Underneath, the offline and field-capture story continues to get real attention — downloaded offline map layers can now be updated in place, and Photo FastFill moved to background processing so it no longer blocks editing.

◆ Prediction

Expect the release notes to stay fix-dominated through the September Google Maps cutoff, with the migration-related map defects tapering after it passes. Photo FastFill leaving early access is the most likely next substantive item.

M
mlr3mbo
ANALYTICS
2.5

mlr3mbo picked its defaults from a benchmark study, not from taste

◆ Current state

mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.

◆ Where it's heading

The package has moved from a toolkit that expected users to assemble a Bayesian optimisation loop into one with a defensible default loop, and the recent fixes — warm-start sizing on multi-objective archives, silently discarded terminators, stale x_domain values — are the consequences of more people running the default path.

◆ Prediction

Expect continued hardening of the acquisition-optimiser classes rather than new acquisition functions.

Alternatives to Fulcrum and mlr3mbo

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

See all Fulcrum alternatives → · See all mlr3mbo alternatives →

Recent activity from Fulcrum and mlr3mbo

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

  1. 1d agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
  2. 2d agoFulcrumiOS fix: slow location resolution blocked record saves
  3. 6d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
  4. 8d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
  5. 8d agoFulcrumiOS fixes: basemap loading and black map screen
  6. 9d agoFulcrumiOS: ArcGIS SDK 300.0.0 and ONNX replaced by a new INFERENCE format
  7. 23d agomlr3mboAcquisition optimiser fixes for warm starts and archives
  8. 3mo agomlr3mboDictionary lookup and restart-limit fixes
  9. 4mo agomlr3mborush 1.0.0 compatibility and Surrogate$check()
  10. 5mo agomlr3mbomlr3mbo 1.0.0 ships benchmark-derived default settings
  11. 10mo agomlr3mbomlr3learners 0.13.0 compatibility
  12. 11mo agomlr3mboMaintainer change and mlr3pipelines 0.9.0 upkeep

Frequently asked questions

What is the difference between Fulcrum and mlr3mbo?

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 mlr3mbo?

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 mlr3mbo?

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