Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of Dovetail and rATTAINS — 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.
The R client for EPA water quality data spent two releases undoing its own promises about data shape.
rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.
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.
rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.
The direction is toward a thinner, lower-maintenance wrapper. Caching went in 0.1.4 when hoardr was archived, tidyjson and janitor went earlier, tibblify went in 1.1.0, and each removal handed a little more data-shaping responsibility back to the user — the current advice is to pass .unnest = FALSE and rectangle the results with whatever tidying package you prefer. Release cadence is slow and mostly reactive: upstream API terms, archived dependencies, and compatibility with test tooling account for most of the log. The package's centre of gravity is staying installable and honest about what ATTAINS returns rather than smoothing it over.
Given the pattern, the next release is likelier to be a compatibility or upstream-driven fix than new endpoint coverage; how the API key requirement affects users in scripted and CI contexts is the obvious open question the entries do not yet answer.
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 rATTAINS.
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 rATTAINS 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 rATTAINS alternatives in Analytics are ranked by recent ship velocity. Browse the "rATTAINS alternatives" section above for the current picks, or visit /alternatives/rattains for the full list with editorial commentary on each.