RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of Dovetail and modeltime.resample — release velocity, themes, recent moves, and the top alternatives to consider.
Dovetail is wiring itself into every tool its users already work in, and now pushes back out to them.
Dovetail sits at the center of a heavy integration cycle. Agents reached general availability in July, Channels 2.0 entered closed beta, and Docs went from launch to steady polish. Around that core, the connectors keep multiplying: Snowflake into Channels, HubSpot tickets and contact enrichment, a Microsoft Copilot connector, and MCP tools reachable from chat.
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.
Dovetail sits at the center of a heavy integration cycle. Agents reached general availability in July, Channels 2.0 entered closed beta, and Docs went from launch to steady polish. Around that core, the connectors keep multiplying: Snowflake into Channels, HubSpot tickets and contact enrichment, a Microsoft Copilot connector, and MCP tools reachable from chat.
The product is moving from a research repository to a signal router. Inbound, it pulls from wherever customer signal already lives — warehouses, CRMs, support queues. Outbound, one-click actions now send a Doc, data point, or Channels idea straight into the tool where the work happens. The AI layer is being tuned rather than expanded: project-level context is a briefing step that shapes classification quality before the model touches the data.
Channels 2.0 graduating from closed beta is the obvious next milestone, and the one-click action menu is the natural place for more destinations to land. More warehouse and CRM sources are likely given the Snowflake and HubSpot pattern.
modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.
Every entry here is compatibility work against something upstream — hardhat 1.0.0, workflows regression mode, then tune 2.0.0 twice. The 0.3.0 notes show a second concern emerging alongside it: making failures legible, with .notes on failed fits, actionable errors from unnest_modeltime_resamples(), and fallback logic when prediction columns go missing across versions. Reproducibility gets the same treatment through explicit seeding.
Expect the next release to track the next tidymodels breaking change, with any new work continuing on error reporting rather than resampling strategies.
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 modeltime.resample.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all Dovetail alternatives → · See all modeltime.resample 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 modeltime.resample alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.resample alternatives" section above for the current picks, or visit /alternatives/modeltime-resample for the full list with editorial commentary on each.