Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Appfigures and Metabase — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Appfigures | Metabase |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 3.8 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | app-analytics, agentic, aso, competitive-intelligence | mcp server, agentic analytics, open source ai, semantic layer |
| Last editorial update | 22h ago | 3mo ago |
| Website | — | Visit → |
Appfigures just made its app-market data something an AI agent can query, not something you screenshot.
Appfigures has spent the last year widening what its estimates cover — iPad data folded into every download and revenue figure, state-level financials in the API, a 15-report App Intelligence suite for competitor research, and Leaderboards that rank apps by explicit metrics instead of opaque store charts. The August release changes who consumes all of that: a CLI built specifically for AI agents, with a hinting system to keep them from misreading the data. The product is no longer only a dashboard.
Metabase open-sourced its AI stack and shipped an MCP server — analytics is going agentic.
Metabase's recent two releases have been the most directionally significant in years. Metabase 60 (March) open-sourced the company's AI tools, shipped an official Metabase MCP server, put Metabot inside Slack, added bring-your-own-model, plus a metrics explorer and split multi-series charts. Metabase 59 (February) introduced Data Studio — an analyst workbench with a semantic layer — and pushed AI SQL generation into the open-source edition. Earlier 55–58 work focused on Documents, embedded analytics, dark mode, and governance.
Appfigures has spent the last year widening what its estimates cover — iPad data folded into every download and revenue figure, state-level financials in the API, a 15-report App Intelligence suite for competitor research, and Leaderboards that rank apps by explicit metrics instead of opaque store charts. The August release changes who consumes all of that: a CLI built specifically for AI agents, with a hinting system to keep them from misreading the data. The product is no longer only a dashboard.
The arc runs from data completeness to data access. First they closed gaps in the underlying estimates, then they built more ways to slice them, and now they are exposing the whole surface to agents that can investigate, compare, monitor, and act — including replying to reviews and adjusting Apple Ads campaigns. Each layer assumes the one below it is trustworthy, which is why the accuracy fixes (iPad coverage, keyword popularity, Google Play delay removal) came first.
Expect the agent surface to deepen before it widens — more write actions exposed through the CLI, and Leaderboards and App Intelligence reports made directly queryable by agents rather than only through the web reports.
Metabase's recent two releases have been the most directionally significant in years. Metabase 60 (March) open-sourced the company's AI tools, shipped an official Metabase MCP server, put Metabot inside Slack, added bring-your-own-model, plus a metrics explorer and split multi-series charts. Metabase 59 (February) introduced Data Studio — an analyst workbench with a semantic layer — and pushed AI SQL generation into the open-source edition. Earlier 55–58 work focused on Documents, embedded analytics, dark mode, and governance.
The arc through 55→60 traces a clear pivot: Metabase is repositioning the BI tool around an AI-native semantic layer that any agent can call. Open-sourcing AI tooling and shipping an MCP server are sequential bets that the value is moving from 'humans clicking dashboards' to 'agents and LLMs querying business data through a governed semantic layer.' Pairing that with Slack-native Metabot and BYO model targets distribution (chat) and enterprise procurement (your model, your governance) at the same time.
Expect rapid third-party MCP integrations to follow the official server release, and AI tooling currently in OSS to become the wedge for self-hosted adoption. The next likely moves are deeper Data Studio integration with the AI generation path, and pricing tiers that bundle agentic-query usage rather than seat counts.
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 Appfigures or Metabase.
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all Appfigures alternatives → · See all Metabase alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Appfigures is currently shipping more aggressively (velocity 3.8 vs 2.5), 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. Appfigures is currently shipping more aggressively (velocity 3.8 vs 2.5), 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 Appfigures alternatives in Analytics are ranked by recent ship velocity. Browse the "Appfigures alternatives" section above for the current picks, or visit /alternatives/appfigures for the full list with editorial commentary on each.
Top Metabase alternatives in Analytics are ranked by recent ship velocity. Browse the "Metabase alternatives" section above for the current picks, or visit /alternatives/metabase for the full list with editorial commentary on each.