IaC

Infrastructure as code: defining servers, networks and services in declarative files that are versioned and applied automatically.

Infrastructure as code means your infrastructure lives in files instead of consoles. Servers, databases, DNS records and permissions are declared in code, Terraform, Pulumi, CloudFormation or the simpler YAML of modern PaaS platforms, and a command reconciles reality with the declaration. Change a file, review it like code, apply it, and every environment can be rebuilt from the repository.

Why it matters to an indie builder: the failure mode IaC prevents is the snowflake server, hand-configured over a year, undocumented, unreplicable, and unrecoverable when it dies. If your product runs anywhere beyond a single hobby VPS, the ability to stand the whole stack up again from a repository is the difference between a bad afternoon and a business-ending weekend.

A concrete example: a database migration gone wrong at 2am. Without IaC: recovery depends on remembering eleven console settings across two providers and the memory of whoever set them up. With IaC: the environment is a 200-line file in git; recovery is apply the previous commit, about six minutes, and the disaster retrospective has a diff to read. The whole setup cost one focused afternoon.

Common mistakes: hand-tweaking infrastructure after applying the code, creating drift where the files lie about reality and the next apply destroys the manual fix (discipline: console changes are forbidden once a resource is managed), managing everything including what the platform already simplifies (a PaaS already is declarative infrastructure; only codify what it does not cover), secrets in state files, which Terraform keeps in plaintext unless configured otherwise, and skipping environments: declare at least production and staging so that rebuilding one is proven, not theoretical. The hosting and devops blocks on IndieBoot mark platforms whose entire value proposition is this idea.