Tech Stacks · Infra
Terraform
Category
Infra
At the studio
Since 2020
Projects shipped
2 case studies
Status
Active
(01) Our take
We write Terraform for every piece of infrastructure we set up, without exception. The discipline of declaring infrastructure in code — reviewable, versioned, reproducible — is non-negotiable on our engagements. We've seen too many teams burned by click-ops to compromise on this.
We use Terraform over Pulumi or CDK most often because the ecosystem maturity and the hiring depth are broader. For teams deeply invested in TypeScript, we'll happily use Pulumi — the underlying philosophy is what matters, not the tool.
(02) What we build with it
Typical work
- AWS infrastructure provisioning
- Cloudflare Workers and R2 configuration
- Multi-environment setups (dev / staging / production parity)
- Disaster recovery and infrastructure documentation
(03) How we engage
Engagement shape
Part of any infrastructure setup we ship. Standalone Terraform engagements cover codifying existing click-ops infrastructure for clients.
(04) In production
Where we've shipped it
(05) Pairs with
Works well with
Technologies we reach for alongside Terraform in most engagements.
Thinking about a Terraform project?