Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of Plotly and tglkmeans — 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.
A k-means implementation that just told users their Spearman clustering on missing data was wrong
tglkmeans is a multi-core k-means implementation with seeding, aimed at single-cell and other large matrix workloads. Version 0.4.0 flipped the id_column default and moved to R's random number generator, 0.5.x added count-matrix downsampling and fixed id handling, and 0.6.3 in May 2026 is a correctness release: Spearman distance was ranking missing values as the largest value instead of dropping them, and predict_tgl_kmeans() with Euclidean distance did not reproduce the training metric when a cluster center had a missing dimension.
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.
tglkmeans is a multi-core k-means implementation with seeding, aimed at single-cell and other large matrix workloads. Version 0.4.0 flipped the id_column default and moved to R's random number generator, 0.5.x added count-matrix downsampling and fixed id handling, and 0.6.3 in May 2026 is a correctness release: Spearman distance was ranking missing values as the largest value instead of dropping them, and predict_tgl_kmeans() with Euclidean distance did not reproduce the training metric when a cluster center had a missing dimension.
The package handles missing data across three distance metrics, and 0.6.3 shows those paths had drifted apart — Spearman behaved unlike Euclidean and Pearson, and prediction behaved unlike training. Both fixes change results on affected data, and the release notes are careful to bound exactly where: Spearman on data with NAs changes, complete data does not. Performance work runs alongside, with the dense per-thread vote matrix removed from the reassignment step.
With the metric paths now aligned on missing-value handling, further work is more likely to target the parallel reassignment internals than the distance semantics.
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 tglkmeans.
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 tglkmeans 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 tglkmeans alternatives in Analytics are ranked by recent ship velocity. Browse the "tglkmeans alternatives" section above for the current picks, or visit /alternatives/tglkmeans for the full list with editorial commentary on each.