Tech USP: Kumiko apps are standard Bun containers. They run where you decide: on our infrastructure, on yours, or on an air-gapped box in your own data center. The same code, the same data model, the same event history.
Buyer’s view: “Our compliance officer wants the data in our own data center, our developers want fast iteration, and our CFO wants to know where the bill comes from.”
Three modes, your choice
| Mode | What it is | Audience |
|---|---|---|
| Hosted | We run it on our EU infrastructure. | Mid-market without DevOps capacity |
| Self-host | You run it on your cloud (Hetzner, AWS-EU, your private cloud, Kubernetes). We ship the build, you ship to production. | Mid-market with DevOps, agencies, developers who want full control |
| On-prem | You run it inside your own data center. Air-gapped works too. Zero outbound dependency on us. | Regulated industries, public-sector contracts, enterprises with strict data policies |
Switching modes later is straightforward: same containers, same database format. Hosted today, self-hosted next year? Export, deploy, point DNS. We help.
EU hosting reality
For the hosted option, your app and database run on Hetzner Cloud in Nuremberg, Germany. Backups stay in EU storage. DNS is also run by Hetzner.
Hosted in the EU, from the database to the backup.
For self-hosted and on-prem, you decide the region, the provider and whether anything leaves your network at all.
Admin without exposed ports
For the hosted option, the servers running your app have no public SSH port. Not closed-by-firewall, not behind fail2ban, just not exposed at all. Admin access is over a private VPN that only authorized operators can connect to.
What this means in practice:
- Brute-force scans hit a closed port and bounce.
- Compromise of a single ops machine doesn’t grant access: the VPN keys are per-operator.
For self-hosted, you decide your own admin posture. We document the same setup so you can replicate it if you want.
What’s built in
- Multi-stage build:
kumiko-buildproducesdist/(client) +dist-server/(server bundle), runtime externals documented - Pre-deploy migrate:
kumiko schema applyas an ephemeral container step - Boot gate: missing migrations or tables → container exits with a clear error. No silent auto-heal in production
- API/Worker mode split: split your app into web-facing and background-job containers when load demands it
- Per-instance consumer delivery: caches stay in sync across replicas without you wiring up the plumbing
Custom domain on your terms
Hosted apps ship with a default URL on our platform. If you want, you bring your own domain (tools.acme.de, intern.muster-ag.de) and we handle the certificate. Your customers see your brand, not ours.
For self-hosted and on-prem, the domain is whatever you point at the box. There’s no “Kumiko-branded URL” anywhere in the code.
Architecture deep dive
- lifecycle: startup phases, graceful shutdown
Reference: samples/showcases/publicstatus/deploy/ (Dockerfile + docker-compose + GHA workflow).
Continue in the docs