ApexCharts
ApexCharts built a paid tier in three releases, then started enforcing it
A side-by-side editorial comparison of billboard.js and Mage — release velocity, themes, recent moves, and the top alternatives to consider.
billboard.js is adding a canvas renderer — an SVG chart library admitting SVG has a ceiling.
The library is mid-flight on a 4.0.0 pre-release train, and the defining addition is a canvas rendering mode alongside the existing SVG output. The same first candidate made grid, regions and category modules tree-shakable, added file extensions to type declarations, and exported shape option types from the main entry. Everything published since has been canvas follow-up: background image positioning, rendering and touch-interaction parity, candlestick labels aligned to wick endpoints.
Feature releases every two months in 2024; one bugfix release in the last twelve.
The release cadence has collapsed. Through 2024 Mage shipped roughly every two months with substantial features each time — memory management rework, dynamic blocks, new sources and destinations, Python 3.11 and 3.12 support. 2025 produced two releases. The most recent entry, 0.9.79 in January 2026, contains no feature section at all: it is dependency pinning, SQLAlchemy 2.0 compatibility, character escaping during code interpolation, and log file handle cleanup. Nothing has followed it in the six months since.
The library is mid-flight on a 4.0.0 pre-release train, and the defining addition is a canvas rendering mode alongside the existing SVG output. The same first candidate made grid, regions and category modules tree-shakable, added file extensions to type declarations, and exported shape option types from the main entry. Everything published since has been canvas follow-up: background image positioning, rendering and touch-interaction parity, candlestick labels aligned to wick endpoints.
Two constraints are being addressed at once. Canvas is the answer to dataset sizes where per-point DOM nodes stop being viable, and the fact that three consecutive candidates are spent on parity fixes shows how much behaviour an SVG-native library has to re-implement to make the alternative renderer feel identical. Tree-shakable modules attack the other constraint — bundle weight — which matters to exactly the same teams choosing a chart library on performance grounds.
Expect further candidates before 4.0.0 stable, still weighted toward canvas parity in interaction and label placement, since that is where every candidate so far has landed.
The release cadence has collapsed. Through 2024 Mage shipped roughly every two months with substantial features each time — memory management rework, dynamic blocks, new sources and destinations, Python 3.11 and 3.12 support. 2025 produced two releases. The most recent entry, 0.9.79 in January 2026, contains no feature section at all: it is dependency pinning, SQLAlchemy 2.0 compatibility, character escaping during code interpolation, and log file handle cleanup. Nothing has followed it in the six months since.
The arc runs from expanding the product to keeping it compiling. The 2024 releases added capability — a canvas rework, multi-project support, streaming sinks, Kubernetes job parameters. The 2025 releases shifted toward integrations and CVE response, including a batch of path traversal fixes carrying assigned identifiers. The last release is entirely defensive, including vendoring croniter into the repository and locking scikit-learn to stop upstream changes from breaking builds. That is the profile of a codebase being kept viable rather than developed.
The entries give no basis for predicting the next release — a six-month gap after a dependency-only patch is the only signal available, and nothing here indicates whether the line is paused or finished.
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 billboard.js or Mage.
ApexCharts built a paid tier in three releases, then started enforcing it
Citus keeps three Postgres branches alive while chasing each new major
Three releases in a year, all of them about the Vega dependency — the feed shows nothing else.
Kylin ships once a year with empty release notes and a native engine nobody is being told about.
Iceberg's release cadence is now backports and CVE patches across three live minor lines.
MCP servers became first-class governed assets in 1.13.0 — and 2.0 is now in release candidate.
See all billboard.js alternatives → · See all Mage alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. billboard.js and Mage are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. billboard.js and Mage are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top billboard.js alternatives in Analytics are ranked by recent ship velocity. Browse the "billboard.js alternatives" section above for the current picks, or visit /alternatives/billboard-js for the full list with editorial commentary on each.
Top Mage alternatives in Analytics are ranked by recent ship velocity. Browse the "Mage alternatives" section above for the current picks, or visit /alternatives/mage-ai for the full list with editorial commentary on each.