RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of modeltime.ensemble and MotherDuck — release velocity, themes, recent moves, and the top alternatives to consider.
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
MotherDuck keeps wrapping its agent-native stack in the plumbing enterprises need to adopt it.
The two capabilities MotherDuck has bet on — Flights for Python pipelines that MCP agents can drive, and Guides for the organizational context those agents read automatically — are now surrounded by the operational layer that makes them usable at scale: RBAC, org-wide admin visibility, regional availability in Sydney and Tokyo, runtime limits. The August 14 release adds the client surface that was still missing, a CLI covering auth, queries, Dives and Flights with scriptable output.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
This is a package whose forecasting capability was settled by 2021 — recursive ensembles, per-series calibration — and whose recent life is dictated entirely by upstream tidymodels churn. New contributors did that compatibility work, including one from the tidymodels side. It now requires tune 2.0.0 and modeltime.resample 0.3.0, pinning it to the current tidymodels generation rather than straddling versions.
Expect the next release to follow the next tune or modeltime.resample breaking change rather than to introduce new ensembling methods.
The two capabilities MotherDuck has bet on — Flights for Python pipelines that MCP agents can drive, and Guides for the organizational context those agents read automatically — are now surrounded by the operational layer that makes them usable at scale: RBAC, org-wide admin visibility, regional availability in Sydney and Tokyo, runtime limits. The August 14 release adds the client surface that was still missing, a CLI covering auth, queries, Dives and Flights with scriptable output.
The pattern is consistent: ship an agent-facing capability, then spend the following weeks making it governable and reachable. Iceberg interoperability keeps widening — Databricks-managed tables, Cloudflare R2 as a persisted catalog, server-side attach — which positions MotherDuck as a compute engine over catalogs it does not own. The CLI extends the same logic to automation: anything the UI can do should be drivable from a script or a CI job.
Expect the CLI to leave preview with Flights and Dives management as its centre of gravity, and Guides to follow the same governance path Flights took — org-level controls, roles, and visibility rules layered on after the capability lands.
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 modeltime.ensemble or MotherDuck.
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 modeltime.ensemble alternatives → · See all MotherDuck alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. MotherDuck 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. MotherDuck 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 modeltime.ensemble alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.ensemble alternatives" section above for the current picks, or visit /alternatives/modeltime-ensemble for the full list with editorial commentary on each.
Top MotherDuck alternatives in Analytics are ranked by recent ship velocity. Browse the "MotherDuck alternatives" section above for the current picks, or visit /alternatives/motherduck for the full list with editorial commentary on each.