Infrastructure you read like code.
Servers, networks and services as versioned, reviewable code. 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 source.
Every change is a commit, and every rollout begins with a reviewable plan. The versioned target state defines what runs on the machines.
Declarative & versioned
The target state lives in Git, with history, diff and accountability for every change.
Reproducible
Versioned definitions make deployments repeatable across test, staging, and production.
Reviewable
Changes go through merge requests. The plan shows the proposed changes before apply.
Idempotent
Repeated applies converge each machine to its defined target state.
What we build with.
We use open-source tools for 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 standard configurations can be reused across projects.
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 roll out together with the infrastructure.
Secrets kept out
Credentials are machine-generated and stay out of version control.
New and existing environments.
We build new environments as code and convert established, hand-maintained systems into maintainable definitions.
-
/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 and repeatable.
-
/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.
-
/06
Handover & operations
We document the environment and train your team for handover. Ongoing operations are available if needed.
Configuration and history are versioned in the repository. Changes and their reviews remain traceable in Git.
Every change is made visible before it changes anything.
Reproducible code instead of undocumented clicks in a console.
OpenTofu, Ansible & co. on your own infrastructure, without vendor lock-in.
Move hand-maintained infrastructure into code.
Tell us briefly about your environment and your goal. We'll propose a repository layout, modules and a migration path.