Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Comparison · Analytics
Hex vs Whatagraph
A side-by-side editorial comparison of Hex and Whatagraph — release velocity, themes, recent moves, and the top alternatives to consider.
Hex vs Whatagraph: at a glance
| Feature | Hex | Whatagraph |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | agents, cli, mcp, model-routing | marketing-reporting, agencies, integrations, data-storage |
| Last editorial update | 21h ago | 12d ago |
| Website | — | — |
What is Hex?
Hex is moving its agent out of the notebook and onto programmable surfaces.
Hex ships a fortnightly digest, and the through-line across the last ten is agent reach. The agent now runs from a CLI and API, appears inside Codex, acts as an MCP client against the user's own apps, can search the web, and can see the generative apps it builds. Alongside that, the model layer has become a customer-facing control: a picker, an admin-set default, Auto with visible attribution, and a rotating roster including Fable 5, Kimi K2.7, Claude Opus 5 and GPT-5.6.
What is Whatagraph?
Marketing reporting quietly rebuilding itself around stored data instead of live API calls.
Whatagraph builds client reports for marketing agencies by pulling from dozens of ad, analytics, and call-tracking sources. The recent releases split into two groups. One keeps widening the source catalog — Snowflake as a warehouse source, WhatConverts lead data, and Ahrefs Rank Tracker as a keyword-level integration separate from the existing domain-level Ahrefs. The other attacks reliability: a Data Storage destination that pre-syncs data so widgets stop waiting on live APIs, the Basis integration rebuilt on that model, and automatic failover when the team member whose account owns a source loses access.
Hex vs Whatagraph: editorial side-by-side
Hex
6.3ANALYTICS
Hex is moving its agent out of the notebook and onto programmable surfaces.
◆ Current state
Hex ships a fortnightly digest, and the through-line across the last ten is agent reach. The agent now runs from a CLI and API, appears inside Codex, acts as an MCP client against the user's own apps, can search the web, and can see the generative apps it builds. Alongside that, the model layer has become a customer-facing control: a picker, an admin-set default, Auto with visible attribution, and a rotating roster including Fable 5, Kimi K2.7, Claude Opus 5 and GPT-5.6.
◆ Where it's heading
Hex is positioning the agent as a component other systems call rather than a feature users visit. Governance is being built out in parallel — spend limits, credit usage controls, enterprise role-request controls, signed embedding — which is the pattern of a product preparing for programmatic usage it does not directly supervise. The generative-app surface is drifting the same way, from generated output toward editable, brandable, embeddable artifacts.
◆ Prediction
Expect the CLI and API surface to deepen before the notebook UI gains much, with more of Context Studio and app management reachable programmatically, and expect the spend and role controls to keep pace as headless usage grows.
Whatagraph
5.0ANALYTICS
Marketing reporting quietly rebuilding itself around stored data instead of live API calls.
◆ Current state
Whatagraph builds client reports for marketing agencies by pulling from dozens of ad, analytics, and call-tracking sources. The recent releases split into two groups. One keeps widening the source catalog — Snowflake as a warehouse source, WhatConverts lead data, and Ahrefs Rank Tracker as a keyword-level integration separate from the existing domain-level Ahrefs. The other attacks reliability: a Data Storage destination that pre-syncs data so widgets stop waiting on live APIs, the Basis integration rebuilt on that model, and automatic failover when the team member whose account owns a source loses access.
◆ Where it's heading
The reporting layer is being made boring in the good sense. Live-API reports break in ways an agency cannot explain to a client — a token expires, someone leaves, a widget goes blank mid-presentation — and the last few months answer each of those failure modes directly: store the data, align spend figures with the vendor's own billing totals, and silently switch to a colleague's credentials when one account stops working. The presentation work is following the same instinct, replacing per-metric threshold rules with automatic shading and consolidating scattered style settings into themes. Less configuration to maintain, fewer ways for a report to be wrong in front of a client.
◆ Prediction
Credential failover currently rescues a source when someone else on the team happens to have access; the gap it exposes is agency-owned connections that do not depend on an individual at all, which is where this thread points next.
Alternatives to Hex 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 Hex or Whatagraph.
Omni
Omni ships weekly, and almost every week the headline item is an AI feature
OpenDataDiscovery
Four ODD Platform releases in two weeks, and not one of them changes the product
Apache Baremaps
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ
Deequ ships GitHub tags whose release notes are one commit message long
Marquez
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all Hex alternatives → · See all Whatagraph alternatives →
Recent activity from Hex and Whatagraph
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoHexFast mode, GPT-5.6, and visible model attribution for Auto
- 12d agoWhatagraphOne broken connection won't break your reports
- 13d agoHexHex Agent becomes callable from the CLI and API ⚡
- 13d agoWhatagraphClearer charts and tables, and a faster way to find the right template
- 18d agoWhatagraphTrack your keywords against competitors with Ahrefs Rank Tracker
- 22d agoHexEditable generative-app code, and an agent that sees what it builds
- 29d agoHexMore control over credits, thread metadata, and role requests
- 1mo agoWhatagraphBasis rebuilt: faster data, cleaner numbers, per-client sources
- 1mo agoHexTwo new models and more controls over generative apps
- 1mo agoHexHex in Figma, IAM role support for AWS, and schema refresh history!
- 1mo agoWhatagraphThemes settings, simplified
- 2mo agoWhatagraphWhatConverts data available on Whatagraph
Frequently asked questions
What is the difference between Hex and Whatagraph?
They serve adjacent needs but don't currently overlap on shipped themes. Hex is currently shipping more aggressively (velocity 6.3 vs 5.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.
Is Hex better than Whatagraph?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Hex is currently shipping more aggressively (velocity 6.3 vs 5.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.
What are the best alternatives to Hex?
Top Hex alternatives in Analytics are ranked by recent ship velocity. Browse the "Hex alternatives" section above for the current picks, or visit /alternatives/hex 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.