← Back to analytics tools
Alternatives · analytics tools

mlr3tuning alternatives

The best mlr3tuning alternatives in analytics tools, ranked by Sparkpulse's velocity_score.

Updated Aug 13, 2026

Looking for the best alternatives to mlr3tuning? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, mlr3tuning shipped 0 meaningful updates in the last 30 days and carries a velocity score of 2.5 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.

About mlr3tuning

mlr3tuning is rebuilding its async machinery under a stable public surface

mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.

Velocity 2.5 · Last update 1h ago

Read the full mlr3tuning trajectory →

Top 12 alternatives to mlr3tuning

Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.

Browse all analytics tools products →

mlr3tuning vs alternatives — shipping velocity at a glance

Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.

ProductVelocitySparks · 30dFocus areasLatest release
mlr3tuning (baseline)2.50mlr3hyperparameter-tuningasync-optimization
writexl6.31xlsxlibxlsxwritercell-formattingwritexl 2.0.0 adds formatting, comments and full libxlsxwriter coverage
mlr3viz2.50mlr3visualizationggplot2
mlr3mbo2.50bayesian-optimizationmlr3hyperparameter-tuningmlr3mbo 1.0.0 ships benchmark-derived default settings
rnaturalearth0.00spatial-datanatural-earthsf-migration
rgbif0.00gbifbiodiversity-databulk-downloadsrgbif 3.8.1 adds SQL-based occurrence downloads
rstanarm0.00bayesianstanregression-models
taxa0.00taxonomyvctrsstalled-rewritetaxa 0.4.0 begins a base-R-vector rewrite without taxmap
rotl0.00open-tree-of-lifetaxonomic-matchingreproducibility
taxize0.00taxonomyapi-aggregationupstream-churn
osmdata0.00openstreetmapoverpass-apispatial-data
posterior0.00bayesianrvarpareto-diagnostics
rredlist0.00iucn-red-listapi-migrationbreaking-changerredlist 1.0.0 rebuilds on IUCN Red List API v4

The 12 best mlr3tuning alternatives, in depth

1. writexl · velocity 6.3

Writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.

Over the last 30 days writexl shipped 1 meaningful update vs mlr3tuning's 0, most recently “writexl 2.0.0 adds formatting, comments and full libxlsxwriter coverage”. Its velocity score of 6.3/10 blends that with longer-term release cadence.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, writexl focuses on xlsx, libxlsxwriter and cell formatting.

Over the last 30 days writexl has been shipping faster than mlr3tuning — a point in its favour if release momentum matters to you.

2. mlr3viz · velocity 2.5

Mlr3viz keeps the ecosystem's plots working while the plots themselves move out.

Its velocity score of 2.5/10 reflects longer-term release cadence.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, mlr3viz focuses on mlr3, visualization and ggplot2.

mlr3viz and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

3. mlr3mbo · velocity 2.5

Mlr3mbo picked its defaults from a benchmark study, not from taste.

Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “mlr3mbo 1.0.0 ships benchmark-derived default settings”.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, mlr3mbo focuses on bayesian optimization, mlr3 and hyperparameter tuning.

mlr3mbo and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

4. rnaturalearth · velocity 0.0

Rnaturalearth finished its sp exit and is now optimising how the data actually arrives.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, rnaturalearth focuses on spatial data, natural earth and sf migration.

rnaturalearth and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

5. rgbif · velocity 0.0

Rgbif is steadily pushing users off paged searching and onto real downloads.

Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “rgbif 3.8.1 adds SQL-based occurrence downloads”.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, rgbif focuses on gbif, biodiversity data and bulk downloads.

rgbif and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

6. rstanarm · velocity 0.0

Rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, rstanarm focuses on bayesian, stan and regression models.

rstanarm and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

7. taxa · velocity 0.0

Taxa started a ground-up rewrite in 2021 and has published almost nothing since.

Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “taxa 0.4.0 begins a base-R-vector rewrite without taxmap”.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, taxa focuses on taxonomy, vctrs and stalled rewrite.

taxa and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

8. rotl · velocity 0.0

Rotl's whole release history is keeping name matching honest against a moving taxonomy.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, rotl focuses on open tree of life, taxonomic matching and reproducibility.

rotl and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

9. taxize · velocity 0.0

Taxize spends its releases absorbing other people's API changes, one dead source at a time.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, taxize focuses on taxonomy, api aggregation and upstream churn.

taxize and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

10. osmdata · velocity 0.0

Osmdata keeps tightening its Overpass query surface, breaking small things to get types right.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, osmdata focuses on openstreetmap, overpass api and spatial data.

osmdata and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

11. posterior · velocity 0.0

Posterior keeps deepening two things: the rvar type and Pareto-based diagnostics.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, posterior focuses on bayesian, rvar and pareto diagnostics.

posterior and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

12. rredlist · velocity 0.0

Rredlist threw out its species-centric API in 1.0.0 and rebuilt around assessments.

Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “rredlist 1.0.0 rebuilds on IUCN Red List API v4”.

Where mlr3tuning leans on mlr3, hyperparameter tuning and async optimization, rredlist focuses on iucn red list, api migration and breaking change.

rredlist and mlr3tuning have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

Frequently asked questions

What are the best alternatives to mlr3tuning?

The top mlr3tuning alternatives we currently track in analytics tools are writexl, mlr3viz, mlr3mbo, rnaturalearth, rgbif, ranked by recent ship velocity.

How is this list of mlr3tuning alternatives ranked?

Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.

Can I compare mlr3tuning directly with one of these alternatives?

Yes — every card has a "Compare with mlr3tuning" link to a side-by-side /compare page.