Vaullet

Walking skeleton — the delivery path, with nothing behind it yet.

You are reading this over HTTPS, which means every hop below is working:

1. DNS vaullet.dev → Hetzner AX41, Ubuntu 26.04 LTS
2. ufw → klipper-lb → Traefik
3. a Gateway API Gateway, and an HTTPRoute that attached itself to it from another namespace
4. a Let's Encrypt certificate that cert-manager issued by planting a temporary HTTPRoute on the same Gateway
5. Service → Pod
6. and the manifest that put it here was synced by Argo CD from vaullet-dev/gitops, not applied by hand

Services land on this same path. Nothing about it changes when they do.