When we reach for it
Every environment we build. The value is not automation, it is the review and the audit trail — a change to production infrastructure that had to be approved like code, and can be explained six months later.
Terraform engineering
Infrastructure declared in version-controlled files, so an environment can be reviewed in a pull request and rebuilt from the repository rather than from memory.
What we reach for first
When we would argue against it
State management is a genuine operational responsibility, and drift from changes made by hand in a console is the failure mode. If a client is not prepared to stop editing infrastructure directly, the code becomes fiction.
What it looks like in delivery
Remote state with locking, a plan posted to the pull request, and apply from the pipeline rather than a laptop. Environments differ by variables, so staging is the same description of the world as production.
Where this appears on the site
Published work that names it
Derived from the stacks published on those pages, not written here — so this list cannot claim something the page it points at does not say.
Also in cloud and infrastructure
Working in Terraform?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.