Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of labelled and Plotly — release velocity, themes, recent moves, and the top alternatives to consider.
The bridge between Stata/SPSS labelled data and tidy R keeps widening, one integration at a time.
labelled manages variable labels, value labels and user-defined missing values on data imported from Stata, SPSS and SAS, filling the gap between those formats' metadata and R's native types. Recent releases have pushed outward from the core label accessors: survey design objects from the survey package are now supported throughout, look_for() results can be rendered as formatted gt tables, and dictionary data frames convert in both directions. Error messaging moved wholesale to cli in 2.14.0.
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.
labelled manages variable labels, value labels and user-defined missing values on data imported from Stata, SPSS and SAS, filling the gap between those formats' metadata and R's native types. Recent releases have pushed outward from the core label accessors: survey design objects from the survey package are now supported throughout, look_for() results can be rendered as formatted gt tables, and dictionary data frames convert in both directions. Error messaging moved wholesale to cli in 2.14.0.
The arc is toward being usable wherever labelled data ends up, not just where it is loaded. Each recent release either extends support to another object type — survey designs, packed columns, plain vectors, tibbles with list columns — or adds a conversion path between labels and some other representation. The look_for() search function has become a second centre of gravity alongside the label accessors, accumulating its own output formats and long-format conversions.
The pattern of adding compatibility with one more object type or output format per release is stable and likely continues. Nothing in these entries indicates a change to the underlying haven_labelled representation the package is built on.
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.
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 labelled or Plotly.
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 labelled 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. 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 labelled alternatives in Analytics are ranked by recent ship velocity. Browse the "labelled alternatives" section above for the current picks, or visit /alternatives/labelled 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.