The challenge
What the system needed to solve
Migrate several websites away from shared hosting and explore a customer-facing hosting stack without letting a billing experiment weaken the production cluster.
The build
Engineering decisions
Moved three independently versioned websites to stateless, anti-affined Kubernetes deployments behind redundant Caddy ingress.
Created container build pipelines and automated immutable-digest promotion for each site.
Designed a private-only FOSSBilling pilot with a dedicated service boundary, trusted private certificates, upgrade controls, backups, and a threat model.
Added public endpoint probes, certificate monitoring, GitHub-hosted off-site checks, and operational dashboards.
Architecture
How the pieces connect
- 1Independent site repositories
- 2Container build and registry
- 3GitOps deployment
- 4Redundant web edge
- 5Isolated billing and provisioning plane
Results
What changed
- Public websites no longer depend on a shared-hosting control panel.
- Source, image, and running release are traceable for every site.
- The billing platform remains deliberately private until its security and recovery gates justify broader exposure.
