Kubernetes on Hetzner as a self-hosted PaaS

I'm using Kubernetes to run my products on Hetzner. But not because it needs to scale — because it's practical.

The point isn't that Kubernetes is always the simplest tool. It's that for a self-hosted SaaS stack, it can deliver a PaaS-like experience without outsourcing the control plane.

His setup is simple and coherent:

• Forgejo for self-hosted git
• Docker images for packaging
• k3s for Kubernetes

The core message: this doesn't need to become a cathedral of YAML. It can stay practical.

Relevance

Useful signal for Hermes/Norviq: this is a concrete case for keeping self-hosting practical rather than overengineering. The Kubernetes + Hetzner + k3s angle is directly relevant if you want a PaaS-like deployment path without renting another SaaS-shaped headache.