Rancher
The public feed carries tags and image manifests; the release notes live in Prime docs.
A side-by-side editorial comparison of Dokku and CRI-O — release velocity, themes, recent moves, and the top alternatives to consider.
Dokku ships patches weekly, and quietly grows a Kubernetes backend under its single-host roots.
Dokku releases on a near-weekly patch cadence, and most entries are dominated by Dependabot bumps to test fixtures. The real content is thin but consistent: a command injection fix in docker options evaluation, per-app Let's Encrypt emails on k3s, atomic buildpack list replacement, custom chown values, and JSON output added to apps:list, ps:scale and docker-options reports. Several tags in early July were published within minutes of each other and out of version order.
Patch tags land monthly with release notes that itemize nothing.
The three most recent CRI-O entries are v1.34.11, v1.34.10 and v1.33.13, cut roughly a month apart across two supported minor lines. All three carry auto-generated notes whose 'Changes by Kind' sections are empty or labelled Uncategorized, with the body given over to download bundles, checksums, SPDX manifests and signatures. Only v1.34.10 admits to a Bug or Regression category, and does not say what it was.
Dokku releases on a near-weekly patch cadence, and most entries are dominated by Dependabot bumps to test fixtures. The real content is thin but consistent: a command injection fix in docker options evaluation, per-app Let's Encrypt emails on k3s, atomic buildpack list replacement, custom chown values, and JSON output added to apps:list, ps:scale and docker-options reports. Several tags in early July were published within minutes of each other and out of version order.
Two threads carry through. The scheduler-k3s plugin keeps accumulating what a real platform needs — helm chart previews, autoscaling auth state, control-plane node matching, per-app certificate configuration — which pushes Dokku beyond the single-host Docker tool it started as. The second is machine readability: command after command gains --format json, turning the CLI into something automation can consume rather than parse.
Expect JSON output to keep spreading command by command until it is the norm rather than a flag, and expect the k3s scheduler to stay the destination for new capability while the Docker scheduler receives fixes. The patch train shows no sign of consolidating into a minor release.
The three most recent CRI-O entries are v1.34.11, v1.34.10 and v1.33.13, cut roughly a month apart across two supported minor lines. All three carry auto-generated notes whose 'Changes by Kind' sections are empty or labelled Uncategorized, with the body given over to download bundles, checksums, SPDX manifests and signatures. Only v1.34.10 admits to a Bug or Regression category, and does not say what it was.
What the feed does show is release engineering: every tag ships static bundles per architecture with checksums, SPDX SBOMs and signing bundles, which is the supply-chain posture Kubernetes runtimes are now expected to hold. The absence of itemized changes means the actual runtime work is invisible here, so read this feed as a release calendar for the 1.33 and 1.34 branches rather than a changelog.
Expect the same monthly patch cadence on both maintained branches, with content that stays uncategorized unless the project changes how it generates notes.
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 CRI-O.
The public feed carries tags and image manifests; the release notes live in Prime docs.
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
Volatility 3 caught up with Volatility 2, then started reorganising itself.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — kubernetes — within Infra & APIs. Dokku is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dokku is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. 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 CRI-O alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CRI-O alternatives" section above for the current picks, or visit /alternatives/cri-o for the full list with editorial commentary on each.