OpenObserve
OpenObserve is shipping a 0.91 patch every few days while 0.92 stabilises alongside it
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 | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | offline-first, gis, computer-vision, arcgis | agency-reporting, data-integrations, warehouse-sources, report-readability |
| Last editorial update | 4h ago | 18h ago |
| Website | — | — |
What is Fulcrum?
A weekly three-platform release train where offline computer vision is the only real bet.
Fulcrum runs a tri-platform cadence — weekly web release notes plus separately versioned iOS and Android drops — and the July window is overwhelmingly maintenance: map stability, layer-format handling, offline ArcGIS reliability. The one substantive thread is the INFERENCE data event, which runs computer-vision models on device without connectivity and now reads its class labels from an uploaded labels.txt. Underneath that, the mobile map engine moved to ArcGIS SDK 300.0.0.
What is Whatagraph?
Whatagraph is building a data layer under the reports — storing data instead of fetching it live.
Whatagraph ships in two registers. The visible one is report readability: automated conditional formatting with a single base color, clearer charts and tables, faster template search, and a themes panel consolidated into one place. The less visible one is architectural — the Basis integration was rebuilt to store data rather than load it live from the API each time a report opens, which fixed slow widgets and dropped connections and aligned reported spend with Basis billing totals. Integration breadth continues in parallel with Ahrefs Rank Tracker, WhatConverts, and Snowflake.
Fulcrum vs Whatagraph: editorial side-by-side
Fulcrum
5.0ANALYTICS
A weekly three-platform release train where offline computer vision is the only real bet.
◆ Current state
Fulcrum runs a tri-platform cadence — weekly web release notes plus separately versioned iOS and Android drops — and the July window is overwhelmingly maintenance: map stability, layer-format handling, offline ArcGIS reliability. The one substantive thread is the INFERENCE data event, which runs computer-vision models on device without connectivity and now reads its class labels from an uploaded labels.txt. Underneath that, the mobile map engine moved to ArcGIS SDK 300.0.0.
◆ Where it's heading
The fixes cluster in one place: offline GIS fidelity. WMS layers needing token headers, ArcGIS feature-layer downloads, custom symbols surviving an offline sync, MBTiles and KML/KMZ uploads — Fulcrum is hardening the claim that a field crew can leave connectivity behind and still see the same map they left with. The CV work pushes the same way, moving inference onto the device instead of a server round-trip. On the web side, Insights stays in beta and is getting interaction polish rather than new analytical surface.
◆ Prediction
The INFERENCE path looks unfinished — custom-model support is arriving in pieces, with labels.txt handling landing a week after the library update — so model configuration and iOS parity are the visible next gaps. Whether Insights leaves beta isn't something these entries indicate either way.
Whatagraph
5.0ANALYTICS
Whatagraph is building a data layer under the reports — storing data instead of fetching it live.
◆ Current state
Whatagraph ships in two registers. The visible one is report readability: automated conditional formatting with a single base color, clearer charts and tables, faster template search, and a themes panel consolidated into one place. The less visible one is architectural — the Basis integration was rebuilt to store data rather than load it live from the API each time a report opens, which fixed slow widgets and dropped connections and aligned reported spend with Basis billing totals. Integration breadth continues in parallel with Ahrefs Rank Tracker, WhatConverts, and Snowflake.
◆ Where it's heading
The storage-first rebuild is the pattern worth watching. Whatagraph's original model — pull from every vendor API when a client opens a report — is what makes agency reporting slow and fragile, and the company is steadily replacing it with pre-synced data it holds itself. Snowflake as a source points the same way: first-party and offline data joining paid media inside the report. The polish items are real but downstream of that; readable charts matter more once the numbers load reliably and reconcile with the platform's own billing.
◆ Prediction
The Basis rebuild reads as a template rather than a one-off, so other live-API integrations with the same slowness and drop problems are the likely next candidates for storage-backed rewrites and per-client source structure.
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.
Dagster
Dagster is spending this cycle on scale problems in the UI and correctness in asset state
Usermaven
Usermaven is outgrowing the pixel — CRM and payment conversions now count as native events.
Chord
Chord's changelog has become a Chord AI changelog — the CDP is being answered by a conversation.
AgencyAnalytics
AgencyAnalytics is selling AI search visibility as a metered add-on, not a feature.
Displayr
Displayr is making its AI legible — showing what Chat sees, what it changed, and why the error happened.
See all Fulcrum alternatives → · See all Whatagraph alternatives →
Recent activity from Fulcrum and Whatagraph
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoFulcrumAndroid 2607.3.0: map panning stability, KML/KMZ layers display
- 1d agoWhatagraphClearer charts and tables, and a faster way to find the right template
- 6d agoWhatagraphTrack your keywords against competitors with Ahrefs Rank Tracker
- 6d agoFulcrumWeb: MBTiles layer uploads and lasso record counts fixed
- 8d agoFulcrumAndroid 2607.2.0: offline ArcGIS styling fixed, labels.txt for CV
- 10d agoFulcrumiOS 2607.1.0: bug fixes and performance optimizations
- 13d agoFulcrumWeb: Insights chat closes artifact panel, media viewer flicker fixed
- 14d agoFulcrumAndroid 2607.1.0: offline custom-model CV, ArcGIS SDK 300 map engine
- 20d agoWhatagraphBasis rebuilt: faster data, cleaner numbers, per-client sources
- 1mo agoWhatagraphThemes settings, simplified
- 1mo agoWhatagraphWhatConverts data available on Whatagraph
- 2mo agoWhatagraphSnowflake, bol. Retailer & Advertising, and a rebuilt CallTrackingMetrics
Frequently asked questions
What is the difference between Fulcrum and Whatagraph?
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum and Whatagraph are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 and Whatagraph are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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.