Terraform Infrastructure as Code & GitOps
If your infrastructure is still managed by hand, or your Terraform setup has grown into a single sprawling workspace that takes forever to plan and is risky to touch, this is where I help. I work with engineering teams across Canada and the US to turn ad-hoc infrastructure into version-controlled, automated, and genuinely maintainable Terraform. The goal isn't just "using Terraform" — plenty of teams already do that and still end up with brittle, slow-to-change setups. The goal is infrastructure code your team can read, extend, and trust, backed by a CI/CD pipeline that deploys changes safely without babysitting.
What's included
- Terraform automation for new and existing AWS infrastructure
- Reusable, composable module design to replace copy-pasted configuration
- Zero-downtime CI/CD pipelines using GitHub Actions
- Workspace and state restructuring for teams whose plans have become slow or risky
- Full documentation and knowledge transfer, so your team owns the result
- I use AI coding tools to speed up Terraform module generation and improve GitHub Actions workflows, with every change reviewed before it ships
Proof it works
- Cut Terraform plan time 90%, from 20 minutes to 2, by splitting a 1,000+ resource workspace into scoped states.
- Reduced CI/CD build time 60% by eliminating 180 redundant Docker builds.
- Cut infrastructure code duplication 70% with shared, reusable modules.
- Brought new-service provisioning time down from 2 weeks to a couple of hours.
Typical engagement
Engagements here are fixed-price and scoped up front, after a free 30-minute call to understand your current setup — whether that's no Terraform at all, a single sprawling workspace, or something in between. The scope and price are agreed before work starts, so there's no open-ended billing. The work itself is hands-on: writing and restructuring Terraform code, building CI/CD pipelines, and documenting the result so your team isn't dependent on me to understand or extend it afterward. Everything built — the Terraform code, the modules, the pipeline configuration — is yours outright; there's no proprietary tooling or license lock-in. This is a good fit if your team wants to own its infrastructure code long-term rather than depend on an external vendor. It's less of a fit if you're looking for a managed-service arrangement where someone else continues operating the infrastructure indefinitely — this is scoped, delivered, and handed off, with documentation and knowledge transfer so your team can run it. I respond to inquiries within 24 hours and work with teams in both Canada and the US.
FAQ
Do we need to already be using Terraform?
No. Some clients come in with zero infrastructure-as-code and some have an existing setup that needs restructuring — the scoping call establishes where you're starting from.
How long does a typical Terraform engagement take?
Typically a couple of days to a couple of weeks, depending on scope, complexity, and how quickly we get access and get oriented in your environment — the scoping call narrows this down before work starts.
Who owns the Terraform code after the project ends?
You do, entirely, along with documentation and a knowledge-transfer session so your team can maintain and extend it independently.
How it works
Simple, low-friction engagement. No lengthy contracts or discovery phases.
Tell me what you need
Fill out the contact form with a brief description of your challenge. I'll respond within 24 hours.
Quick scoping call
We jump on a 30-minute call to understand your environment, goals, and timeline. I'll follow up with a clear scope and fixed price — usually within a couple of days, up to a week for more complex asks.
I get to work
Hands-on delivery with regular updates. You get clean documentation and knowledge transfer — not a black box.
Done — and you own it
Everything I build is yours. I document it thoroughly so your team can maintain and extend it independently.
Ready to talk about infrastructure as code & gitops?
Tell me a bit about your challenge and I'll get back to you within 24 hours.
Get in touch →Related posts
The CI/CD Mistake That Was Costing Us 180 Redundant Docker Builds
Build-time environment variables were silently forcing a rebuild for every environment and region combination. Switching to runtime variables cut CI/CD build time 60%.
How I Cut Terraform Plan Time From 20 Minutes to 2 (a 90% Reduction)
A single 1,000+ resource Terraform workspace was making every plan take 20 minutes. Here's how restructuring it into scoped folders and states fixed it.
Designing Terraform Modules Teams Actually Want to Reuse
A few rules of thumb for keeping Terraform modules small, composable, and safe to change without a scary blast radius.