Omni
Omni ships weekly, and almost every week the headline item is an AI feature
Comparison · Analytics
Fulcrum vs Metabase
A side-by-side editorial comparison of Fulcrum and Metabase — release velocity, themes, recent moves, and the top alternatives to consider.
Fulcrum vs Metabase: at a glance
| Feature | Fulcrum | Metabase |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | field-data-collection, esri-arcgis, offline-maps, mobile-releases | mcp server, agentic analytics, open source ai, semantic layer |
| Last editorial update | 6h ago | 3mo ago |
| Website | — | Visit → |
What is Fulcrum?
Fulcrum is consolidating on Esri, with Google Maps gone September 1
The mapping stack is the whole story right now: ArcGIS SDK 300.0.0 on iOS, the latest ArcGIS and deck.gl on web, and a hard cutover date after which any organization still defaulting to Google Maps is switched to Esri automatically. The mobile releases in this window are almost entirely map and location fixes — basemap loading, offline symbol styling, location resolution that blocked saves. On-device inference quietly changed format, dropping ONNX.
What is Metabase?
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.
Fulcrum vs Metabase: editorial side-by-side
Fulcrum
6.3ANALYTICS
Fulcrum is consolidating on Esri, with Google Maps gone September 1
◆ Current state
The mapping stack is the whole story right now: ArcGIS SDK 300.0.0 on iOS, the latest ArcGIS and deck.gl on web, and a hard cutover date after which any organization still defaulting to Google Maps is switched to Esri automatically. The mobile releases in this window are almost entirely map and location fixes — basemap loading, offline symbol styling, location resolution that blocked saves. On-device inference quietly changed format, dropping ONNX.
◆ Where it's heading
One platform bet runs through everything: Esri as the single map engine, with Google's satellite, hybrid, and street imagery retained as basemap options so the migration costs users imagery choice, not capability. The current release cadence is stabilization work paying down that migration rather than new ground.
◆ Prediction
Expect map and location fixes to keep dominating releases through the September 1 cutover, with the Esri-only capabilities already listed — snapping, ArcGIS Feature Service connectivity, offline basemaps — becoming the default surface rather than the alternative one.
Metabase
2.5ANALYTICS
Metabase open-sourced its AI stack and shipped an MCP server — analytics is going agentic.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Fulcrum and Metabase
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 Metabase.
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
Amundsen
Amundsen's last release was a config flag, and the feed has been silent for two years
See all Fulcrum alternatives → · See all Metabase alternatives →
Recent activity from Fulcrum and Metabase
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12h agoFulcrumiOS fix for slow location resolution blocking saves
- 5d agoFulcrumMap engine updated to the latest ArcGIS and deck.gl
- 6d agoFulcrumAndroid stability fixes for ArcGIS location and signatures
- 6d agoFulcrumiOS basemap loading and map-centering fixes
- 7d agoFulcrumArcGIS SDK 300.0.0 lands; ONNX inference support removed
- 7d agoFulcrumOffline ArcGIS layers keep custom symbols and labels
- 3mo agoMetabaseScraping artifact: cookie consent page, not a release
- 4mo agoMetabaseDuplicate index capture of Metabase 60 changelog page
- 4mo agoMetabaseScraping artifact: changelog index page, not a release
- 4mo agoMetabaseMetabase 60 ⚡
- 4mo agoMetabaseScraping artifact: newsletter signup module, not a release
- 5mo agoMetabaseMetabase 59 ⚡
Frequently asked questions
What is the difference between Fulcrum and Metabase?
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Metabase?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Metabase?
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.