Your agents write the service. Zeroko runs it.
Why we built Zeroko, what it does today, and how to try it in the closed beta.
Coding agents got good at writing small backends: a webhook that files an issue, an API behind a weekend app, a tool the team uses every morning. Where they still stumble is the next step. To keep that backend running, an agent has to stitch together a function host, a database, a bucket, a queue and a scheduler, each with its own account, its own keys and its own way of failing.
Zeroko is that next step in one piece. A service is a JavaScript module, and everything it needs to keep state comes with it, as bindings: a SQLite database, file storage, background jobs and crons, realtime connections, static files, and calls to the other services of the workspace. Deploying is one HTTP request with the code in it. If the new version doesn't start, the old one keeps serving, and the agent reads why.
Three ways in
The skill. One Markdown file teaches any agent how Zeroko works: how to write a service, how to deploy it, every binding and every limit. Each workspace serves its own, filled in with its address, and agents fetch it again before each use, so what they know matches where they deploy.
MCP. For agents that speak the Model Context Protocol, the same API is an MCP server at the workspace's own address. In Claude Code it's one command, and then the agent deploys, reads logs, rolls back and queries its databases as tools.
The SDK. For a project you already have, the SDK deploys
it with its own build: Vite sites and apps, Nuxt, SvelteKit, Astro, React
Router, SolidStart, TanStack Start, Hono, Express and Koa. npm run build,
and it's live.
Open, and yours
The runner, the program that runs the services, is open source under the AGPL, and with the open source panel it's the whole product for one machine: you can run Zeroko on your own server today. The SDK and the panel are MIT. The code you deploy stays yours, under whatever license you choose: see Licenses.
Zeroko Cloud runs the runner for you: one runner per workspace, in its own sandbox, held to its plan, updated and brought back on its own.
Where we are
Zeroko Cloud is in a closed beta, on the Free plan, while we see how people and their agents use it. If you'd like in, write to us. Paid plans, your own domains and more come after the beta; this blog will say when.