Terraform codebase
Modules and a state layout that scale with your team: environments, remote state and locking done right.
Infrastructure as code for Google Cloud and bare metal
If your infrastructure lives in someone’s head or in a web console, it can’t be reviewed, repeated or recovered. I describe cloud and bare-metal infrastructure in Terraform and Ansible, so every change goes through Git and every environment can be rebuilt from scratch.
When to call me
Sounds familiar?
These are the situations where teams usually bring me in.
- Infrastructure was clicked together in a console, and nobody knows exactly what is there.
- Staging and production differ in ways nobody can fully explain.
- Terraform exists, but the state is fragile and people are afraid to run apply.
- Servers are configured by hand, and each one is a little different.
- Rebuilding a lost environment would take days.
What I deliver
What you get
Import of existing resources
Everything created by hand is brought into code — without recreating anything.
Ansible automation
Repeatable server configuration for bare metal and VMs instead of snowflake servers.
Networking
VPCs, subnets, firewalls, load balancing and DNS designed and documented as code.
Access & security
Least-privilege IAM, dedicated service accounts and secrets kept out of the codebase.
Pipelines for infrastructure
A plan on every merge request and an apply after review — infrastructure changes get the same workflow as code.
How it works
From first call to handover
- 01
Inventory
Map what exists today — in the cloud, on hardware and in people’s heads.
- 02
Codify
Import and describe resources in Terraform and Ansible, starting with the most critical ones.
- 03
Automate
Move plans and applies into CI with reviews, so changes are visible and reversible.
- 04
Document
Leave a codebase your team can read, extend and trust.
Tools
- Terraform
- Ansible
- Google Cloud
- Bare metal
- Linux
- Networking
- GitLab CI
- GitHub Actions
- Docker
FAQ
Common questions
- Can we adopt Terraform without recreating our infrastructure?
- Yes. Existing resources are imported into Terraform state step by step, so nothing has to be torn down or rebuilt.
- Do you only work with Google Cloud?
- Google Cloud and bare metal are where my experience is deepest. If your stack is elsewhere, get in touch anyway — the principles of infrastructure as code are the same, and I’ll tell you honestly whether I’m the right fit.
- Terraform or Ansible?
- Usually both: Terraform to create infrastructure — networks, instances, managed services — and Ansible to configure what runs on the servers, especially on bare metal.
Related services
Kubernetes
Clusters on Google Cloud (GKE) or bare metal — designed, migrated, upgraded and hardened. Secure by default, boring to operate.
CI/CD & Releases
Fast, reliable pipelines in GitLab CI or GitHub Actions — from commit to production with automated checks and safe rollbacks.
Audits & Cost Optimization
An independent review of your infrastructure: what to fix first, what to automate and where you are overpaying — in the cloud or on hardware.
Contact
Let’s talk about your infrastructure
Tell me what you’re building and where it hurts — I’ll get back to you with next steps.