Infrastructure as Code Without State Files (and Without the Headaches)
If you've managed cloud resources over the last decade, you've likely had a run-in with a state file.
Whether it's Terraform's .tfstate or Pulumi's stack state, traditional Infrastructure-as-Code (IaC) tools rely on a centralized ledger. This file is their source of truth-a mapping of declared resource names to physical cloud IDs, tracking metadata and dependencies.
While state files solved a major problem in the early days of cloud automation, they introduced a host of operational challenges that teams spend hundreds of engineering hours managing.
Puls is built around a different philosophy: what if we didn't need state files at all?