Infrastructure as code
If your infrastructure only exists in a console and in one engineer's memory, it cannot be reviewed, audited or rebuilt. We turn it into code that can.
Infrastructure as code means describing your servers, networks, Kubernetes clusters and their configuration in Terraform, Terragrunt, Ansible and Packer, and deploying applications through GitOps (ArgoCD) with policies (Kyverno). We do this on AWS (including EKS) and on Hetzner and other EU providers, for teams that need reproducible, reviewable infrastructure. Projects start at €4,000 and take 2–6 weeks.
We map what exists: accounts, networks, servers, clusters, DNS, secrets, and how changes are made today.
Repository layout, environments, state storage, module boundaries and the review flow.
We import and write the code step by step, with plans reviewed so nothing is recreated by accident.
CI for plans and applies, documentation, and a session where your team makes a real change.
When the project ends, a new engineer can open one repository and see every account, network, cluster and server you run, how it is configured, and the history of every change with its reviewer. A pull request shows a Terraform plan before anything changes. A merged pull request is applied by CI, not from a laptop.
For Kubernetes, ArgoCD keeps the cluster in line with Git. If someone changes something by hand, it shows up as drift. Kyverno policies stop the most common unsafe patterns before they run.
The same setup answers several audit questions at once. Who changed the firewall rule? The pull request. Was it reviewed? Branch protection. Can you rebuild after a disaster? Here is the code, and here is the last time we did it.
We built this model for a payments fintech: Terraform and Terragrunt on AWS, EKS for microservices, ArgoCD, Kyverno and KEDA, a Packer golden image, and Ansible for the card-processing stack.
We do not hide your infrastructure behind our own tools or modules you cannot read. Everything is standard open-source tooling in your own repositories.
A European fintech processing payments, cards and crypto, with 20–50 people and a regulated core. We lead its DevOps over the long term: infrastructure as code, PCI DSS controls, payments connectivity and disaster recovery.
Eight blockchain networks on dedicated servers, built with Terraform and Ansible. A custom health daemon knows when a node has fallen behind the chain and takes it out of rotation on its own.
From €4,000 excluding VAT for a small environment, such as one cloud account with a few services. Several accounts, Kubernetes and GitOps add scope. You get a fixed quote after we have seen what exists.
2–6 weeks, depending on size. We work in small steps, so parts of the infrastructure are under code within the first week.
No. We import existing resources into Terraform and check every plan before applying, so running systems are not recreated. Rebuilds happen only where you choose them.
Mostly AWS (including EKS) and Hetzner, plus other EU providers and dedicated servers. Tools: Terraform, Terragrunt, Ansible, Packer, ArgoCD, Kyverno and KEDA. We adapt to tools you already use where they make sense.
That is the goal. We keep the code plain, document the structure, and hand over with a real change made by your engineers. If you prefer, we can keep running it under a monthly plan.
Tell us what you run and where. We will suggest a first step and a fixed price.