Every Terraform team eventually faces the same question: how do we manage dev, staging, and prod from one codebase? Terraform offers two answers. Workspaces let you reuse one configuration with separate state per workspace. Directory-per-environment gives each environment its own directory, its own backend config, and its own variables. Both work. Both have sharp edges. Picking the wrong one for your team size creates the kind of mess that takes a quarter to unwind.

This post explains how each approach actually works, where each one breaks down, and the hybrid pattern most growing teams land on.

How workspaces actually work

A workspace is a named container for state inside a single backend. One configuration, multiple state files.…