Hosting + on-prem — you choose where it runs

Tech USP: Kumiko apps are standard Bun containers. Coolify, Hetzner, Kubernetes, bare-metal — all work.

Deploy options

Mode	Setup	Audience
Coolify on Hetzner	Multi-stage Dockerfile + pre-deploy migrate step	Solo devs, indie hackers
Kubernetes	Standard container, init-container for migrations	Mid-market with DevOps
Bare-metal	Bun + Postgres + Redis + Meilisearch	Strict on-prem European
kumiko.so Hosted	Click → live (H2 2026)	When you don’t want to operate it

What’s built in

• Multi-stage build — kumiko-build produces dist/ (client) + dist-server/ (~1 MB server bundle), 7 native externals documented
• Pre-deploy migrate — kumiko migrate apply as an ephemeral container step, drizzle-kit + automatic projection rebuild
• Boot gate — missing migrations or tables → SchemaDriftError, container exits. No auto-heal in production
• API/Worker mode split — createApiEntrypoint + createWorkerEntrypoint + createAllInOneEntrypoint, lane routing for jobs and MSP consumers
• Per-instance consumer delivery — SSE consumer per instance, delivery: "per-instance" for cache sync between API replicas

Architecture deep dive

• hosting-stack — Coolify/k8s/bare-metal setups
• migrations — per-app migration story
• scaling — API horizontal, worker as separate processes
• lifecycle — startup phases, graceful shutdown

Reference: samples/showcases/publicstatus/deploy/ (Dockerfile + docker-compose + GHA workflow).

Where this lands in the pitch

• EU mid-market: Top argument “data stays with you” — on-prem is real, not marketing speak
• Indie hackers: Hetzner stack demo (”~€50–150/month instead of several hundred dollars for Vercel + Supabase + Clerk”)