Skill 02
Infrastructure & self-hosting
Your own servers that get by on little hardware and still stay transparent.
Many small businesses pay for five cloud services that a single server could handle – with the data staying in-house. I plan and build these environments: virtualisation with Proxmox, services in containers, backups that have actually been restored.
It matters to me that you can see what is going on. Central logging, alerts on failed logins and monitoring that shows which layer is at fault during an outage – not just that “the internet is slow”.
What I do
- Virtualisation with Proxmox VE and LXC
- Setting up, hardening and documenting Linux and Windows servers
- Self-hosted services: Nextcloud, Pi-hole, password manager, Git
- Central logging and alerting with a small footprint
- Network diagnostics down to the individual layer
Tech stack
| Layer | Technology | Why |
|---|---|---|
| Virtualisation | Proxmox VE, LXC | many services on little hardware, cleanly separated |
| Containers | Docker, Docker Compose, Portainer | Git-backed stacks that update themselves |
| Operating systems | Debian/Ubuntu, Windows Server | whatever operations require |
| Logging | OpenObserve, Vector, rsyslog | full-text search at around 255 MB RAM |
| Network | Pi-hole, FRITZ!Box TR-064, mtr, dig | DNS filtering and troubleshooting without extra hardware |
| Access | WireGuard, Cloudflare | reachable from outside without open ports |
Related projects
Planning something similar?
Tell me by email what you have in mind. The first conversation is free.