Home first, cloud at the edge.
Carddex started in Azure. Today its data, its operations and its control run on my own Proxmox fleet at home, and Azure keeps only what a customer touches, built so it can leave. It's the migration I sell, done on my own platform first, with every step in code and nothing switched on before it proved itself.
Operational numbers from November 2026. The migration is nearly done; what's still moving is marked as such below.
Data, operations and control.
Everything that is mine to run now runs at home, on hardware I can touch, without a per-hour meter.
The data lives here
The production database has run at home since October: PostgreSQL on a Patroni pair, one member per node, so either node can go down for a patch window and writes carry on. Every night a checked dump leaves the pair, Proxmox Backup Server keeps the guests, and a replicated S3-compatible store (Garage) holds the files behind the dashboards. Azure keeps a read copy next to the public API.
It can see itself
VictoriaMetrics and VictoriaLogs run on two nodes, and every producer writes to both. vmalert and Alertmanager page me with Azure unreachable, and the heartbeat rules are generated from the inventory, so a new machine can't be forgotten. A watcher outside the house pages me when the house itself goes quiet; the first drill passed. Azure Monitor stays on as a second path until the home pager has earned the job.
One identity, one secret store
Keycloak, a two-node cluster on the same HA database, signs people and services into Grafana, git and CI over OIDC. OpenBao, on three Raft voters, is the source of truth for secrets, and apps get theirs at deploy time instead of calling a cloud vault from their code. No Windows domain.
Builds and deploys from home
Builds already run on local agents, with BuildKit and package caches, so a build no longer pulls the internet each time. Forgejo now hosts git and the container registry, every Azure DevOps repo is being mirrored into it, and Jenkins is taking over the pipelines. Semaphore runs every converge and every Terraform apply, and an apply waits for a reviewed plan and a manual confirm. The cut-over from Azure DevOps is in progress.
Only what faces a customer.
- Customer-facing apps — stay on Azure Container Apps and are being made portable in place: no cloud SDK in the code, secrets handed in at deploy, our own hostnames. Leaving later is a deploy change, not a rewrite.
- The public API's read model — a PostgreSQL copy next to the apps, fed from home, so a customer never waits on a home line.
- This site — a free-tier Static Web App.
- Nothing else — the cloud DEV environment is being retired; only production stays in Azure.
Foundations before features.
Each phase lands switched off, gets proven, and only then goes live. Nothing depends on a step that hasn't earned it.
- Foundations — static addressing on every node and a default-deny firewall on every guest. Live.
- Observability — the home stores, the pager, the off-site watcher, Grafana. Live.
- Identity and secrets — Keycloak and OpenBao. Live.
- Builds — Forgejo and Jenkins. Switching over now.
- Queues, files and Terraform state — home, with the cloud as a copy. Next.
- App portability, then a smaller Azure — the apps stay in Azure, without anything that ties them there. Last.
The house is where the data and the work are, so the house runs everything that's mine. Customers shouldn't depend on one house, so the cloud keeps what faces them, built so it can leave. The target is an Azure bill of less than half what it was in October. I'll put the real number here once it's a month of invoices, not a forecast.