Cortex
Cortex 1.22 is on its fourth candidate, with sharded Parquet and years of deprecated flags removed.
A side-by-side editorial comparison of Countly and Superwise — release velocity, themes, recent moves, and the top alternatives to consider.
Countly's two LTS lines now get the same security fixes within a week of each other.
Countly ships security patches on two LTS lines, 25.03 and 24.05. In late October 25.03.56 moved the Docker images to Node.js 24.22.1 for a Brotli CVE and brought Python 3.12.15 to the A/B testing stack; 25.03.58 tightened tokens: app-restricted tokens must state their permissions, password changes revoke a member's tokens, and single-use tokens hold under concurrent requests. 24.05.55 then brought those same fixes to the older line, including the isolated-vm sandbox for custom hook code that 25.03 adopted in August.
Superwise now measures the tokens it saves and can shorten model replies to save more
Sentinel has become the product: since September it is the default on login, with a new home screen and a switcher to the rest of the platform, plus Solo, Pro and Business plans built around Sentinel usage. Token optimization arrived with Headroom prompt compression, then Caveman, an optional setting that shortens model responses while keeping code, numbers and identifiers, with savings reported on the FinOps and Operational dashboards. Guardrails grew into language, image resolution and image sharpness checks, with a test sandbox, and 1.41 can generate test cases from a guardrail's configuration.
Countly ships security patches on two LTS lines, 25.03 and 24.05. In late October 25.03.56 moved the Docker images to Node.js 24.22.1 for a Brotli CVE and brought Python 3.12.15 to the A/B testing stack; 25.03.58 tightened tokens: app-restricted tokens must state their permissions, password changes revoke a member's tokens, and single-use tokens hold under concurrent requests. 24.05.55 then brought those same fixes to the older line, including the isolated-vm sandbox for custom hook code that 25.03 adopted in August.
The work is about access control and supply chain, not new analytics features. Tokens, sessions and login counting are being tightened release by release, and the 24.05 line is being pulled up to the 25.03 runtime (Node.js 22 for custom code, Python 3.12 with CmdStanPy for A/B testing) instead of being left on older stacks. Feature work shows up only in small items such as explicitly named databases and a licence payment-overdue banner.
Expect more paired patches as token and session hardening continues on both lines. The entries don't say how long 24.05 will keep receiving backports.
Sentinel has become the product: since September it is the default on login, with a new home screen and a switcher to the rest of the platform, plus Solo, Pro and Business plans built around Sentinel usage. Token optimization arrived with Headroom prompt compression, then Caveman, an optional setting that shortens model responses while keeping code, numbers and identifiers, with savings reported on the FinOps and Operational dashboards. Guardrails grew into language, image resolution and image sharpness checks, with a test sandbox, and 1.41 can generate test cases from a guardrail's configuration.
The gateway is moving from reporting cost to reducing it. August's FinOps dashboard said where tokens went, and the autumn releases act on that and then report the saving, which turns the metric into a sales argument. Guardrails are following the same self-service path: editable per Sentinel, testable before publishing, and now seeded with generated cases. The Sentinel CLI's growing status, logs and Claude Desktop support make it a tool admins run locally.
Budget thresholds or routing rules that act on these metrics have not appeared yet, and remain the likely next step now that savings are measured. More image guardrails are also plausible, since sharpness was added one release after resolution.
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 Superwise.
Cortex 1.22 is on its fourth candidate, with sharded Parquet and years of deprecated flags removed.
OpenMetadata reaches 2.1 rc1 after a month of repairing 2.0's connectors.
Stitch keeps patching connectors one replication bug at a time.
Datawrapper's October is touch tooltips, keyboard focus and small chart repairs.
Fluent Bit spends October bounding what its inputs will accept.
Axiom makes agent work checkable, and points alerts straight at coding agents
See all Countly alternatives → · See all Superwise 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 Superwise are shipping at a similar cadence (velocity 5.0 vs 5.0, 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 Superwise are shipping at a similar cadence (velocity 5.0 vs 5.0, 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 Superwise alternatives in Analytics are ranked by recent ship velocity. Browse the "Superwise alternatives" section above for the current picks, or visit /alternatives/superwise for the full list with editorial commentary on each.