Infrastructure / Platform Engineer
I help teams ship production infrastructure they can actually operate. Twenty years across enterprise Ansible automation, secret management, observability, and the messy seams in between. The engineer behind the IGN8 stack — available for selected engagements.
I build the unglamorous middle layer that lets product teams move fast — and I write it down so the next on-call engineer is not me at 3am.
I'm an independent infrastructure engineer based in Denmark. I spend my days inside enterprise Ansible Automation Platform fleets — APP-XXXX inventory generators, patching pipelines, security baselines — and my nights building the IGN8 open-source stack: a hub-and-spoke platform that wires secrets, inventory, configuration, and observability together with sane defaults.
I prefer working in small, accountable engagements where the brief is real and the constraints are honest. I will tell you when an idea is wrong, ship the boring version that works, and leave behind documentation, runbooks, and Ansible roles you can hand to a junior on Monday.
Four overlapping practices. Most engagements pull from two or three at once.
Design and build internal platforms on Hetzner, Proxmox, OpenStack or bare-metal. Pulumi-based IaC, Cloudflare DNS, Let's Encrypt + Caddy, Ansible-driven configuration. The full IGN8 hub-and-spoke pattern, or just the pieces you need.
Opinionated Ansible — the path is paved so teams can run their first automation on day one, not after a quarter of plumbing. Two delivery shapes from the same code: enterprise via Ansible Automation Platform (AAP), or self-hosted and containerized via Podman Quadlets. Inventory, credentials, execution environments, job templates, RBAC and rollouts — all defined as code, all reproducible.
NVD sync, fleet-wide vulnerability scanning (OpenVAS, OVAL, RH Insights), automated triage with GitHub Issues, secret management with HashiCorp Vault. Compliance-aware without the paperwork theatre.
When the infrastructure needs a UI on top: Django + DRF backends, Next.js frontends, Chrome extensions for capture flows. Pragmatic shipping over framework purity.
Pick the shape that matches your problem. We can refine on a 30-minute call.
One to two weeks. I embed, read the code, talk to the people, and hand back a written assessment with concrete next steps. Fixed fee.
Four to twelve weeks. Defined deliverable — a platform component, a migration, an automation pipeline. Weekly demos, runbooks, handover.
Ongoing, one to two days per week. I act as your senior platform engineer: architecture decisions, code review, mentoring, on-call escalation.
Brief description of the problem, the team, and any deadline you're working against. I reply within two working days.