Service
Kubernetes and self-hosted infrastructure, set up by someone who runs his own
We set up and run the infrastructure behind websites and applications: servers, containers, deployments, monitoring and backups.
What we handle
You get a working deployment pipeline and someone to call when something looks wrong.
- Docker and Kubernetes setup, including private clusters
- Automatic deployments from GitHub on every merge
- TLS, DNS and CDN configuration with Cloudflare
- Container registries, backups and certificate renewal
- Uptime and error monitoring
What we run ourselves
Our own stack is the best reference. Everything below is in production today and is the same setup we build for clients.
- Proxmox hypervisor with a controller and three worker nodes running Kubernetes
- Harbor private container registry and GitHub Actions on a self-hosted runner
- Authentik single sign-on in front of internal tools
- Self-hosted n8n, Nextcloud, MCP servers and PDF services
- Cloudflare DNS, tunnels and HTTPS, with certificate renewal on a timer
Cloud or your own servers
Public cloud is the simplest choice for most teams. When data residency or monthly cost matters more, we deploy to private servers instead and run them the same way.
Frequently asked questions
Can you host a website you didn't build?
Usually yes, if it can run in a container. We review the code first and tell you what needs to change.
Which cloud providers do you work with?
AWS, Microsoft Azure, Google Cloud Platform, Cloudflare and private Kubernetes clusters.