Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of Dovetail and slope — release velocity, themes, recent moves, and the top alternatives to consider.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
August has been a run of small surface work aimed at the same problem: getting into and around the workspace. Cover images with rich previews and dedicated icons make content browsable, digital twins gained a direct chat link and their own creation option instead of requiring a generic agent first, chat context now survives the jump to fullscreen, and the chat footer was thinned out. July's work pointed outward instead — one-click actions that send a Doc, data point, or Channels idea to the tool where it will be acted on, and a Snowflake integration bringing warehouse data into Channels.
A year after gutting itself for a C++ rewrite, SLOPE is back to polishing the interface
SLOPE fits sorted L-one penalized regression models. In July 2025 it replaced its entire solver with the external libslope C++ library, removing the ADMM solver, dropping debugging fields, changing alpha scaling and warning users directly that the breakage was extensive. The releases since have rebuilt convenience on top of that core: summary() and refit() methods for cross-validated objects, automatic refitting in cvSLOPE(), and a threading default reduced from half the available cores to one.
August has been a run of small surface work aimed at the same problem: getting into and around the workspace. Cover images with rich previews and dedicated icons make content browsable, digital twins gained a direct chat link and their own creation option instead of requiring a generic agent first, chat context now survives the jump to fullscreen, and the chat footer was thinned out. July's work pointed outward instead — one-click actions that send a Doc, data point, or Channels idea to the tool where it will be acted on, and a Snowflake integration bringing warehouse data into Channels.
The digital twin is quietly becoming the product's front door. Three separate releases this month reduced the friction of creating one, sharing one, and holding a conversation with one, which is more attention than any other surface received. Around it the interface is being simplified rather than extended — fewer controls in the footer, previews instead of lists, context that persists across views. Nothing in this window adds a capability; the whole month is about making existing ones reachable.
Expect the sharing path to keep widening — permissions, guest access, or an embed for a twin link — since a link that opens straight into chat only pays off if it can safely leave the workspace.
SLOPE fits sorted L-one penalized regression models. In July 2025 it replaced its entire solver with the external libslope C++ library, removing the ADMM solver, dropping debugging fields, changing alpha scaling and warning users directly that the breakage was extensive. The releases since have rebuilt convenience on top of that core: summary() and refit() methods for cross-validated objects, automatic refitting in cvSLOPE(), and a threading default reduced from half the available cores to one.
The arc runs rewrite, then repair, then convenience. The 1.2.0 release is the repair phase — coefficients_scaled was returning unscaled values, which silently affected every coef.SLOPE() call — and 2.0.0 onward is convenience, with refit() now working without re-supplying training data. The tag timestamps are non-monotonic: 1.0.1 is stamped a minute after 1.1.0 despite the lower version, so ordering here reflects when tags were pushed, not what superseded what.
With the cross-validation workflow now closing itself out through automatic refitting, further work is more likely to extend the summary and plotting surface than to touch the solver again.
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 Dovetail or slope.
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
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.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
See all Dovetail alternatives → · See all slope alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dovetail is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. Dovetail is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Dovetail alternatives in Analytics are ranked by recent ship velocity. Browse the "Dovetail alternatives" section above for the current picks, or visit /alternatives/dovetail for the full list with editorial commentary on each.
Top slope alternatives in Analytics are ranked by recent ship velocity. Browse the "slope alternatives" section above for the current picks, or visit /alternatives/slope for the full list with editorial commentary on each.