A backend for vibe coding — web apps, games and more
Hosting, a database and logins for your web app or game.
Hosting on your own domain, a database with your own server code, logins, saves, multiplayer and sharing on X. Ask your AI agent to set them up, pick only what you need, and pay only what it costs.
npx kumodeck signup
const kumo = await Kumo.init({ projectKey })// Signs in a guest
await kumo.saves.set('best', { score: 4200 })// Saves the best score
const room = await kumo.rooms.quickMatch('duel')// Finds an opponentA flat backend
Parts that run on the server for you. Use only the ones you need.
-
01
Logins
Users start as guests, then link an email and keep their progress. Rotating sessions, multi-tab safe.
kumo.auth.linkEmail() -
02
Cloud saves
JSON slots per user that follow them across devices, with version checks so two devices never clobber each other.
kumo.saves.set('slot1', s) -
03
Database & your code
Your own server code and SQL database, with cron and files. Anything you would run on your own server.
kumodeck functions deploy -
04
Multiplayer rooms
For games: quick match, 6-letter room codes, shared state, host migration and reconnect after a reload.
kumo.rooms.quickMatch('duel') -
05
Hosting
Versioned deploys, instant rollbacks, a URL per environment — and your own domain.
kumodeck deploy dist -
06
Realtime channels
Named rooms that deliver a message to everyone inside at once: lobbies, live events, shared workspaces. Voice calls too.
kumo.realtime.join('lobby') -
07
Sharing on X
Big cards, challenge links and how many people each post brought in.
kumodeck share on -
08
From your AI agent
Ask in plain words: deploy, use the database, check the costs. The agent runs the commands; you approve.
> Deploy it and share it on X.
How it works
Three commands from folder to live app.
-
1
$ kumodeck init
Create the project
Development and production environments, publishable and secret keys — in one step.
-
2
$ kumodeck config push
Declare the rules
Which features are on and room sizes live in kumo.config.json, enforced by the server.
-
3
$ kumodeck deploy dist
Publish it
Only changed files upload. Every version is kept; rollback is one command.
Build it yourself?
What you would build yourself, and what you write instead.
| Building it yourself | With KUMODeck | |
|---|---|---|
| User accounts | Auth server, password hashing, token rotation, guest upgrade | Kumo.init() |
| Your own server code | Servers, a SQL database, scaling, cron jobs | kumodeck functions deploy |
| Multiplayer | WebSocket servers, matchmaking, reconnection, host migration | rooms.quickMatch() |
| Hosting | CDN, cache rules, versioning, rollback | kumodeck deploy |
| Environments | Separate test data and keys | dev + prod per project |
Typical scope for a small team building a production-grade backend for one web app or game.
Your app runs in the user’s browser, so the rules are kept on the server.
Publishable keys only
The SDK refuses secret keys. What a browser holds can only act as one user.
Server-side rules
Limits and which features are on live in config. A modded client cannot change them.
Isolated environments
Test users and test data never touch production.
Start from your AI agent or from a template.
Tell your AI agent what you want to build, or start from a template: a Functions starter, and game templates for vanilla canvas, Phaser, PixiJS, three.js and a multiplayer lobby.