← Back to home
Comparison · Analytics

Fulcrum vs OpenMC

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

Fulcrum vs OpenMC: at a glance

FeatureFulcrumOpenMC
SectorAnalyticsAnalytics
Velocity score6.32.5
Sparks · 30d00
Top themesfield-data-collection, esri-arcgis, offline-maps, mobile-releasesmonte-carlo-transport, random-ray, depletion, neutronics
Last editorial update9h ago19h ago
WebsiteVisit →

What is Fulcrum?

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.

Read the full Fulcrum trajectory →

What is OpenMC?

OpenMC's random ray solver has gone from new arrival to the centre of every release

OpenMC is a Monte Carlo particle transport code for neutronics and radiation analysis. Since the random ray transport solver landed in 0.15.0 it has received substantial work in every subsequent release, most recently local adjoint sources, temperature and distributed-density feedback, fission-heating tallies and a weight-window bootstrapping workflow. The other consistent thread is shutdown-dose and depletion tooling, where 0.15.3 introduced an R2SManager to automate the rigorous two-step workflow and 0.16.0 extended it with reactivity control, CRAM substeps and multiple meshes.

Read the full OpenMC trajectory →

Fulcrum vs OpenMC: editorial side-by-side

F
Fulcrum
ANALYTICS
6.3

Fulcrum is consolidating on Esri, with Google Maps gone September 1

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

O
OpenMC
ANALYTICS
2.5

OpenMC's random ray solver has gone from new arrival to the centre of every release

◆ Current state

OpenMC is a Monte Carlo particle transport code for neutronics and radiation analysis. Since the random ray transport solver landed in 0.15.0 it has received substantial work in every subsequent release, most recently local adjoint sources, temperature and distributed-density feedback, fission-heating tallies and a weight-window bootstrapping workflow. The other consistent thread is shutdown-dose and depletion tooling, where 0.15.3 introduced an R2SManager to automate the rigorous two-step workflow and 0.16.0 extended it with reactivity control, CRAM substeps and multiple meshes.

◆ Where it's heading

The project is layering a deterministic-adjacent solver alongside its Monte Carlo core rather than replacing it, and the ratio of random-ray work to core-solver work in each release keeps rising. In parallel it is packaging expert workflows into objects — R2SManager is the clearest case, turning a multi-stage shutdown dose calculation into a class rather than a recipe. The Python API is where most of that packaging surfaces, and it is also where the compatibility breaks land, with the minimum version moving to 3.12 in 0.16.0.

◆ Prediction

Given that every release since 0.15.0 has expanded the random ray solver's feedback and tally coverage, the next is likely to continue closing the gap between it and the main solver's feature set. The notes do not indicate whether it is intended to become a default path.

Alternatives to Fulcrum and OpenMC

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

See all Fulcrum alternatives → · See all OpenMC alternatives →

Recent activity from Fulcrum and OpenMC

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

  1. 15h agoFulcrumiOS fix for slow location resolution blocking saves
  2. 5d agoFulcrumMap engine updated to the latest ArcGIS and deck.gl
  3. 6d agoOpenMCSurface-flux tallies and PDG particle identifiers in OpenMC 0.16.0
  4. 6d agoFulcrumAndroid stability fixes for ArcGIS location and signatures
  5. 6d agoFulcrumiOS basemap loading and map-centering fixes
  6. 7d agoFulcrumArcGIS SDK 300.0.0 lands; ONNX inference support removed
  7. 7d agoFulcrumOffline ArcGIS layers keep custom symbols and labels
  8. 8mo agoOpenMCR2SManager automates shutdown dose rate calculations in OpenMC 0.15.3
  9. 1y agoOpenMCOpenMC 0.15.2 hotfixes an MPI regression
  10. 1y agoOpenMCRay-traced material volumes and Phong-shaded plots in OpenMC 0.15.1
  11. 2y agoOpenMCOpenMC 0.15.0 introduces a random ray transport solver
  12. 2y agoOpenMCWeight window generation and continuous nuclide feed in OpenMC 0.14.0

Frequently asked questions

What is the difference between Fulcrum and OpenMC?

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

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

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