discrim
discrim settled into a thin engine shim after handing its model definitions to parsnip.
Comparison · Analytics
bonsai vs Countly
A side-by-side editorial comparison of bonsai and Countly — release velocity, themes, recent moves, and the top alternatives to consider.
bonsai vs Countly: at a glance
What is bonsai?
bonsai keeps widening tidymodels' boosted-tree engine bench, catboost most recently
bonsai exists to attach non-core tree engines to parsnip's boost_tree() and rand_forest(), and the release history reads as a steady accumulation of them: partykit, aorsf, lightgbm, and now catboost. The 0.4.x line is spent making catboost behave like a full tidymodels citizen rather than adding anything new.
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.
bonsai vs Countly: editorial side-by-side
bonsai
0.0ANALYTICS
bonsai keeps widening tidymodels' boosted-tree engine bench, catboost most recently
◆ Current state
bonsai exists to attach non-core tree engines to parsnip's boost_tree() and rand_forest(), and the release history reads as a steady accumulation of them: partykit, aorsf, lightgbm, and now catboost. The 0.4.x line is spent making catboost behave like a full tidymodels citizen rather than adding anything new.
◆ Where it's heading
Each engine follows the same arc — land it, then close the gaps that keep it from tuning cleanly (parameter naming, multi_predict, threading, case weights). Recent work is squarely in that second phase for catboost, with dials supplying the matching parameter objects on its own release schedule. Bug-fix density is high relative to new surface.
◆ Prediction
Expect the catboost integration to keep filling in tuning and GPU-related arguments before any further engine is added; the entries give no signal about which engine would come next.
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.
Alternatives to bonsai and Countly
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 bonsai or Countly.
dbparser
dbparser shed its database and CSV writers to become just a DrugBank parser.
desirability2
desirability2 is making multi-metric model selection a first-class tidymodels step.
crosstalk
crosstalk is frozen infrastructure: four releases in five years, mostly CRAN upkeep.
cmdstanr
cmdstanr keeps adding fast approximations beside full HMC, and fighting Windows toolchains.
comtradr
comtradr's 1.0 line is a long tail of patches against a brittle UN trade API.
See all bonsai alternatives → · See all Countly alternatives →
Recent activity from bonsai and Countly
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoCountlyCustom-code sandbox swapped to isolated-vm; images rebuilt on Node 24
- 10d agoCountlyFixes for event keys containing special characters
- 10d 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
- 2mo agobonsaicatboost gains multi_predict() and corrected tuning parameters
- 1y agobonsaicatboost engine added to boost_tree()
- 1y agobonsailightgbm accepts sparse matrices for fit and predict
- 2y agobonsaiaorsf fit failure in multisession workers fixed
- 2y agobonsaiaorsf engine added; lightgbm gains dataset params and case weights
- 3y agobonsailightgbm num_leaves becomes tunable; alias arguments disallowed
Frequently asked questions
What is the difference between bonsai and Countly?
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 bonsai better than Countly?
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 bonsai?
Top bonsai alternatives in Analytics are ranked by recent ship velocity. Browse the "bonsai alternatives" section above for the current picks, or visit /alternatives/bonsai-r for the full list with editorial commentary on each.
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.