Questions that come up before buying, answered directly.
Sorted into 4 blocks: Trust & lock-in · EU compliance · Operations · Pricing & migration.
Trust & lock-in
1. “What happens if you disappear tomorrow?”
Your app is TypeScript code on the open framework, and you can export code and data. If kumiko.rocks shuts down tomorrow:
- Your app keeps running, it doesn’t depend on our servers
- You deploy it yourself (Docker on Hetzner / Kubernetes / bare-metal)
- The framework and bundled features are public on GitHub under the MIT License, full source access, fork allowed, your own development allowed
- If we stop, anyone can carry the framework on without restrictions
Your app is as independent of us as a Linux server is of Linus Torvalds.
2. “We’re a large company. Who’s liable when something goes wrong?”
For Enterprise, an SLA, support guarantees and a source-code escrow with a notary are available on request. Standard for European mid-market with compliance requirements.
For kumiko.rocks Hosted, the hosting agreement governs operations; an SLA is available for Enterprise on request. For Self-Host, you’re responsible for operations (as with any open-source software).
3. “We hate vendor lock-in. How is that handled?”
Three layers:
- Your app code: you can export it and run it yourself on the open framework
- Your data: lives in your Postgres. Standard PG, no proprietary format.
pg_dumpout, into anywhere - The framework itself: public on GitHub under the MIT License (open source), NPM packages free to use, forks allowed. No “cloud-only API” like Firebase
4. “Who’s already running this?”
Kumiko runs as a pilot program in 2026. Live in production today: publicstatus.eu, a status-page platform that itself runs on Kumiko and serves multiple tenants with their own subdomain and branding.
You start your own project with the docs and the Show Pony tutorial.
5. “What if Kumiko doesn’t fit technically?”
Three layers of protection:
- Check the fit first: Kumiko is not for >100k events/sec or mandatory edge compute. The docs tell you before you build anything
- Start small: the Show Pony tutorial shows in one afternoon whether the approach holds for you
- Code is yours from day one: code and data can be exported, no lock-in
6. “Can we fork Kumiko and develop it ourselves?”
Yes. The framework is MIT licensed on GitHub. You may:
- Fork it and use it internally, unrestricted
- Publish and run your own forks, including as a platform for third parties
- Contribute patches and features, pull requests with a DCO sign-off welcome
The one condition of the MIT License: keep the copyright and license notice in your copies.
EU compliance
7. “GDPR data-processing agreement (DPA): what’s in it?”
For kumiko.rocks Hosted: standard DPA per GDPR Art. 28, hosting in Germany (Hetzner). Uploaded files and an encrypted copy of the database backups are stored at Scaleway in Paris. Template ships before contract start for review by your data protection officer.
For Self-Host you’re both controller and processor. No DPA needed because no external processing.
8. “Where is our data?”
Default hosting is Hetzner Germany, which also runs the DNS. Backups are in the EU. Uploaded files are stored at Scaleway in Paris (details in the subprocessor list). Local LLM (Llama, Mistral via Ollama) means even AI requests don’t leave your data center. If you use Anthropic or OpenAI, that runs through your own contracts with the US providers (BYOK), not through us.
9. “What does the audit trail look like in practice?”
Every change to an entity is an event in the database. In code, ctx.events.load(id, { asOf }) returns all events up to any point in time, which gives you the state at that moment. A per-entity history view in the UI is planned but not available yet.
ISO 27001 audit, GDPR access requests, internal review: each is one query instead of a sprint.
10. “What about GDPR erasure (right to be forgotten)?”
Crypto-shredding: PII fields are encrypted with user-specific keys. “Forget” = delete the key. The audit trail remains readable for compliance audits (event structure), personal data is mathematically illegible.
Detail: Event sourcing and audit.
11. “Can we run on-prem without internet?”
Yes. Own hardware, air-gapped setup, or Hetzner without outbound: all possible. Local LLM via Ollama runs on your own GPU server. You install updates manually as container images. Setup docs: Hosting and on-prem.
Operations
12. “What skills does my team need?”
- Minimum: TypeScript basics + SQL understanding. No event-sourcing vocabulary needed. Hello-World comes without it
- Mid-level: React + Postgres operations (migrations, backups). Standard stack
- Advanced: Event-sourcing concepts for complex domain models. Docs and examples included
Compared to other event-sourcing frameworks (Marten, Axon): a much lower entry barrier. You can build CRUD apps without writing a single “aggregate”.
13. “How fast is the database actually?”
We don’t publish our own throughput measurements yet. What we can say:
- Database: Postgres scales into the billions of rows, that’s not our bottleneck
- Scaling: API and worker containers run separately and scale horizontally
If you need >100,000 events/sec (trading platform, telemetry pipeline), Kafka or EventStoreDB belongs there, not Kumiko.
14. “What happens if the server dies? Restore story?”
Standard setup on Hetzner:
- Database backups: automatic daily Postgres snapshots, 30-day retention
- Off-site: daily encrypted copy of all backups to Scaleway Object Storage in Paris (a second, independent provider)
- Restore time (RTO): typically <2 hours after Hetzner server loss (new VM + restore snapshot + container restart)
- Data loss (RPO): the write-ahead log is backed up continuously, point-in-time recovery is possible
- Restore drill: we recommend once per quarter (can be automated)
For kumiko.rocks Hosted we run this. For Self-Host it’s your responsibility, with docs in Hosting and on-prem.
15. “How do updates work? Breaking changes?”
- Versions: Kumiko is pre-1.0. Releases ship often, and any minor version can contain breaking changes
- Migration notes: every breaking change is listed with instructions in the changelog.
bunx kumiko-upgradewalks you through the steps and applies codemods where they exist - Update path on Self-Host: container image pin in your hand. You decide when you update
- Security issues: please report them to hello@kumiko.rocks
16. “Which versions, which dependencies?”
Stack today (as of 2026-10-20):
- Bun ≥ 1.4 (runtime), Postgres (we run version 18), Redis (realtime and jobs), Meilisearch (optional, for search)
- External packages in the server bundle: @node-rs/argon2, sharp, bullmq, ioredis, postgres, temporal-polyfill, pino, pino-pretty, meilisearch
Stack docs: Hosting and on-prem.
Pricing & migration
17. “What does it really cost?”
The framework has no license fee, neither per user nor per app. Under the MIT License you may use it for any purpose, including hosting for third parties. What hosting costs depends on traffic and which building blocks you run. We work that out with you. Our own apps run together on three small servers at Hetzner. Details: Pricing.
18. “How do we migrate from [Excel/Notion/Airtable/Retool/in-house build]?”
Per tool, different:
- Excel/Notion/Airtable: CSV export → schema generation. Days of work for a mid-size table
- Retool: UI gets regenerated, data source (Postgres) stays. 2–4 weeks for a mid-size tool
- In-house (Node/Django/Rails): depends on complexity. Plan a few weeks for it
19. “What if the AI generates bad code?”
Three layers of protection:
- You approve: in Kumiko Studio every AI change is meant to arrive as a proposal in your conversation, and only what you approve is applied. Restoring an earlier state is meant to be possible as well. The Studio page shows how far each step has come
- Custom code stays untouched: the patcher only edits recognized patterns. Your own handler bodies are not overwritten
- Validation loop: TypeScript check + tests + linter feed back to the AI. If tests fail, it corrects. If that does not work, the request is meant to go to us. How far that handover has come is shown on the Studio page
20. “How do you prevent abuse from other tenants? Storage hog, mail spam, AI runaway?”
Structurally, not with monitoring band-aids: BYOK is the default, not a premium feature. What’s variably expensive runs through your accounts:
- Email send: Brevo, Postmark, SES, with your own SMTP key. When another tenant runs spam, their account burns, not a shared platform pool
- AI tokens: Anthropic, OpenAI or local model, with your own key. Cost explosion from bot loops hits the originator, not the platform pool
- File storage: your app’s files are stored at Scaleway in Paris, in a separate bucket per customer. Storage-hog tenants fill their own bucket, not other customers’
Limits for platform resources like egress, database and file storage are set in the respective hosted contract. No surprise suspensions, no hidden clauses.
At disproportionate load (>10× median over 7 days) we talk to you in person. Fair use, not algorithm.
21. “How do you technically protect our app against other tenants and external attacks?”
Four layers, all standard, all verifiable in the docs:
- Cross-App isolation via Network-Policy: Every app runs in its own Kubernetes namespace with an egress firewall. An app can only reach the services it needs (own database, own Redis, selected external APIs). Lateral movement to other customer apps is technically impossible on the network level
- Container hardening: the images run as a non-root user
- 3-Layer Rate-Limiting: Edge throttle on HTTP level (DDoS), strict auth-endpoint limit (brute force), plus per-handler rate-limits in the application code (domain-specific). Layers complement each other
- Backups: personal fields are already encrypted in the database (crypto-shredding). The daily off-site copy to Scaleway is encrypted on top, its contents are unreadable without the password
Plus on application layer: per-app database with its own Postgres role and GRANTs (cross-app DB reading technically impossible), field-level encryption for sensitive fields, Wireguard-VPN-only admin access (no public SSH).
Question not answered?
Contact: hello@kumiko.rocks
Want the app built for you? Kumiko Studio
Tech details: Framework for architecture overview, Docs for deep dives.