Rancher
The public feed carries tags and image manifests; the release notes live in Prime docs.
A side-by-side editorial comparison of Terragrunt and OctoPrint — release velocity, themes, recent moves, and the top alternatives to consider.
Terragrunt graduated six experiments at once and has spent three candidates stabilising them
Terragrunt is running the v1.1.0 release-candidate cycle, now at rc3. The first candidate completed six experiments simultaneously — stack-dependencies, a content-addressable store, a catalog redesign, mark-many-as-read, opt-out-auth and DAG queue display. The two candidates since have added only bug fixes for those features plus improvements to how releases are published and verified.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
The entire feed is the 2.0.0 release candidate series — four RCs between April and July 2026, no stable tag. The testing asks reveal what changed underneath: blocklisted serial ports and baud rates are migrated into a serial connector, testers are asked which connector they used when a printer lands in an error state, and rc1 raises Klipper and Moonraker printers directly. Each RC restates the same release-candidate warnings, so the notes read as testing instructions rather than a changelog.
Terragrunt is running the v1.1.0 release-candidate cycle, now at rc3. The first candidate completed six experiments simultaneously — stack-dependencies, a content-addressable store, a catalog redesign, mark-many-as-read, opt-out-auth and DAG queue display. The two candidates since have added only bug fixes for those features plus improvements to how releases are published and verified.
The experiment-graduation model is doing what it is supposed to: features developed behind flags land together in one minor, and the candidate cycle is purely stabilisation. The release-publishing and verification work appearing in rc2 suggests supply-chain provenance is being treated as release-blocking rather than as a follow-up.
With three candidates carrying identical feature lists, v1.1.0 final is the likely next release, followed by a fresh batch of experiments opening for v1.2.
The entire feed is the 2.0.0 release candidate series — four RCs between April and July 2026, no stable tag. The testing asks reveal what changed underneath: blocklisted serial ports and baud rates are migrated into a serial connector, testers are asked which connector they used when a printer lands in an error state, and rc1 raises Klipper and Moonraker printers directly. Each RC restates the same release-candidate warnings, so the notes read as testing instructions rather than a changelog.
Serial is being demoted from the way OctoPrint talks to a printer to one implementation of a connector interface, which is the structural precondition for supporting printers that speak something else. The cost is deliberate: rc1 removes deprecated APIs, warns that plugins will break, and points users at a recovery page to restart in safe mode. A maintainer running a long public RC cycle on a single-maintainer project is managing that breakage rather than rushing past it.
Expect further RCs until the connector migration stops producing reports, with the plugin ecosystem's readiness — not the core code — deciding when 2.0.0 goes stable.
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 Terragrunt or OctoPrint.
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.
Patch tags land monthly with release notes that itemize nothing.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
See all Terragrunt alternatives → · See all OctoPrint alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OctoPrint is currently shipping more aggressively (velocity 2.5 vs 0.0), 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. OctoPrint is currently shipping more aggressively (velocity 2.5 vs 0.0), 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 Terragrunt alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Terragrunt alternatives" section above for the current picks, or visit /alternatives/terragrunt for the full list with editorial commentary on each.
Top OctoPrint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OctoPrint alternatives" section above for the current picks, or visit /alternatives/octoprint for the full list with editorial commentary on each.