OpenReplay
OpenReplay moves its Go backend to pgx v5 and patches vulnerable deps across 1.25–1.27.
A side-by-side editorial comparison of Countly and Dagster — release velocity, themes, recent moves, and the top alternatives to consider.
Countly 25.03.58 tightens API tokens, sessions and login lockouts in one security patch.
Countly 25.03.58 is a security-heavy patch for the 25.03 line. App-restricted tokens must now declare their permissions, password changes and member lockouts revoke tokens, single-use tokens and reset links work once even under concurrency, and login failures count per account regardless of username casing. It also tightens access to dashboards, dbviewer and exports, and fixes file migration, remote-config targeting and star-rating widgets.
Dagster extends Declarative Automation from assets to jobs, unifying the orchestration model.
Dagster is shipping steady incremental improvements across 1.13.x: asset health status for retrying partitions, SnowflakeDbtProjectComponent maturation, alert policy YAML enforcement in Dagster+, and an automation condition UI that shows why historical conditions fired. The most architecturally significant change in the window is Declarative Automation for jobs, now in preview — it applies the same condition-based trigger model that assets use to scheduled batch jobs.
Countly 25.03.58 is a security-heavy patch for the 25.03 line. App-restricted tokens must now declare their permissions, password changes and member lockouts revoke tokens, single-use tokens and reset links work once even under concurrency, and login failures count per account regardless of username casing. It also tightens access to dashboards, dbviewer and exports, and fixes file migration, remote-config targeting and star-rating widgets.
The 25.03 LTS line keeps absorbing security work at a fast clip: an upstream Node CVE, certificate distrust, and now a sweep of Countly's own token and permission model. Feature work stays in enterprise licensing and journeys, while LTS releases mostly harden what exists.
Expect a matching 24.05 backport of the token and permission fixes. Token owners may also need migration guidance, since existing app-restricted tokens without permissions are now limited to their owner's rights.
Dagster is shipping steady incremental improvements across 1.13.x: asset health status for retrying partitions, SnowflakeDbtProjectComponent maturation, alert policy YAML enforcement in Dagster+, and an automation condition UI that shows why historical conditions fired. The most architecturally significant change in the window is Declarative Automation for jobs, now in preview — it applies the same condition-based trigger model that assets use to scheduled batch jobs.
Declarative Automation expanding to jobs is the directional story. If it exits preview and gains adoption, it reduces the need for sensors and schedules as separate primitives — the same declarative condition layer covers everything. The Dagster+ MCP server gaining OAuth documentation signals growing interest in using Dagster as an orchestration target for AI agents, not just a data pipeline tool.
Declarative Automation for jobs will exit preview within 1-2 minor releases, and the next visible investment is likely deeper first-class support for AI workload orchestration alongside the existing data pipeline primitives.
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 Dagster.
OpenReplay moves its Go backend to pgx v5 and patches vulnerable deps across 1.25–1.27.
Basedash automations can now attach scheduled CSV exports to Slack and email.
OpenPanel tags three more note-free builds in one evening, reaching 3.16.4.
Fulcrum turns on Insights, its AI assistant for field data, for every customer.
Holistics lets admins put a key dashboard on everyone's Home page.
OpenHouse locks down its column-defaults capability flag as default values near completion.
See all Countly alternatives → · See all Dagster 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 Dagster 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 Dagster 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-server for the full list with editorial commentary on each.
Top Dagster alternatives in Analytics are ranked by recent ship velocity. Browse the "Dagster alternatives" section above for the current picks, or visit /alternatives/dagster for the full list with editorial commentary on each.