Lightdash
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
Comparison · Analytics
Fulcrum vs Whatagraph
A side-by-side editorial comparison of Fulcrum and Whatagraph — release velocity, themes, recent moves, and the top alternatives to consider.
Fulcrum vs Whatagraph: at a glance
| Feature | Fulcrum | Whatagraph |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | gis, esri-migration, offline-maps, field-data-capture | reporting, agencies, integrations, reliability |
| Last editorial update | 14h ago | 1h ago |
| Website | — | — |
What is Fulcrum?
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.
What is Whatagraph?
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Whatagraph is working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removed live API calls from render time in the Basis rebuild, connection failover keeps widgets alive when one teammate's token expires, and report shortcuts let a heavy report be split into a hub with supporting detail. Presentation control arrives steadily alongside — automatic conditional formatting, per-metric decimal places, chosen comparison colors. The newest change moves unified-field mapping into the Source Group builder, so a cross-channel group can be fixed in place instead of rebuilt.
Fulcrum vs Whatagraph: editorial side-by-side
Fulcrum
6.3ANALYTICS
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Whatagraph
5.0ANALYTICS
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
◆ Current state
Whatagraph is working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removed live API calls from render time in the Basis rebuild, connection failover keeps widgets alive when one teammate's token expires, and report shortcuts let a heavy report be split into a hub with supporting detail. Presentation control arrives steadily alongside — automatic conditional formatting, per-metric decimal places, chosen comparison colors. The newest change moves unified-field mapping into the Source Group builder, so a cross-channel group can be fixed in place instead of rebuilt.
◆ Where it's heading
The through-line is reliability and workflow cost at agency scale, where one account runs hundreds or thousands of sources across several people. Each release picks a specific moment where that scale used to force a detour — a dead token, a forty-widget report, a half-built source group — and removes the detour rather than adding a capability. Integration work stays additive and named: Ahrefs Rank Tracker, WhatConverts, Snowflake, bol., each filling a stated reporting gap rather than broadening a connector catalog.
◆ Prediction
Expect the same volume-driven treatment applied to the remaining multi-step setup flows, and further integrations chosen to close named gaps rather than to grow the connector count.
Alternatives to Fulcrum and Whatagraph
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 Whatagraph.
Delta Lake
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
See all Fulcrum alternatives → · See all Whatagraph alternatives →
Recent activity from Fulcrum and Whatagraph
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20h agoWhatagraphUnify metrics and dimensions while creating a Source Group
- 1d agoFulcrumiOS: async database queries, non-blocking Photo FastFill
- 5d agoFulcrumWeb fixes: shared-view exports, MBTiles popups, KML and ArcGIS layers
- 7d agoWhatagraphTurn your report into client portal with Report shortcuts
- 7d agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
- 8d agoFulcrumiOS fix: slow location resolution blocked record saves
- 13d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
- 14d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
- 21d agoWhatagraphOne broken connection won't break your reports
- 21d agoWhatagraphClearer charts and tables, and a faster way to find the right template
- 27d agoWhatagraphTrack your keywords against competitors with Ahrefs Rank Tracker
- 1mo agoWhatagraphBasis rebuilt: faster data, cleaner numbers, per-client sources
Frequently asked questions
What is the difference between Fulcrum and Whatagraph?
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 5.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 Whatagraph?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 5.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 Whatagraph?
Top Whatagraph alternatives in Analytics are ranked by recent ship velocity. Browse the "Whatagraph alternatives" section above for the current picks, or visit /alternatives/whatagraph for the full list with editorial commentary on each.