dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
A side-by-side editorial comparison of Plotly and qtl2convert — 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 conversion utility in pure maintenance mode, tracking R-devel breakage release by release
qtl2convert is the format-shim of the R/qtl2 ecosystem: it moves genotype probabilities and genetic maps between DOQTL, R/qtl and R/qtl2 representations. The last three releases contain no new conversion functions at all — 0.32 fixed a C string comparison flagged by CRAN, 0.34 restored attribute-clearing that R-devel 4.7 changed underneath the package, and 0.36 adjusted parallel core defaults plus a test tweak. The functional surface has been stable since 0.26 added cross2_ril_to_genril().
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.
qtl2convert is the format-shim of the R/qtl2 ecosystem: it moves genotype probabilities and genetic maps between DOQTL, R/qtl and R/qtl2 representations. The last three releases contain no new conversion functions at all — 0.32 fixed a C string comparison flagged by CRAN, 0.34 restored attribute-clearing that R-devel 4.7 changed underneath the package, and 0.36 adjusted parallel core defaults plus a test tweak. The functional surface has been stable since 0.26 added cross2_ril_to_genril().
This is a package whose release cadence is driven by its dependencies, not its roadmap. Two of the last three releases exist purely because upstream R or CRAN's check suite moved; the maintainer responds within weeks and ships. The cores=0 change in 0.36 is the only user-visible behavior shift in over a year, and it landed simultaneously in sibling package qtl2fst — this is a maintainer-wide convention change, not a qtl2convert decision.
Expect the next release to be triggered by another R-devel or CRAN check change rather than a feature request, following the same pattern as 0.32 and 0.34.
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 qtl2convert.
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
AgencyAI got skills three weeks ago; everything since has been making them routine.
See all Plotly alternatives → · See all qtl2convert 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 qtl2convert alternatives in Analytics are ranked by recent ship velocity. Browse the "qtl2convert alternatives" section above for the current picks, or visit /alternatives/qtl2convert for the full list with editorial commentary on each.