Contact →

Architecture

54 CONTAINERS 3 NODES

dc1 dc2 dc3

Tech stack

Backend Go · Rust · Python PHP · Symfony FastAPI MySQL · Prisma
Frontend SvelteKit · React · Next.js TypeScript TailwindCSS · Vite
Desktop · Mobile · Infra Wails · Tauri 2 Flutter · Dart Docker · Proxmox Arch Linux

Why self-hosted

Paying for a cloud service means renting your own infrastructure: the data isn't really mine anymore, since it lives with a third party, subject to their terms, their outages, their pricing changes. Self-hosting reverses that. I own the hardware, I control the configuration, and none of it can be pulled out from under me overnight.

Concretely, that means 54 containers spread across three Proxmox nodes (dc1, dc2, dc3), on hardware I bought and administer myself. No monthly cloud bill, no third-party service standing between my projects and the machines that run them.

That principle goes well beyond the infra itself: chrysalide keeps its data 100% local, purify-tuya never phones home to Tuya's servers, and voice-lab runs entirely in the browser — the same conviction, applied twice, to the projects and to what runs them.

A question about the infra?

Write →