Basedash
Basedash introduces semantic SQL Models and AI Sources — turning its analytics workspace into a governed data layer.
A side-by-side editorial comparison of Countly and Holistics — release velocity, themes, recent moves, and the top alternatives to consider.
Countly ripped out its custom-code sandbox and rebuilt its Docker stack from scratch in a single LTS drop.
Countly is in an extended security hardening cycle, maintaining two parallel LTS lines — 25.03.x and 24.05.x — with coordinated patch releases. The 25.03.52-LTS was structurally significant: Docker images rebuilt as multi-stage on Debian 13 and Node.js 24 to strip compilers and build tooling from production images, the legacy v8-sandbox replaced by isolated-vm eliminating network, filesystem, and process access from custom hooks, and the A/B testing backend migrated from end-of-life Python 3.8 and pystan to Python 3.12 and cmdstanpy. The 25.03.53 and 24.05.53 patches that followed addressed XSS, OIDC session handling, and embedded widget cross-origin policies.
After a summer fencing in its AI layer, Holistics points it at the question analysts get asked most.
Holistics ships short, frequent notes, and the August 31 pair is the first in months that adds capability rather than control. Analyze Changes lets any user right-click a data point and get a two-step investigation: whether the movement is statistically unusual at all, then which dimensions and segments drove it and by how much. Anomaly Detection scans a time-series metric against an expected range built from its own history and flags the outliers, with the resulting chart saveable to a dashboard. Both are named as parts of a new Smart Analysis surface. The weeks before were governance — redaction of data the AI may see, and an AI user attribute restricting what it can reach.
Countly is in an extended security hardening cycle, maintaining two parallel LTS lines — 25.03.x and 24.05.x — with coordinated patch releases. The 25.03.52-LTS was structurally significant: Docker images rebuilt as multi-stage on Debian 13 and Node.js 24 to strip compilers and build tooling from production images, the legacy v8-sandbox replaced by isolated-vm eliminating network, filesystem, and process access from custom hooks, and the A/B testing backend migrated from end-of-life Python 3.8 and pystan to Python 3.12 and cmdstanpy. The 25.03.53 and 24.05.53 patches that followed addressed XSS, OIDC session handling, and embedded widget cross-origin policies.
Countly is hardening its self-hosted security posture — the isolated-vm switch and Docker rebuild reduce attack surface without changing the product surface for end users. Running two LTS tracks simultaneously signals a maturing enterprise customer base that cannot upgrade on a quarterly cadence. Feature development in journey_engine and content continues on a separate lane from the security work, suggesting the two concerns are intentionally decoupled.
The Node.js 22/24 migration will propagate to additional components. The isolated-vm change will likely prompt tighter documentation of what custom code can and cannot access. Dual LTS maintenance continues as long as significant deployments remain on 24.05.x.
Holistics ships short, frequent notes, and the August 31 pair is the first in months that adds capability rather than control. Analyze Changes lets any user right-click a data point and get a two-step investigation: whether the movement is statistically unusual at all, then which dimensions and segments drove it and by how much. Anomaly Detection scans a time-series metric against an expected range built from its own history and flags the outliers, with the resulting chart saveable to a dashboard. Both are named as parts of a new Smart Analysis surface. The weeks before were governance — redaction of data the AI may see, and an AI user attribute restricting what it can reach.
The AI work has run in a recognizable order: capability, then observability, then access control, then redaction — and now capability again, but aimed somewhere new. Everything Holistics shipped before answered questions about building or querying; Smart Analysis answers why a number moved, which is the request that has always been routed to an analyst. Governance arriving first is what makes it viable: redaction and the AI user attribute decide what the investigator may look at before it is allowed to investigate on its own. Alongside it, presentation keeps moving into AML, so what analysts used to click is versioned as code.
The published roadmap already lists AI Dashboard Summaries and organization-level AI memory, so the next step is likely narrative output over the same investigation — an explanation attached to the dashboard rather than produced on right-click. Whether Smart Analysis stays a manual gesture or starts running unprompted against monitored metrics is the open question.
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 Holistics.
Basedash introduces semantic SQL Models and AI Sources — turning its analytics workspace into a governed data layer.
GoAccess 1.11 cuts storage memory 20% and parsing time 35% — meaningful gains for large log volumes.
updown.io adds closed port monitoring and a detailed check metrics page with multi-year uptime heatmaps.
Fulcrum ships steady mobile and web maintenance with Photo FastFill as the one standout enhancement.
Neo4j's Virtual Graph lets you run Cypher against Snowflake and BigQuery without moving any data.
OpenObserve approaches 1.0.0 GA after a 836-commit v0.92.0 that added three new product surfaces.
See all Countly alternatives → · See all Holistics alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Countly and Holistics are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Countly and Holistics are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
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.
Top Holistics alternatives in Analytics are ranked by recent ship velocity. Browse the "Holistics alternatives" section above for the current picks, or visit /alternatives/holistics for the full list with editorial commentary on each.