SoftEther VPN
Post-quantum key exchange landed, then the release train went quiet.
A side-by-side editorial comparison of Terragrunt and Talos Linux — 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.
Talos 1.14 pulls BGP routing into the OS and locks /var down by default.
Talos is running a stable 1.12 patch line alongside the 1.14 beta cycle. The 1.12.x releases are pure maintenance — kernel bumps to 6.18.x, etcd lock and volume-mount race fixes, OOM protection for the pod runtime. The 1.14 betas are where the surface changes: an embedded GoBGP speaker configured through machine config, DNS over TLS and DNS over HTTPS per name server, btrfs for user volumes, and a set of new CRI configuration documents that apply without a reboot.
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.
Talos is running a stable 1.12 patch line alongside the 1.14 beta cycle. The 1.12.x releases are pure maintenance — kernel bumps to 6.18.x, etcd lock and volume-mount race fixes, OOM protection for the pod runtime. The 1.14 betas are where the surface changes: an embedded GoBGP speaker configured through machine config, DNS over TLS and DNS over HTTPS per name server, btrfs for user volumes, and a set of new CRI configuration documents that apply without a reboot.
The direction is to absorb infrastructure that used to live in system extensions or add-on DaemonSets into the OS config surface itself. Native BGP removes the reason to ship FRR; CRI base-runtime and customization documents replace machine-file patching; apply-config drops its reboot mode. At the same time the defaults are getting stricter — EPHEMERAL /var now mounts noexec, which the release notes admit breaks Longhorn v1 and vCluster on new machines.
Expect further 1.14 betas that keep reshaping the new document types before GA — the BGP surface already changed between beta.0 and beta.1 — while 1.12.x continues as a fixes-and-kernel-bumps line. The noexec default is the change most likely to generate follow-up guidance or an opt-out refinement.
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 Talos Linux.
Post-quantum key exchange landed, then the release train went quiet.
OpenMQTTGateway spent three years shedding its dependencies, then stopped shipping entirely.
umbrelOS now pins any Docker container to the home screen — the app store stopped being the boundary.
ZoneMinder 1.38 finally split capturing from analysing — and added roles to a system that had none.
YARA ships bounds checks, not features — three patch releases published thirteen minutes apart.
Dokku ships patches weekly, and quietly grows a Kubernetes backend under its single-host roots.
See all Terragrunt alternatives → · See all Talos Linux alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Talos Linux is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Talos Linux is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Talos Linux alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Talos Linux alternatives" section above for the current picks, or visit /alternatives/talos-linux for the full list with editorial commentary on each.