Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of Fulcrum and RadialMR — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | RadialMR |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | gis, esri-migration, offline-maps, field-data-capture | mendelian-randomization, radial-plots, correctness-audit, statistical-inference |
| Last editorial update | 6h ago | 4d ago |
| Website | — | Visit → |
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.
RadialMR's 2026 release corrects degrees of freedom that had been wrong since documentation.
RadialMR implements radial-plot formulations of IVW and MR-Egger Mendelian randomization, with outlier detection and interactive plotting. The recent history is thin on features and increasingly focused on the arithmetic: 1.2.4 in July 2026 fixes the degrees of freedom returned by egger_radial() to the documented n-2, corrects the heterogeneity p-value that inherited the same error, and repairs a negated lower bound in the random-effects bootstrap standard error search interval in ivw_radial().
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.
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.
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.
RadialMR implements radial-plot formulations of IVW and MR-Egger Mendelian randomization, with outlier detection and interactive plotting. The recent history is thin on features and increasingly focused on the arithmetic: 1.2.4 in July 2026 fixes the degrees of freedom returned by egger_radial() to the documented n-2, corrects the heterogeneity p-value that inherited the same error, and repairs a negated lower bound in the random-effects bootstrap standard error search interval in ivw_radial().
This is a package being read closely by its maintainer rather than extended. The 1.2.x line pairs statistical corrections with defensive hardening — an rmr_format class check so unformatted input fails with a clear message, and plotly_radial() dispatching on object class instead of counting list elements. Both are the kind of change made while auditing, not while building.
Expect the audit to continue into the remaining estimator internals and print methods rather than new radial variants; the entries show no feature work queued.
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 RadialMR.
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
See all Fulcrum alternatives → · See all RadialMR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
Top RadialMR alternatives in Analytics are ranked by recent ship velocity. Browse the "RadialMR alternatives" section above for the current picks, or visit /alternatives/radialmr for the full list with editorial commentary on each.