ThingsBoard
An IoT platform whose release notes have become a CVE ledger
Comparison · Analytics
Fulcrum vs ROOT
A side-by-side editorial comparison of Fulcrum and ROOT — release velocity, themes, recent moves, and the top alternatives to consider.
Fulcrum vs ROOT: at a glance
| Feature | Fulcrum | ROOT |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | field-data-collection, gis, esri-migration, offline-reliability | hep-analysis, rntuple, rdataframe, lts-branches |
| Last editorial update | 2d ago | 2h ago |
| Website | — | Visit → |
What is Fulcrum?
Fulcrum is consolidating its whole mapping stack on Esri, and retiring Google Maps to finish it.
Fulcrum ships weekly web release notes alongside separate iOS and Android builds, and nearly all of the recent work is mapping. The ArcGIS SDK moved to 300.0.0 on mobile and the map engine picked up current ArcGIS and deck.gl versions on web, while a run of fixes addressed offline layer styling, basemap loading and attachment downloads on poor connections. On-device machine learning inference dropped ONNX for a new format, with labels now read from an uploaded labels.txt file.
What is ROOT?
ROOT is shipping the pieces of its long-promised v7 inside the v6 release line
ROOT maintains an unusual number of parallel branches — patches for 6.26, 6.28, 6.30, 6.32, 6.36 and 6.38 all landed within weeks of each other in June 2026 — because CERN experiments pin to versions for years at a time. The 6.40 LTS released in May is where the actual work is: an opt-out from automatic object registration, experimental multithreaded histograms, a new RFile interface, an libcurl-based HTTP I/O layer with S3 support, and a rebuilt ML data loader. June's patch wave is the routine consequence, closing out the 6.26 and 6.38 series while fixing the first regressions in 6.40.
Fulcrum vs ROOT: editorial side-by-side
Fulcrum
6.3ANALYTICS
Fulcrum is consolidating its whole mapping stack on Esri, and retiring Google Maps to finish it.
◆ Current state
Fulcrum ships weekly web release notes alongside separate iOS and Android builds, and nearly all of the recent work is mapping. The ArcGIS SDK moved to 300.0.0 on mobile and the map engine picked up current ArcGIS and deck.gl versions on web, while a run of fixes addressed offline layer styling, basemap loading and attachment downloads on poor connections. On-device machine learning inference dropped ONNX for a new format, with labels now read from an uploaded labels.txt file.
◆ Where it's heading
The mapping stack is converging on Esri across every client, and the announced September 1 retirement of the legacy Google Maps engine makes that explicit. Esri Maps has absorbed Google's satellite, hybrid and street basemaps, and the GIS capabilities Fulcrum keeps investing in — snapping, ArcGIS Feature Service connectivity, offline basemaps, GPS tracks, the redesigned location editor — only exist on that engine. Everything else in the feed is stabilization on the same surface, which is what a team does when it is preparing to move every remaining customer onto one path.
◆ Prediction
Expect migration reminders and switching guidance for organizations still defaulting to Google Maps as September 1 approaches, and MMPK layers to leave Early Access once the engine consolidation is complete.
ROOT
0.0ANALYTICS
ROOT is shipping the pieces of its long-promised v7 inside the v6 release line
◆ Current state
ROOT maintains an unusual number of parallel branches — patches for 6.26, 6.28, 6.30, 6.32, 6.36 and 6.38 all landed within weeks of each other in June 2026 — because CERN experiments pin to versions for years at a time. The 6.40 LTS released in May is where the actual work is: an opt-out from automatic object registration, experimental multithreaded histograms, a new RFile interface, an libcurl-based HTTP I/O layer with S3 support, and a rebuilt ML data loader. June's patch wave is the routine consequence, closing out the 6.26 and 6.38 series while fixing the first regressions in 6.40.
◆ Where it's heading
The ROOT 7 redesign is arriving piecemeal under ROOT::Experimental rather than as a version bump: RNTuple replacing TTree, RDataFrame replacing TTree::Draw, RFile replacing TFile, and now the ability to switch off the global-directory ownership model that has defined ROOT's ergonomics for decades. The team is easing migration with documentation rather than deprecation — 6.40 ships a TTree::Draw-to-RDataFrame translation guide instead of a removal notice. Build weight is being cut in the same pass, with bundled builtin packages reduced roughly fourfold in favour of system libraries.
◆ Prediction
Expect further 6.40.x patches through the year as experiments migrate onto the LTS, concentrated in RNTuple and the new histogram paths where the code is youngest. The experimental namespace is the thing to watch: features that stabilize there are the clearest available signal of what a ROOT 7 would actually contain.
Alternatives to Fulcrum and ROOT
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 ROOT.
Apache Drill
A SQL-on-anything engine shipping rarely, but each release widens what it can reach
Apache Superset
Superset's tracked feed is a Helm chart tag stream with no notes attached.
ApexCharts
Three releases in three weeks moved ApexCharts from free library to gated open-core.
Graphite
Graphite's answer to its own CVE backlog is a pre-release nobody calls official.
Cortex
Cortex is betting on Parquet block storage and graduating years of experimental features.
See all Fulcrum alternatives → · See all ROOT alternatives →
Recent activity from Fulcrum and ROOT
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoFulcrumSSO notification wording and an ArcGIS map engine update
- 5d agoFulcrumAndroid: ArcGIS location and signature field fixes
- 5d agoFulcrumiOS: basemap loading and location button fixes
- 6d agoFulcrumiOS drops ONNX for on-device inference; ArcGIS SDK 300
- 6d agoFulcrumiOS: offline ArcGIS layers keep custom symbols
- 10d agoFulcrumReplace a map layer file without recreating the layer
- 1mo agoROOTROOT 6.32.24 patches the 6.32 maintenance branch
- 1mo agoROOTROOT 6.30.12 patches the 6.30 maintenance branch
- 1mo agoROOTROOT 6.28.16 patches the 6.28 maintenance branch
- 1mo agoROOTROOT 6.38.06 closes the 6.38 series, adds Python 3.15 support
- 2mo agoROOTROOT 6.40.02 fixes RNTuple model extension and SOFIE padding
- 2mo agoROOTROOT 6.26.20 is the final patch for the 6.26 series
Frequently asked questions
What is the difference between Fulcrum and ROOT?
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 ROOT?
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 ROOT?
Top ROOT alternatives in Analytics are ranked by recent ship velocity. Browse the "ROOT alternatives" section above for the current picks, or visit /alternatives/cern-root for the full list with editorial commentary on each.