Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of Dovetail and vellumverse — 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 meta-package whose entire changelog is a version pin, tracking an ecosystem moving faster than it is.
vellumverse attaches the vellum graphics ecosystem in one library() call, reports which versions loaded, lists the bundled packages and surfaces functions masked across them. It is deliberately dependency-light, having dropped rlang and declared only what the conflict reporter actually uses. Since 0.2.0 every release has been a version pin bump rather than new behaviour of its own.
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.
vellumverse attaches the vellum graphics ecosystem in one library() call, reports which versions loaded, lists the bundled packages and surfaces functions masked across them. It is deliberately dependency-light, having dropped rlang and declared only what the conflict reporter actually uses. Since 0.2.0 every release has been a version pin bump rather than new behaviour of its own.
The release record is an index of other packages' work: four of the last six entries do nothing but raise the floor on vellum, vellumplot and vellumwidget. The cadence tells the real story, with pins moving roughly weekly and each bump chasing a minor release somewhere downstream, so the meta-package is currently a distribution convenience rather than a component. The one genuinely structural release in the window was 0.2.1, which trimmed the dependency surface to keep an attach-only package cheap to install.
Expect the pin bumps to keep pace with the ecosystem's weekly releases rather than any feature of its own, and the pin on vellumplot to move again as the interaction grammar the widget now depends on continues to land. Whether vellumverse ever grows beyond attach-and-report is not visible in these entries.
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 vellumverse.
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 vellumverse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dovetail and vellumverse are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 and vellumverse are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 vellumverse alternatives in Analytics are ranked by recent ship velocity. Browse the "vellumverse alternatives" section above for the current picks, or visit /alternatives/vellumverse for the full list with editorial commentary on each.