Start
Introduction
A runtime for the small services your agents build.
Zeroko runs small HTTP services: websites, APIs, webhooks and backends, each
a few JavaScript modules. Your agent writes the code and deploys it in one
request; Zeroko gives it an address, https://<name>.<domain>, and whatever
it asks for through bindings:
| Binding | What the service gets |
|---|---|
db | A SQLite database, with locks for changes from concurrent requests |
files | File storage, streamed, up to 5 GB a file |
jobs | Background work with retries, and crons |
realtime | WebSocket and Server-Sent Events connections on channels |
assets | The static files deployed with the code |
service:<name> | Calls to another service, without leaving Zeroko |
A service's process keeps nothing between requests: it starts in about 40 ms on the first request and stops when idle. Everything it keeps goes through a binding, so nothing is lost when it stops, restarts or gets a new version.
The pieces
- The runner runs the services. It is one container with one volume, and it has an API but no interface. It is open source (AGPL).
- The panel manages one runner: services, versions, logs, data, tokens and settings. It also serves the skill agents read, and the runner's API for them. The open source panel is self-hosted next to the runner.
- Zeroko Cloud runs a runner for each workspace, yours or a team's, in its own sandbox, on plans from free: see Zeroko Cloud.
Where to go next
- Quickstart: a service deployed in a few minutes.
- Zeroko Cloud: workspaces, plans and teams.
- Teach your agent: the skill, and how agents use it.
- Self-hosting: the runner and the panel on your own machine.