Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of ApexCharts and Metabase — release velocity, themes, recent moves, and the top alternatives to consider.
Three releases in three weeks moved ApexCharts from free library to gated open-core.
ApexCharts is shipping the v6 line at an unusual clip — ten releases since 20 July, spanning a plugin platform, a hybrid SVG/canvas renderer, and two new chart types. The core is still zero-dependency and SVG-first, and every release states that existing configs render unchanged. What is new is a commercial layer: an offline licence check now sits over seven premium modules and one chart type, while the free catalogue keeps expanding alongside it.
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.
ApexCharts is shipping the v6 line at an unusual clip — ten releases since 20 July, spanning a plugin platform, a hybrid SVG/canvas renderer, and two new chart types. The core is still zero-dependency and SVG-first, and every release states that existing configs render unchanged. What is new is a commercial layer: an offline licence check now sits over seven premium modules and one chart type, while the free catalogue keeps expanding alongside it.
The commercialisation arc tightens one notch per release. 6.5.0 introduced licensing with a watermark and an explicit promise that no chart type would be gated; 6.6.0 gated one; 6.7.0 changed enforcement from accepting any valid key to requiring an entitled plan. Running underneath is a genuine engineering push — incremental updateSeries, canvas cell rendering, a numeric fast path for line and area — that makes the paid layer easier to justify. The pattern is a generous free core with the new authoring and analysis surface behind a key.
Expect more premium chart types following `unit`, since the gating machinery and trial-mode watermark are now built and proven. The shared key format across the apex* family suggests entitlement checks propagate to the sibling libraries next.
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 ApexCharts 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 ApexCharts 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. ApexCharts is currently shipping more aggressively (velocity 10.0 vs 2.5), with 3 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. ApexCharts is currently shipping more aggressively (velocity 10.0 vs 2.5), with 3 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 ApexCharts alternatives in Analytics are ranked by recent ship velocity. Browse the "ApexCharts alternatives" section above for the current picks, or visit /alternatives/apexcharts 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.