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 GLAuth — 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.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
GLAuth's 2.5.0 in April was the substantial release: OpenTelemetry tracing wired through the handler and plugin packages plus otelsql, embedded plugins, RISC-V platform support, StartTLS and LDAPS brought to feature parity, and LDAP paging compatibility when proxying. The two releases since are corrective — rejecting disabled users on all backends during Bind, an arbitrary-password issue, and a release-time plugin compatibility check.
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.
GLAuth's 2.5.0 in April was the substantial release: OpenTelemetry tracing wired through the handler and plugin packages plus otelsql, embedded plugins, RISC-V platform support, StartTLS and LDAPS brought to feature parity, and LDAP paging compatibility when proxying. The two releases since are corrective — rejecting disabled users on all backends during Bind, an arbitrary-password issue, and a release-time plugin compatibility check.
The direction in 2.5.0 is toward being operable in production rather than merely functional: distributed tracing, a config watcher that notices files added to a directory, credentials no longer leaking at INFO log level, and a legacy behaviour mode so existing deployments can upgrade without changing semantics. The patches since suggest the authentication paths are getting scrutiny they had not previously had, with disabled-user handling inconsistent across backends until 2.5.1 fixed it.
Expect the 2.5 line to keep taking small authentication-correctness fixes, with the embedded plugin mechanism and the release-time compatibility check pointing toward more attention on how third-party backends are built and shipped.
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 GLAuth.
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.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
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 GLAuth alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. GLAuth is currently shipping more aggressively (velocity 5.0 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. GLAuth is currently shipping more aggressively (velocity 5.0 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 GLAuth alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GLAuth alternatives" section above for the current picks, or visit /alternatives/glauth for the full list with editorial commentary on each.