pins
pins keeps adding a storage backend per release while retiring its original API
Comparison · Analytics
Countly vs dtplyr
A side-by-side editorial comparison of Countly and dtplyr — release velocity, themes, recent moves, and the top alternatives to consider.
Countly vs dtplyr: 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 dtplyr?
dtplyr stopped hijacking data.table objects and became an opt-in translator
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
Countly vs dtplyr: 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.
dtplyr
0.0ANALYTICS
dtplyr stopped hijacking data.table objects and became an opt-in translator
◆ Current state
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
◆ Where it's heading
The package is trailing dplyr's own feature releases rather than leading them, adding each new verb once it settles upstream. Performance work is targeted at specific verbs where data.table has a faster primitive: setorder() for arrange(), reference drops for select(), rleid() for consecutive_id(). Release cadence has thinned considerably since 2023.
◆ Prediction
Expect further one-for-one translations as dplyr adds verbs, and continued fixes around .by and non-standard column names; the entries show no sign of a broader redesign.
Alternatives to Countly and dtplyr
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 dtplyr.
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 dtplyr alternatives →
Recent activity from Countly and dtplyr
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
- 11mo agodtplyrreframe(), case_match() and consecutive_id() gain translations
- 3y agodtplyrcrayon dependency dropped
- 3y agodtplyrVerbs stop auto-dispatching; lazy_dt() now required ⚡
- 3y agodtplyrdtplyr 1.2.2
- 4y agodtplyrdtplyr 1.2.1
- 4y agodtplyrEight tidyr verbs gain data.table translations
Frequently asked questions
What is the difference between Countly and dtplyr?
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 dtplyr?
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 dtplyr?
Top dtplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "dtplyr alternatives" section above for the current picks, or visit /alternatives/dtplyr for the full list with editorial commentary on each.