Skip to content
PL
Services

Infrastructure & DevOps

I build environments you can rebuild from code, from a Proxmox cluster with Ceph to deployment pipelines in GitLab CI.

Request a quote

Who this is for

For companies that have outgrown a single server and need infrastructure with redundancy, repeatable deployments and a sane cost.

What you get

  • Design and rollout of a private cloud on Proxmox VE with a Ceph cluster and high availability.
  • Application or Docker clusters, including an image registry.
  • Infrastructure as code: Ansible and AWX for configuration, Terraform for cloud resources.
  • CI/CD pipelines in GitLab CI: build, test, deploy and roll back.
  • Migrations between on-premise and public cloud, in both directions.
  • Backups on Proxmox Backup Server and a disaster recovery plan that has actually been tested.
  • Architecture and runbook documentation, so the environment does not depend on one person.

Problems I typically solve

  • One host failure takes the whole service down because there is no redundancy.
  • Server configuration exists only in the administrator’s head.
  • Deploying to production is a manual procedure nobody wants to run on a Friday.
  • Backups are taken, but no one has ever verified a restore.
  • Public cloud bills grow faster than traffic.

Stack involved

Virtualization & private cloud

  • Proxmox VE
  • Proxmox Backup Server
  • Ceph
  • KVM
  • QEMU
  • Docker
  • MinIO

Automation & IaC

  • Ansible
  • AWX
  • Terraform
  • Bash

CI/CD

  • GitLab CI
  • GitHub Actions
  • Jenkins
  • Git

Public cloud & hybrid

  • Azure
  • AWS
  • Google Cloud
  • Oracle Cloud

How I work

Four steps, always in this order

No audit means no design, no design means no rollout. This order saves money by the third step.

  1. Step 01

    Audit and analysis

    An inventory of what is actually running and a risk list ordered by business impact. Without this step everything that follows is guesswork.

  2. Step 02

    Architecture design

    The target shape of the environment, with cost, schedule and a rollback plan. Decisions are made before the rollout, not during it.

  3. Step 03

    Implementation

    Staged delivery, with configuration described in Ansible and Terraform. Every step is repeatable and reversible.

  4. Step 04

    Operations and monitoring

    Monitoring with thresholds tuned to real traffic, updates, restore testing and a report on the state of the environment.

Frequently asked questions

Other services

Contact

Describe the problem and get a specific answer

The fastest way to get to the point is to outline your current environment and what needs to change in your first message.

················