pins
pins keeps adding a storage backend per release while retiring its original API
Comparison · Analytics
Countly vs insight
A side-by-side editorial comparison of Countly and insight — release velocity, themes, recent moves, and the top alternatives to consider.
Countly vs insight: 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 insight?
insight quietly widens the set of model objects the easystats ecosystem can read
insight is the extraction layer under the easystats packages — it answers what a fitted model's parameters, data, variance and priors are, for whatever object it is handed. The 1.4.x and 1.5.x releases read as a steady widening of that support list: tidymodels workflows, cmdstanr fits, rstpm2 survival models, lavaan variance-covariance, mice imputations.
Countly vs insight: 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.
insight
0.0ANALYTICS
insight quietly widens the set of model objects the easystats ecosystem can read
◆ Current state
insight is the extraction layer under the easystats packages — it answers what a fitted model's parameters, data, variance and priors are, for whatever object it is handed. The 1.4.x and 1.5.x releases read as a steady widening of that support list: tidymodels workflows, cmdstanr fits, rstpm2 survival models, lavaan variance-covariance, mice imputations.
◆ Where it's heading
Two things move together here. The support list grows toward objects produced outside the easystats world, and performance work targets the helpers that everything else calls — compact_list(), is_empty_object(), find_parameters() on mgcv models. New functions appear occasionally (get_simulated(), vcovFPC()) but the center of gravity is coverage, not capability.
◆ Prediction
Expect further model classes to be added as downstream easystats packages need them, and continued alignment with R-devel behavior changes like the weighted-residuals revision.
Alternatives to Countly and insight
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 insight.
tsibble
tsibble shipped one release in five and a half years - the data structure is finished
yardstick
yardstick made fairness metrics a first-class part of tidymodels evaluation
tune
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
leaflet
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
See all Countly alternatives → · See all insight alternatives →
Recent activity from Countly and insight
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
- 1mo agoinsightcompact_list() performance and lavaan variance-covariance support
- 2mo agoinsightcmdstanr support and finite-population-corrected variance
- 4mo agoinsightget_simulated() added; rstpm2 survival models supported
- 6mo agoinsightWeighted residuals revised to match R 4.6.0
- 6mo agoinsighttidymodels workflow objects become readable
- 8mo agoinsightlme4 convergence and fixest data extraction fixes
Frequently asked questions
What is the difference between Countly and insight?
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 insight?
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 insight?
Top insight alternatives in Analytics are ranked by recent ship velocity. Browse the "insight alternatives" section above for the current picks, or visit /alternatives/insight for the full list with editorial commentary on each.