Question 1

What exactly counts as Infrastructure as Code?

Accepted Answer

IaC is any version-controlled, machine-readable file that defines infrastructure state. This includes Terraform HCL files that provision cloud resources, AWS CloudFormation YAML templates, Kubernetes manifests, Ansible playbooks, Pulumi TypeScript files, and even well-structured shell scripts committed to a repo. The defining criteria: it's readable by a machine (not just a human), it's stored in version control (Git), and it defines infrastructure state declaratively or procedurally. A one-off shell command typed into a terminal is NOT IaC — a shell script committed to your repo and run via CI/CD IS IaC.

Question 2

When should a startup start using IaC?

Accepted Answer

Start IaC earlier than you think — ideally before you have more than one environment (staging + production). The right trigger is your first 'I need to recreate this infrastructure' moment: setting up a staging environment identical to production, onboarding an engineer who needs a dev environment, or recovering from a server failure. If you've manually clicked through AWS or Google Cloud console to set things up, that's a sign to start codifying what you've built. A common approach: use a PaaS (Heroku, Railway) until you hit its limits, then migrate to IaaS + IaC. Starting IaC during the migration is easier than retroactively codifying a complex existing setup.

Question 3

What mistakes do startups make when adopting IaC?

Accepted Answer

The biggest mistake is treating IaC as an all-or-nothing migration. Teams try to codify everything at once, get overwhelmed, and abandon it. Start with new infrastructure only — codify it as you build it rather than retroactively converting existing resources. Second common mistake: not storing state properly. Terraform state files accidentally committed to Git or stored locally create conflicts and data loss. Use remote state backends (S3, Terraform Cloud) from day one. Third: not applying IaC to environments consistently — staging hand-coded, production in Terraform — so drift accumulates silently. Fourth: skipping code review for infrastructure changes, treating IaC as less important than application code.

Question 4

If we're using a PaaS like Heroku or Railway, do we still need IaC?

Accepted Answer

PaaS abstracts away most infrastructure concerns, so you may not need IaC at all in early stages. However, even PaaS deployments benefit from IaC for: configuring environment variables consistently across environments, managing add-ons and database tiers as code, and documenting infrastructure decisions for new team members. As you scale, PaaS limitations often push you toward IaaS — and having IaC habits before that transition makes it much smoother. Think of it as: PaaS removes the need for IaC urgently, but IaC mindset (configuration in code, not in dashboards) remains valuable regardless of the platform.

Question 5

How do I know if our IaC practices are working well?

Accepted Answer

Key indicators: (1) New environment provisioning time — how long does it take to spin up a new staging environment? It should be minutes, not days. (2) Mean time to recovery — after an infrastructure failure, how quickly can you restore service? IaC should make this dramatically faster. (3) Configuration drift — run periodic drift detection (terraform plan on production) to confirm actual infrastructure matches code. Zero drift is the goal. (4) Code review coverage — are infrastructure changes going through the same PR review process as application code? (5) Onboarding speed — can a new engineer provision a local dev environment without human assistance?

Question 6

How did Infrastructure as Code emerge as a practice?

Accepted Answer

IaC grew from the DevOps movement that emerged around 2008–2010, as teams realized that the gap between development and operations was causing reliability problems. Early tools like CFEngine (1993) and Puppet (2005) pioneered configuration management, but the modern IaC movement accelerated with Chef (2009), Ansible (2012), and Terraform (2014). The rise of cloud computing (AWS launched EC2 in 2006) made programmatic infrastructure provisioning practical and economically necessary. The term 'Infrastructure as Code' was popularized by Kief Morris's book of the same name (2016) and became a core DevOps principle. Today it's considered a baseline engineering practice for any team with more than one environment.

Question 7

How do IaC needs change as a startup grows from seed to Series B?

Accepted Answer

Seed stage: IaC is optional — a PaaS handles most concerns, and a simple Dockerfile plus deployment script suffices. Series A: IaC becomes important as you add environments, compliance requirements, and multiple engineers touching infrastructure. Terraform or Pulumi codifying your cloud resources is the right investment. Series B and beyond: IaC is essential — you need multi-region deployments, DR plans, security audits, and infrastructure that can be reviewed, tested, and rolled back like application code. At this stage, dedicated platform engineering may own IaC as a product itself, providing self-service infrastructure to product teams.

Question 8

What is GitOps and how does it extend Infrastructure as Code?

Accepted Answer

GitOps is an operational framework where Git is the single source of truth for both application code AND infrastructure state, and automated systems continuously reconcile actual infrastructure to match what's in the repo. In GitOps, a merge to main triggers automatic infrastructure changes — no manual terraform apply commands. Tools like ArgoCD and Flux implement GitOps for Kubernetes workloads. The benefits: every infrastructure change has a PR, code review, and audit trail; rollbacks are a git revert; and drift is automatically detected and corrected. GitOps is IaC plus automation plus Git-native workflows. Most startups encounter GitOps when adopting Kubernetes at scale.

IaC

Definition

Example Usage

Common Misconceptions

Related Terms

Technical Debt

Agile

Related Tools

Frequently Asked Questions about IaC

Explore More Resources

Browse Tools

Build Your Stack

Recommended Reading

Listen & Learn

Help us improve this definition

Help us improve this page

Stay in the loop