Casdoor
One commit, one release: nine tags in a week, tightening org-level control and credential handling.
A side-by-side editorial comparison of Dokku and Robusta — release velocity, themes, recent moves, and the top alternatives to consider.
Dokku is quietly turning into a k3s front-end with a JSON-first CLI.
Dokku is twenty-six patches deep into the 0.38 line, shipping small releases every one to two weeks whose bodies are largely dependabot bumps. The substantive work sits in two places: the k3s scheduler, which just picked up wildcard domain routing through Traefik, manually managed cert issuers, and kernel sysctl control, and the CLI surface, where `:report` and `:list` subcommands are gaining `--format json` while being ported from bash to Go. A command-injection fix in the docker-options eval path landed in v0.38.25.
Robusta's alpha train keeps widening what can push alerts in and where it can run.
Robusta ships alpha releases every one to three weeks, each a small bundle of merged PRs rather than a headline feature. The recent four cover alert ingestion breadth (Jira Service Management, F5 Distributed Cloud documented against the Send Events API), operational plumbing (JSON log format behind an environment variable, a global imagePullSecret for the Helm chart, namespace-scoped RBAC guidance), and routine dependency and CVE bumps. The 0.47.0 release adds a workflow trigger action, letting one Robusta workflow fire another on the platform.
Dokku is twenty-six patches deep into the 0.38 line, shipping small releases every one to two weeks whose bodies are largely dependabot bumps. The substantive work sits in two places: the k3s scheduler, which just picked up wildcard domain routing through Traefik, manually managed cert issuers, and kernel sysctl control, and the CLI surface, where `:report` and `:list` subcommands are gaining `--format json` while being ported from bash to Go. A command-injection fix in the docker-options eval path landed in v0.38.25.
The single-host Docker PaaS Dokku started as is increasingly a front-end for a Kubernetes backend. Across these ten releases nearly every new feature touches either scheduler-k3s or machine-readable output, and almost none touch the original Docker-only path. The bash-to-Go port running underneath reads as groundwork for the structured-output work rather than a refactor for its own sake.
Expect `--format json` to keep spreading across the remaining bash subcommands, and k3s to keep absorbing the certificate and networking controls the nginx and Traefik paths already have.
Robusta ships alpha releases every one to three weeks, each a small bundle of merged PRs rather than a headline feature. The recent four cover alert ingestion breadth (Jira Service Management, F5 Distributed Cloud documented against the Send Events API), operational plumbing (JSON log format behind an environment variable, a global imagePullSecret for the Helm chart, namespace-scoped RBAC guidance), and routine dependency and CVE bumps. The 0.47.0 release adds a workflow trigger action, letting one Robusta workflow fire another on the platform.
The pattern is integration breadth plus operability, not new product surface: more systems that can push events in, more ways to run the agent inside a locked-down cluster. Structured JSON logging and the namespace-scoped RBAC guide both read as groundwork for regulated and multi-tenant deployments where a cluster-wide agent is a non-starter. Workflow chaining is the one thread here that could grow past plumbing, since triggering workflows from workflows is where automation stops being one-shot alert handling.
The next alpha will most likely continue the same mix — another event source or two alongside dependency and CVE bumps. Whether workflow chaining becomes a real automation layer cannot be judged from these four releases.
Other Infra & APIs 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 Dokku or Robusta.
One commit, one release: nine tags in a week, tightening org-level control and credential handling.
Cronicle has spent 2026 hardening the paths that let a scheduler run arbitrary commands
A virtualization manager coasting on backports, with releases years apart
The workflow engine keeps shipping weekly, and more of each release is Seqera plumbing
Kata rewrote its runtime in Rust and made it the default in 4.0.0
An RPKI validator that now treats its own attack surface as the product
See all Dokku alternatives → · See all Robusta alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — kubernetes — within Infra & APIs. Dokku and Robusta 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. Dokku and Robusta 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 Infra & APIs products to evaluate alongside.
Top Dokku alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokku alternatives" section above for the current picks, or visit /alternatives/dokku for the full list with editorial commentary on each.
Top Robusta alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Robusta alternatives" section above for the current picks, or visit /alternatives/robusta for the full list with editorial commentary on each.