Infrastructure you read like code.
Servers, networks and services as versioned, reviewable code — not hand-clicked one-offs. With OpenTofu/Terraform and Ansible we build infrastructure that rebuilds itself from the repository: from the first machine to the whole data center.
The repository is the truth.
Every change is a commit, every rollout a reviewable plan. What is in Git is what runs on the machines — not the other way around.
Declarative & versioned
The target state lives in Git — with history, diff and accountability for every change.
Reproducible
Same definition, same result — test, staging or production, today or a year from now.
Reviewable
Changes go through merge requests. The plan shows exactly what will happen before the apply.
Idempotent
Safe to apply again and again. No configuration drift, no snowflake servers.
What we build with.
Proven, open-source tooling — cleanly separated into provisioning, configuration and operations.
Provisioning
OpenTofu/Terraform brings up VMs, networks and resources on Proxmox and in the cloud.
Reusable modules
Vetted modules for VMs, networks and standards — defined once, used across every project.
Cloud-init templating
Machines boot pre-configured: packages, users, SSH keys and the agent from the first second.
Configuration management
Ansible roles, playbooks and inventory drive services, packages and policies to their target state.
Containers
Docker and Podman Compose definitions for services that belong in containers.
CI/CD & GitOps
Pipelines validate, plan and roll out — a merge into the main branch deploys the change.
Observability from day one
Monitoring, metrics and agents are rolled out with the infrastructure — not bolted on later.
Secrets kept out
Credentials stay out of version control — generated, not guessed, and never in Git.
From greenfield to takeover.
Whether a new environment or a grown, hand-tended landscape — we move it into clean, maintainable code.
-
/01
Assessment & target picture
What exists, what should be automated, where the risks are — and what the target state looks like.
-
/02
Modules & standards
Reusable building blocks, naming and network conventions, a repository layout that scales.
-
/03
Provisioning
Machines and resources via plan and apply — traceable, repeatable, no surprises.
-
/04
Configuration & roles
Ansible drives services, packages, users and policies into a defined, idempotent state.
-
/05
CI/CD & GitOps workflow
Pipelines that validate, plan and roll out on every merge request — review instead of gut feeling.
-
/06
Handover & operations
Documentation, training and optional ongoing operations — your team can take over, but doesn't have to.
One truth, with history and review — no knowledge stuck only in people's heads.
Every change is made visible before it changes anything.
Reproducible code instead of undocumented clicks in a console.
OpenTofu, Ansible & co. — no vendor lock-in, on your own infrastructure.
Done with snowflakes. Bring on the code.
Tell us briefly about your environment and your goal — we'll propose a repository layout, modules and a migration path.