billboarder
An htmlwidget whose release notes are mostly billboard.js version bumps, quiet since 2021.
Comparison · Analytics
Countly vs tune
A side-by-side editorial comparison of Countly and tune — release velocity, themes, recent moves, and the top alternatives to consider.
Countly vs tune: at a glance
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.
What is tune?
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
Countly vs tune: editorial side-by-side
Countly
5.0ANALYTICS
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.
tune
0.0ANALYTICS
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
◆ Current state
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
◆ Where it's heading
Two migrations run through this timeline. The tunable surface keeps widening - first censored regression as a mode, then postprocessors via tailor - so that a candidate is now a preprocessor, model and postprocessor triple rather than just a model. The parallel story has moved from foreach to future and now to mirai, each step deprecating the last. Neither is finished.
◆ Prediction
Expect the foreach path to be removed outright, and the postprocessing surface to grow as tailor gains more steps; the GauPro switch will likely need follow-up as its behavior differs from the old engine.
Alternatives to Countly and tune
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 tune.
bbotk
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
bayesplot
bayesplot keeps widening its posterior-check catalogue while absorbing each ggplot2 break.
animation
Contribution-driven maintenance on a package whose last structural change was magick support.
pins
pins keeps adding a storage backend per release while retiring its original API
tsibble
tsibble shipped one release in five and a half years - the data structure is finished
See all Countly alternatives → · See all tune alternatives →
Recent activity from Countly and tune
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoCountlyCustom-code sandbox swapped to isolated-vm; images rebuilt on Node 24
- 9d agoCountlyFixes for event keys containing special characters
- 9d agoCountlyJourney deeplinks take dynamic parameters; hooks validated on save
- 20d agoCountlyStar-rating logo path and data-manager transformation fixes
- 21d agoCountlyLTS backport: data-manager transformation fix
- 1mo agoCountlyJourneys survive user merges; SDK-provided asset paths
- 3mo agotuneQuantile regression tuning; Bayesian search moves to GauPro
- 9mo agotuneFixes int_pctl() with future parallelism on last_fit()
- 11mo agotunePostprocessors become tunable; mirai joins future as a backend ⚡
- 11mo agotuneDevelopment snapshot re-enabling skipped tests
- 1y agotuneWarns on foreach parallelism; space-filling grids by default
- 2y agotuneFixes parallel tuning errors under multisession plans
Frequently asked questions
What is the difference between Countly and tune?
They serve adjacent needs but don't currently overlap on shipped themes. Countly is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 tune?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Countly is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 tune?
Top tune alternatives in Analytics are ranked by recent ship velocity. Browse the "tune alternatives" section above for the current picks, or visit /alternatives/tune for the full list with editorial commentary on each.