← Back to home
Comparison · Infra & APIs

Terragrunt vs werf

A side-by-side editorial comparison of Terragrunt and werf — release velocity, themes, recent moves, and the top alternatives to consider.

Terragrunt vs werf: at a glance

FeatureTerragruntwerf
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themesterraform, infrastructure-as-code, experiments, release-candidatekubernetes-delivery, multi-channel-releases, buildah, dockerfile-fidelity
Last editorial update3h ago1h ago
WebsiteVisit →Visit →

What is Terragrunt?

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.

Read the full Terragrunt trajectory →

What is werf?

Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.

werf publishes into parallel channels simultaneously — v2.75.3 tagged beta, ea and stable landed the same minute as v2.75.4 for alpha, while the v3 line runs separately through 3.0.2, a 3.0.0 alpha and a 3.1.0 dev build. The 2.x entries are corrective: buildah pull retries and serialisation, a stapel service script made executable regardless of umask, host cleanup no longer wiping other werf versions' git cache. The v3 entries carry the actual features.

Read the full werf trajectory →

Terragrunt vs werf: editorial side-by-side

T
Terragrunt
INFRA · APIS
0.0

Terragrunt graduated six experiments at once and has spent three candidates stabilising them

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

W
werf
INFRA · APIS
5.0

Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.

◆ Current state

werf publishes into parallel channels simultaneously — v2.75.3 tagged beta, ea and stable landed the same minute as v2.75.4 for alpha, while the v3 line runs separately through 3.0.2, a 3.0.0 alpha and a 3.1.0 dev build. The 2.x entries are corrective: buildah pull retries and serialisation, a stapel service script made executable regardless of umask, host cleanup no longer wiping other werf versions' git cache. The v3 entries carry the actual features.

◆ Where it's heading

The v3 work is about making builds predictable and inspectable: embedded kubeconform schemas, a per-project meta-repo safeguard with a migration path, additional patches files with the defaults disableable, and repo-built scratch images made readable by dive. Meanwhile v3 alphas are restoring flags that v3 had dropped, which suggests the major is being trimmed and then walked back based on review. Dockerfile fidelity — COPY --parents, COPY/ADD --exclude in staged builds — is a recurring thread across both lines.

◆ Prediction

Expect the 2.75 line to keep taking build-backend fixes while v3 stabilises, with more v2 flags restored in v3 alphas as review findings land before the major reaches a stable channel.

Alternatives to Terragrunt and werf

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 werf.

See all Terragrunt alternatives → · See all werf alternatives →

Recent activity from Terragrunt and werf

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5h agowerfv2.75.3 stops host cleanup wiping other versions' git cache
  2. 5h agowerfv2.75.4 makes buildah base-image pulls retry and serialise
  3. 19h agowerfv3.1.0 embeds kubeconform schemas and adds a meta-repo safeguard
  4. 7d agowerfv3.0.2 fixes build-log progress ordering
  5. 8d agowerfv3.0.0-alpha.2 restores dropped deploy flags and honors COPY --parents
  6. 1mo agoTerragruntv1.1.0-rc3
  7. 1mo agoTerragruntv1.1.0-rc2
  8. 1mo agoTerragruntv1.1.0-rc1

Frequently asked questions

What is the difference between Terragrunt and werf?

They serve adjacent needs but don't currently overlap on shipped themes. werf 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.

Is Terragrunt better than werf?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. werf 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.

What are the best alternatives to Terragrunt?

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.

What are the best alternatives to werf?

Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.