Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of ApexCharts and Count — 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.
Count is turning its BI canvas into a governed, agent-operated analytics platform.
Count is a data-canvas analytics tool reorganizing itself around an AI agent. In two months it shipped a full public REST API and hosted MCP server (governed agent access via OAuth and service accounts), a major agent upgrade that lets the agent read and edit the entire canvas and answer from Slack, and the ability to plug external MCP servers (Linear, HubSpot, Stripe, Slack, Drive) into the agent. Around the agent it keeps broadening warehouse support—ClickHouse, Snowflake semantic models, OSI—alongside chart and UX polish.
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.
Count is a data-canvas analytics tool reorganizing itself around an AI agent. In two months it shipped a full public REST API and hosted MCP server (governed agent access via OAuth and service accounts), a major agent upgrade that lets the agent read and edit the entire canvas and answer from Slack, and the ability to plug external MCP servers (Linear, HubSpot, Stripe, Slack, Drive) into the agent. Around the agent it keeps broadening warehouse support—ClickHouse, Snowflake semantic models, OSI—alongside chart and UX polish.
Count is building toward analytics where agents are first-class operators: a governed API/MCP layer for access, an agent that drives the canvas end to end, external tool reach via MCP, and connection-level context so guidance is captured once and inherited. Governance—permissions, scopes, service accounts—is the enabling layer that makes agent access acceptable in real data stacks rather than a bolt-on.
Expect more connection- and warehouse-level context controls, a widening catalog of supported external MCP integrations, and deeper Slack-native agent workflows.
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 Count.
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 Count 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 6.3), 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 6.3), 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 Count alternatives in Analytics are ranked by recent ship velocity. Browse the "Count alternatives" section above for the current picks, or visit /alternatives/count for the full list with editorial commentary on each.