Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of Plotly and TLF-Library — release velocity, themes, recent moves, and the top alternatives to consider.
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.
The Open Systems Pharmacology plotting layer spent 2025 absorbing a ggplot2 major break.
tlf is the plotting library behind Open Systems Pharmacology's tables, listings and figures — a ggplot2 wrapper producing the PK/PD reporting output the OSP suite generates. Recent work splits into two strands: a feature set adding Lower Limit Of Quantification annotation to time-profile and observed-vs-predicted plots alongside a reworked axis-limits API, and then hot fixes to survive ggplot2 v4.0.0's breaking changes. The axis change is the substantive one, separating cropping the view from filtering the data behind it.
Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.
The Cloud releases are assembling the standard pieces of a hosting business in order — identity first (domain verification, explicitly framed as the step before SSO), then billing (viewer seats, then metered compute credits), and now production-grade serving (custom domains, automatic certificate renewal). Studio is being hardened as the authoring front end that feeds it: Universal Deployment pushed beyond Dash apps, credentials saved once and reused, a Winget channel to widen Windows installs, and in v0.0.86 a rebuilt session engine plus automatic retries so agent runs survive expired tokens. The two tracks converge on one funnel — author in Studio, deploy to Cloud, pay by compute consumed.
The Domain Verification entry names SSO as the next step and places it in the Enterprise tier, so single sign-on is the most likely Cloud release next. Studio should hold its one-to-two-week cadence, with the newly added app thumbnails pointing toward more work on browsing and organizing generated apps.
tlf is the plotting library behind Open Systems Pharmacology's tables, listings and figures — a ggplot2 wrapper producing the PK/PD reporting output the OSP suite generates. Recent work splits into two strands: a feature set adding Lower Limit Of Quantification annotation to time-profile and observed-vs-predicted plots alongside a reworked axis-limits API, and then hot fixes to survive ggplot2 v4.0.0's breaking changes. The axis change is the substantive one, separating cropping the view from filtering the data behind it.
The library is maturing into a stable reporting dependency rather than growing new plot types — the newest releases are watermark placement, log-tick safety and upstream compatibility, not new figures. Its exposure is to ggplot2: v4.0.0 required same-day hot fixes, which is the risk profile of a wrapper this thin. Note that this feed's version numbers and publication stamps disagree, with 1.5.170 stamped four months before the lower-numbered 1.5.158, so the release order has to be read from version numbers and the changelog ranges rather than from the feed order.
With the ggplot2 v4 fallout patched and the LLOQ work promoted to a stable 1.6 line, the next releases most likely continue as small rendering fixes. Nothing in these entries points to a new plot class in progress.
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 Plotly or TLF-Library.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
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.
OpenCTI spends a release unblocking queues and hardening upserts
See all Plotly alternatives → · See all TLF-Library alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Plotly is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Plotly is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 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.
Top TLF-Library alternatives in Analytics are ranked by recent ship velocity. Browse the "TLF-Library alternatives" section above for the current picks, or visit /alternatives/tlf-library for the full list with editorial commentary on each.