← Back to home
Comparison · Analytics

Countly vs dials

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

Countly vs dials: at a glance

FeatureCountlydials
SectorAnalyticsAnalytics
Velocity score5.00.0
Sparks · 30d00
Top themesproduct-analytics, self-hosted, security-hardening, sandboxingtidymodels, hyperparameters, deep-learning, grid-search
Last editorial update8h 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 dials?

dials is quietly registering the tuning parameters for tidymodels' deep-learning push

dials defines the parameter objects and grid constructors that tidymodels tunes over, which makes its release notes a reliable early read on what the rest of the stack is about to support. The last two releases are dominated by attention-model parameters — SAINT and tabular deep learning via brulee, TabPFN via parsnip's tab_pfn() — alongside catboost parameters for bonsai and calibration parameters for tailor.

Read the full dials trajectory →

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

D
dials
ANALYTICS
0.0

dials is quietly registering the tuning parameters for tidymodels' deep-learning push

◆ Current state

dials defines the parameter objects and grid constructors that tidymodels tunes over, which makes its release notes a reliable early read on what the rest of the stack is about to support. The last two releases are dominated by attention-model parameters — SAINT and tabular deep learning via brulee, TabPFN via parsnip's tab_pfn() — alongside catboost parameters for bonsai and calibration parameters for tailor.

◆ Where it's heading

The grid machinery itself is settled: grid_space_filling() consolidated the older designs, and the grid_*() functions now error rather than warn on the wrong size argument. What keeps moving is the parameter catalog, and it is moving toward neural and foundation-model territory that tidymodels historically left alone. Error-message quality is a steady secondary theme.

◆ Prediction

Expect further parameter objects to land ahead of the parsnip and brulee releases that use them — the attention and tabular-foundation-model work in flight is the clearest thing the entries point to.

Alternatives to Countly and dials

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

See all Countly alternatives → · See all dials alternatives →

Recent activity from Countly and dials

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. 9d agoCountlyFixes for event keys containing special characters
  3. 9d agoCountlyJourney deeplinks take dynamic parameters; hooks validated on save
  4. 20d agoCountlyStar-rating logo path and data-manager transformation fixes
  5. 21d agoCountlyLTS backport: data-manager transformation fix
  6. 1mo agoCountlyJourneys survive user merges; SDK-provided asset paths
  7. 1mo agodialsAttention and tabular deep-learning parameters for brulee models
  8. 4mo agodialsParameters for ordinal_reg() and the tab_pfn() foundation model
  9. 11mo agodialsprop_terms() for supervised feature selection recipes
  10. 1y agodialsCalibration method parameters for classification and regression
  11. 1y agodialsPostprocessing parameters added; grid size mismatches now error
  12. 2y agodialsgrid_space_filling() consolidates the space-filling designs

Frequently asked questions

What is the difference between Countly and dials?

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

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

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