Umami
Umami spent late 2025 patching Next.js CVEs, then shipped Boards and Session Replay in v3.1.0.
A side-by-side editorial comparison of Whatagraph and MotherDuck — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Whatagraph | MotherDuck |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | marketing-reporting, agencies, integrations, data-storage | duckdb, agent-native, mcp, iceberg |
| Last editorial update | 2h ago | 2h ago |
| Website | — | Visit → |
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.
DuckDB in the cloud is turning into an agent's workspace, not just a query engine.
MotherDuck runs DuckDB as a managed service with hybrid local/cloud execution, and its release notes read as weekly batches rather than headline launches. The past two months added the pieces an analytics platform needs to be bought rather than tried: RBAC, SCIM, regional coverage in Dublin, Sydney, and Tokyo, and a Postgres wire endpoint that lets Looker, dbt Cloud, DBeaver, and DataGrip connect without a custom driver. Alongside that, Dives (shareable data apps) went GA and Flights (Python data pipelines) went from Preview to available on every plan.
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.
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.
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.
MotherDuck runs DuckDB as a managed service with hybrid local/cloud execution, and its release notes read as weekly batches rather than headline launches. The past two months added the pieces an analytics platform needs to be bought rather than tried: RBAC, SCIM, regional coverage in Dublin, Sydney, and Tokyo, and a Postgres wire endpoint that lets Looker, dbt Cloud, DBeaver, and DataGrip connect without a custom driver. Alongside that, Dives (shareable data apps) went GA and Flights (Python data pipelines) went from Preview to available on every plan.
The clearer arc is that every new surface is built to be driven by an agent as well as a human. Flights are creatable via SQL, UI, or any MCP client; Dives carry statuses that the MCP tools filter on; MCP responses moved to a token-efficient encoding; and the newest release adds Guides, where an organization's metric definitions and join rules live in MotherDuck and get read automatically by agents through MCP. In parallel, the storage story keeps opening outward — Databricks-managed Iceberg writes, Cloudflare R2 as a persisted Iceberg catalog, server-side attach of external Iceberg REST catalogs — so MotherDuck queries data it does not own.
Guides is the piece to watch: expect it to leave Preview with governance attached — versioning, ownership, and the ability to require a guide before an agent writes SQL — since a shared definition layer is only trustworthy if someone controls it.
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 Whatagraph or MotherDuck.
Umami spent late 2025 patching Next.js CVEs, then shipped Boards and Session Replay in v3.1.0.
ADManager Plus opened to third-party identity apps in January, then shipped six months of fixes.
Five of six VictoriaMetrics entries are scraped GitHub page furniture; one is a real LTS patch.
Sigma is moving data modeling out of its own UI and into the terminal.
Steady administrative depth for M365, punctuated by a run of serious security fixes.
An on-prem M365 auditing tool whose releases are mostly dependency hygiene.
See all Whatagraph alternatives → · See all MotherDuck alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. MotherDuck 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. MotherDuck 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.
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.
Top MotherDuck alternatives in Analytics are ranked by recent ship velocity. Browse the "MotherDuck alternatives" section above for the current picks, or visit /alternatives/motherduck for the full list with editorial commentary on each.