rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
rstanarm vs vetiver
A side-by-side editorial comparison of rstanarm and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
rstanarm vs vetiver: at a glance
What is rstanarm?
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
2.32.2 is entirely infrastructure and dependency work: formula machinery migrated from lme4 to reformulas, `r_eff` no longer computed for loo by default, the Stan R packages repo replaced by R-Universe, rstantools adopted to fix build and export errors, and CRAN NOTE cleanups — contributed largely by four first-time contributors. 2.32.1 and 2.26.1 follow the same pattern, tracking rstan syntax and adding `posterior::as_draws()` support. The last release with substantive modelling content is 2.21.1, which changed how default priors are determined and flipped `autoscale` to FALSE outside default priors.
What is vetiver?
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
rstanarm vs vetiver: editorial side-by-side
rstanarm
0.0ANALYTICS
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
◆ Current state
2.32.2 is entirely infrastructure and dependency work: formula machinery migrated from lme4 to reformulas, `r_eff` no longer computed for loo by default, the Stan R packages repo replaced by R-Universe, rstantools adopted to fix build and export errors, and CRAN NOTE cleanups — contributed largely by four first-time contributors. 2.32.1 and 2.26.1 follow the same pattern, tracking rstan syntax and adding `posterior::as_draws()` support. The last release with substantive modelling content is 2.21.1, which changed how default priors are determined and flipped `autoscale` to FALSE outside default priors.
◆ Where it's heading
The package has moved from feature development into ecosystem maintenance, and the contributor list shows why it survives: outside developers keep it compiling against a moving Stan, lme4 and CRAN. The `as_draws()` support and the reformulas migration both point the same way — rstanarm increasingly consumes shared infrastructure (posterior, reformulas, rstantools) instead of carrying its own.
◆ Prediction
Expect the next release to track another upstream change — rstan, reformulas or CRAN policy — rather than add model families. The pre-fit model surface looks settled.
vetiver
0.0ANALYTICS
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
◆ Current state
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
◆ Where it's heading
The feature era ended before this window opened. Deploying to SageMaker, generating Docker files, storing renv lockfiles in model metadata and supporting keras, luz and recipes all landed in 0.2.1 and 0.2.2; nothing since has extended what vetiver does. What it does now is track the rest of tidymodels — when recipes gains a prototype API or probably becomes something a workflow can contain, vetiver adds a line. That is a package holding its position rather than advancing it.
◆ Prediction
The entries do not support a confident prediction of new capability. On this pattern the next release tracks another tidymodels change, most likely the postprocessing stage that workflows added in 1.3.0.
Alternatives to rstanarm and vetiver
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 rstanarm or vetiver.
writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif
rgbif is steadily pushing users off paged searching and onto real downloads.
taxa
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all rstanarm alternatives → · See all vetiver alternatives →
Recent activity from rstanarm and vetiver
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agovetiverSupport all versions of xgboost
- 9mo agovetiverFirst release in two years catches up with recipes and probably
- 10mo agorstanarmrstanarm 2.32.2 migrates formula machinery to reformulas
- 2y agorstanarmrstanarm 2.32.1 fixes unit_vector error, enables LTO
- 2y agovetiverFix plumber file generation bug
- 2y agorstanarmrstanarm 2.26.1 adopts new rstan syntax and as_draws()
- 2y agovetiverFix plumber generation for board_url() pins
- 3y agovetivervetiver 0.2.3
- 3y agovetiverModels expose their input prototype over HTTP
- 4y agorstanarmrstanarm 2.21.3 fixes loo() and adds stan_jm offsets
- 6y agorstanarmrstanarm 2.21.1 changes default prior behaviour
Frequently asked questions
What is the difference between rstanarm and vetiver?
They serve adjacent needs but don't currently overlap on shipped themes. rstanarm and vetiver are shipping at a similar cadence (velocity 0.0 vs 0.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.
Is rstanarm better than vetiver?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rstanarm and vetiver are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to rstanarm?
Top rstanarm alternatives in Analytics are ranked by recent ship velocity. Browse the "rstanarm alternatives" section above for the current picks, or visit /alternatives/rstanarm for the full list with editorial commentary on each.
What are the best alternatives to vetiver?
Top vetiver alternatives in Analytics are ranked by recent ship velocity. Browse the "vetiver alternatives" section above for the current picks, or visit /alternatives/vetiver-r for the full list with editorial commentary on each.