← Back to home
Comparison · Analytics

Countly vs mlr3mbo

A side-by-side editorial comparison of Countly and mlr3mbo — release velocity, themes, recent moves, and the top alternatives to consider.

Countly vs mlr3mbo: at a glance

FeatureCountlymlr3mbo
SectorAnalyticsAnalytics
Velocity score5.02.5
Sparks · 30d00
Top themesproduct-analytics, self-hosted, security-hardening, sandboxingbayesian-optimization, mlr3, hyperparameter-tuning, r-stats
Last editorial update11h ago1h ago
WebsiteVisit →Visit →

What is Countly?

Countly's LTS line is spending its releases on hardening the surfaces customers extend.

The 25.03 LTS and 24.05 branches are moving together, and the recent content is dominated by security and scoping work rather than features. The latest LTS rebuilds the api and frontend Docker images as multi-stage builds on Debian 13 with Node 24 so compilers and build tooling no longer ship, overrides fourteen vulnerable transitive dependencies, and replaces the unmaintained v8-sandbox behind custom code with isolated-vm. Earlier releases scoped internal event hooks to their own apps, fixed the consents table returning fields beyond the consent columns, and stopped dashboard widgets being copied by users without access to the referenced apps.

Read the full Countly trajectory →

What is mlr3mbo?

mlr3mbo picked its defaults from a benchmark study, not from taste

mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.

Read the full mlr3mbo trajectory →

Countly vs mlr3mbo: editorial side-by-side

C
Countly
ANALYTICS
5.0

Countly's LTS line is spending its releases on hardening the surfaces customers extend.

◆ Current state

The 25.03 LTS and 24.05 branches are moving together, and the recent content is dominated by security and scoping work rather than features. The latest LTS rebuilds the api and frontend Docker images as multi-stage builds on Debian 13 with Node 24 so compilers and build tooling no longer ship, overrides fourteen vulnerable transitive dependencies, and replaces the unmaintained v8-sandbox behind custom code with isolated-vm. Earlier releases scoped internal event hooks to their own apps, fixed the consents table returning fields beyond the consent columns, and stopped dashboard widgets being copied by users without access to the referenced apps.

◆ Where it's heading

The pattern across these releases is closing the gaps where a customer-supplied artefact — custom hook code, a copied widget, a projection on a request — could reach further than intended. That work is now touching the runtime itself, and the isolated-vm swap is a breaking change: custom code relying on setTimeout, setInterval or async completion fails with a logged error instead of running. The journey engine is the only place shipping genuinely new capability, and it is enterprise-only.

◆ Prediction

Expect follow-up releases to soften the custom-code migration, since the isolated-vm switch silently breaks any hook that awaited a timer, and further ab-testing work now that pystan has been replaced with compiled Stan executables.

M
mlr3mbo
ANALYTICS
2.5

mlr3mbo picked its defaults from a benchmark study, not from taste

◆ Current state

mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.

◆ Where it's heading

The package has moved from a toolkit that expected users to assemble a Bayesian optimisation loop into one with a defensible default loop, and the recent fixes — warm-start sizing on multi-objective archives, silently discarded terminators, stale x_domain values — are the consequences of more people running the default path.

◆ Prediction

Expect continued hardening of the acquisition-optimiser classes rather than new acquisition functions.

Alternatives to Countly and mlr3mbo

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 Countly or mlr3mbo.

See all Countly alternatives → · See all mlr3mbo alternatives →

Recent activity from Countly and mlr3mbo

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoCountlyCustom-code sandbox swapped to isolated-vm; images rebuilt on Node 24
  2. 10d agoCountlyFixes for event keys containing special characters
  3. 10d agoCountlyJourney deeplinks take dynamic parameters; hooks validated on save
  4. 20d agoCountlyStar-rating logo path and data-manager transformation fixes
  5. 22d agoCountlyLTS backport: data-manager transformation fix
  6. 23d agomlr3mboAcquisition optimiser fixes for warm starts and archives
  7. 1mo agoCountlyJourneys survive user merges; SDK-provided asset paths
  8. 3mo agomlr3mboDictionary lookup and restart-limit fixes
  9. 4mo agomlr3mborush 1.0.0 compatibility and Surrogate$check()
  10. 5mo agomlr3mbomlr3mbo 1.0.0 ships benchmark-derived default settings
  11. 10mo agomlr3mbomlr3learners 0.13.0 compatibility
  12. 11mo agomlr3mboMaintainer change and mlr3pipelines 0.9.0 upkeep

Frequently asked questions

What is the difference between Countly and mlr3mbo?

They serve adjacent needs but don't currently overlap on shipped themes. Countly is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.

Is Countly better than mlr3mbo?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Countly is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.

What are the best alternatives to Countly?

Top Countly alternatives in Analytics are ranked by recent ship velocity. Browse the "Countly alternatives" section above for the current picks, or visit /alternatives/countly for the full list with editorial commentary on each.

What are the best alternatives to mlr3mbo?

Top mlr3mbo alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3mbo alternatives" section above for the current picks, or visit /alternatives/mlr3mbo for the full list with editorial commentary on each.