Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of ApexCharts and vellumplot — release velocity, themes, recent moves, and the top alternatives to consider.
Licensing settled, ApexCharts is back to changing what a chart can take as input.
ApexCharts is deep into a fast v6 line, shipping roughly weekly. The licensing arc that dominated 6.5 through 6.7 — trial watermarks, the first premium-gated chart type, then entitlement checks — has settled, and the last three releases are library work again. 6.9.0 is the largest of them: a histogram type that bins raw samples, a morph engine that conserves marks across chart types, and the end of the library's dependency-free packaging.
vellumplot tags its first release with a bet most R grammars don't make: the static figure and the widget are the same object.
A new grammar of graphics built on the vellum vector engine, developing fast — ten releases in roughly three weeks — and now at its first tagged release. The distinguishing architectural claim is that the compiled plot is the scene, so a static export and an interactive widget cannot drift apart, and that it renders without a graphics device because vellum measures text itself. Accessibility is treated as a first-class output rather than an afterthought: tagged PDF with a navigable structure tree and alt text, a plot_lint() check, and colour-vision-deficiency simulation at render time.
ApexCharts is deep into a fast v6 line, shipping roughly weekly. The licensing arc that dominated 6.5 through 6.7 — trial watermarks, the first premium-gated chart type, then entitlement checks — has settled, and the last three releases are library work again. 6.9.0 is the largest of them: a histogram type that bins raw samples, a morph engine that conserves marks across chart types, and the end of the library's dependency-free packaging.
The through-line now is input and arrangement rather than catalogue size. Charts increasingly accept the measurements a team actually has instead of pre-aggregated values, and the seams that let you hand a chart its own layout — plotOptions.unit.positions, the pluggable layout hook — are being filled in with kits rather than hard-coded options. The premium boundary has stopped moving; the free catalogue keeps growing around it.
Expect the raw-observation pattern to reach another chart type now that the bar pathway handles binning, and expect the remaining pluggable seams to get companion kits the way positions just did.
A new grammar of graphics built on the vellum vector engine, developing fast — ten releases in roughly three weeks — and now at its first tagged release. The distinguishing architectural claim is that the compiled plot is the scene, so a static export and an interactive widget cannot drift apart, and that it renders without a graphics device because vellum measures text itself. Accessibility is treated as a first-class output rather than an afterthought: tagged PDF with a navigable structure tree and alt text, a plot_lint() check, and colour-vision-deficiency simulation at render time.
The release sequence shows a grammar filling in ggplot2-parity features and specialist marks in parallel. Parity work landed as secondary axes, rich legend titles, and Sankey styling; the specialist end added categorical datashading, image marks, flow maps and edge bundling for dense graphs. Version 0.7.0 shows a willingness to break early — vsunburst() was removed outright in favour of one vhierarchy() constructor covering sunburst, icicle, treemap and circlepack — which is the right time to do it and suggests the API is still being consolidated toward fewer, more general constructors.
Expect more consolidation of near-duplicate constructors under type arguments and continued expansion of the declarative interactivity introduced in 0.7.0, now that the first tagged release has fixed a public API surface.
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 vellumplot.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all ApexCharts alternatives → · See all vellumplot 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 1. 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 1. 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 vellumplot alternatives in Analytics are ranked by recent ship velocity. Browse the "vellumplot alternatives" section above for the current picks, or visit /alternatives/vellumplot for the full list with editorial commentary on each.