Looker
Looker's release feed is mostly page furniture; the shipping behind it is thin.
A side-by-side editorial comparison of Fulcrum and Plotly — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | Plotly |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | esri-migration, arcgis, field-data-collection, mobile-releases | dash-hosting, plotly-cloud, custom-domains, compute-credits |
| Last editorial update | 54m ago | 11h ago |
| Website | — | Visit → |
Fulcrum is retiring Google Maps for Esri and stabilising the ArcGIS stack behind it.
The legacy Google Maps engine is being retired on 1 September 2026, with any organisation still defaulting to it switched over automatically. The mobile releases since are consolidation on the replacement: ArcGIS SDK 300.0.0, restored styling on offline ArcGIS feature layers, better basemap loading, and fixes to location-button behaviour on both platforms. iOS 2607.3.0 also swapped ONNX for a different on-device inference format.
The desktop app builder is pre-1.0, but Plotly Cloud quietly turned into a Dash hosting platform.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
The legacy Google Maps engine is being retired on 1 September 2026, with any organisation still defaulting to it switched over automatically. The mobile releases since are consolidation on the replacement: ArcGIS SDK 300.0.0, restored styling on offline ArcGIS feature layers, better basemap loading, and fixes to location-button behaviour on both platforms. iOS 2607.3.0 also swapped ONNX for a different on-device inference format.
This is a forced migration being executed carefully — the map engine is the field app's core dependency, and each release since the announcement has fixed something in the ArcGIS path rather than adding capability. The pace of small mobile releases suggests they are clearing defects ahead of the September cutover rather than working to a feature roadmap.
Expect continued ArcGIS-focused fix releases on both platforms through the September cutover, with feature work resuming only once the Google Maps default is gone.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
The centre of gravity has moved from the desktop tool to the hosting product. Studio's releases are pre-1.0 hardening — navigation, credential handling, install paths — while Cloud is the side gaining capability that changes what a customer can do, and it is where the tier boundaries are being drawn. Consumption economics are becoming explicit, with idle spend and cold starts surfaced as customer-tunable settings rather than hidden platform behaviour.
The next Cloud releases most likely extend the resource and access controls a hosted app needs — finer app sizing, or authentication and access rules on custom domains — rather than adding capability to Studio.
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 Plotly.
Looker's release feed is mostly page furniture; the shipping behind it is thin.
Shynet went silent for two and a half years and a security audit is what woke it up.
Power BI's monthly grind: authoring defaults, DAX documentation, and cleaner axes.
BigQuery is making itself agent-callable and pulling inference inside the SQL boundary.
Lightdash is turning BI into an app platform its users' coding agents can build against.
TimescaleDB trades new features for lock contention wins and a security patch
See all Fulcrum alternatives → · See all Plotly 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 1 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 1 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 Plotly alternatives in Analytics are ranked by recent ship velocity. Browse the "Plotly alternatives" section above for the current picks, or visit /alternatives/plotly for the full list with editorial commentary on each.