Looker
Looker's release feed is mostly page furniture; the shipping behind it is thin.
A side-by-side editorial comparison of ApexCharts and Plotly — release velocity, themes, recent moves, and the top alternatives to consider.
ApexCharts built a paid tier in three releases, then started enforcing it
ApexCharts is shipping at a remarkable pace — six releases in under two weeks — and doing two things at once. It is adding chart types and interaction work at a steady clip: sunburst, a unit chart with six layouts, continuous heatmap axes, a bar chart race, cursor-anchored wheel zoom, and a performance release that cut scatter DOM nodes in half with byte-identical output. Simultaneously it has stood up commercial licensing, moving from no license check at all, to trial mode with a watermark, to a premium chart type, to requiring an entitled plan rather than any valid key.
The desktop app builder is pre-1.0, but Plotly Cloud quietly turned into a Dash hosting platform.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
ApexCharts is shipping at a remarkable pace — six releases in under two weeks — and doing two things at once. It is adding chart types and interaction work at a steady clip: sunburst, a unit chart with six layouts, continuous heatmap axes, a bar chart race, cursor-anchored wheel zoom, and a performance release that cut scatter DOM nodes in half with byte-identical output. Simultaneously it has stood up commercial licensing, moving from no license check at all, to trial mode with a watermark, to a premium chart type, to requiring an entitled plan rather than any valid key.
The library is converting from a fully open charting component into an open core with a paid tier, and it is doing so carefully — each step preserves existing configs, features keep working in trial mode, and the first paywalled item was a new chart type rather than something users already depended on. That sequencing matters: nothing was taken away, so the pressure lands on new capability rather than on installed usage.
Expect further chart types to launch premium-first, and the entitlement check tightened in 6.7.0 to become the mechanism through which plan tiers are differentiated.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
The centre of gravity has moved from the desktop tool to the hosting product. Studio's releases are pre-1.0 hardening — navigation, credential handling, install paths — while Cloud is the side gaining capability that changes what a customer can do, and it is where the tier boundaries are being drawn. Consumption economics are becoming explicit, with idle spend and cold starts surfaced as customer-tunable settings rather than hidden platform behaviour.
The next Cloud releases most likely extend the resource and access controls a hosted app needs — finer app sizing, or authentication and access rules on custom domains — rather than adding capability to Studio.
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 Plotly.
Looker's release feed is mostly page furniture; the shipping behind it is thin.
Fulcrum is retiring Google Maps for Esri and stabilising the ArcGIS stack behind it.
Shynet went silent for two and a half years and a security audit is what woke it up.
Power BI's monthly grind: authoring defaults, DAX documentation, and cleaner axes.
BigQuery is making itself agent-callable and pulling inference inside the SQL boundary.
Lightdash is turning BI into an app platform its users' coding agents can build against.
See all ApexCharts alternatives → · See all Plotly 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 7.5 vs 0.0), with 2 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 7.5 vs 0.0), with 2 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 Plotly alternatives in Analytics are ranked by recent ship velocity. Browse the "Plotly alternatives" section above for the current picks, or visit /alternatives/plotly for the full list with editorial commentary on each.