← Back to home
Comparison · Analytics

Countly vs loo

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

Countly vs loo: at a glance

FeatureCountlyloo
SectorAnalyticsAnalytics
Velocity score5.02.5
Sparks · 30d00
Top themesproduct-analytics, self-hosted, security-hardening, sandboxingbayesian, cross-validation, stan, 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 loo?

loo keeps rewriting the diagnostics Bayesian modellers read off model comparison

loo computes leave-one-out cross-validation and model comparison for Bayesian models in the Stan ecosystem. Two releases in this window changed what users actually read: 2.7.0 replaced the fixed Pareto-k thresholds with sample-size-dependent ones and dropped the middle category, and 2.10.0 reshaped loo_compare's output into a data.frame with new uncertainty columns. The releases between are diagnostic robustness fixes and moment-matching corrections.

Read the full loo trajectory →

Countly vs loo: 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.

L
loo
ANALYTICS
2.5

loo keeps rewriting the diagnostics Bayesian modellers read off model comparison

◆ Current state

loo computes leave-one-out cross-validation and model comparison for Bayesian models in the Stan ecosystem. Two releases in this window changed what users actually read: 2.7.0 replaced the fixed Pareto-k thresholds with sample-size-dependent ones and dropped the middle category, and 2.10.0 reshaped loo_compare's output into a data.frame with new uncertainty columns. The releases between are diagnostic robustness fixes and moment-matching corrections.

◆ Where it's heading

The package is being brought in line with the current PSIS literature rather than extended with new features, and the practical effect is that the numbers practitioners quote in papers keep changing meaning. Work is increasingly delegated to posterior for shared computations, and the project has added contributor process, benchmarks and a published AI contribution policy.

◆ Prediction

Expect further work on comparison diagnostics — the p_worse and diag_* columns are new enough that their defaults and documentation will likely be revised next.

Alternatives to Countly and loo

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 loo.

See all Countly alternatives → · See all loo alternatives →

Recent activity from Countly and loo

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 agoloopsis_smooth_tail revert and simplify arg restored
  5. 20d agoCountlyStar-rating logo path and data-manager transformation fixes
  6. 22d agoCountlyLTS backport: data-manager transformation fix
  7. 1mo agoCountlyJourneys survive user merges; SDK-provided asset paths
  8. 1mo agolooloo_compare returns a data.frame with new uncertainty columns
  9. 7mo agolooStacking overflow fixes and posterior-based ESS
  10. 2y agolooMore robust Pareto-k diagnostics and moment matching
  11. 2y agolooPareto-k thresholds now depend on sample size
  12. 3y agolooLOO predictive metrics and CRPS scoring functions

Frequently asked questions

What is the difference between Countly and loo?

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 loo?

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 loo?

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