RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of modeltime.ensemble and Tinybird — 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.
Every weekly release now pushes Forward further ahead of Classic before the September sunset.
Tinybird ships a descriptive weekly changelog, and the current window is dominated by ingestion. Remote files can now be imported through the v1 API to append or replace Data Source rows, v1 ingestion became the default for local files a week after arriving as experimental, and JSON integer handling was corrected. Reliability work runs alongside it: quarantined data persists across compatible deployments, and deployment backfills and validation got fixes.
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.
Tinybird ships a descriptive weekly changelog, and the current window is dominated by ingestion. Remote files can now be imported through the v1 API to append or replace Data Source rows, v1 ingestion became the default for local files a week after arriving as experimental, and JSON integer handling was corrected. Reliability work runs alongside it: quarantined data persists across compatible deployments, and deployment backfills and validation got fixes.
The Classic-to-Forward migration is the organizing fact, and the September 15 sunset for Free and Developer plans set the clock. Nearly every capability in this window lands on Forward or on the v1 surface, while Classic receives limits adjustments rather than features. Ingestion is where the investment is concentrated, moving from experimental to default in weeks.
Expect the v1 ingestion surface to keep absorbing sources — remote URLs now, likely more managed connectors next — and the remaining gaps in deployment and backfill reliability to close ahead of the sunset. The paid tiers still have no announced Classic end date.
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 Tinybird.
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 Tinybird alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Tinybird 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. Tinybird 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 Tinybird alternatives in Analytics are ranked by recent ship velocity. Browse the "Tinybird alternatives" section above for the current picks, or visit /alternatives/tinybird for the full list with editorial commentary on each.