Guides¶
Guides show how to get one job done end to end: what the runtime does under the hood, then the commands and code you need. They assume you have a node and a tenant key; if not, start with Get started or Self-hosting.
Using a node¶
For developers (tenants) who deploy and look after services.
-
Get access
How the operator creates a tenant and a key, how you configure
21ci, scopes, your own tokens, expiry and rotation. -
Projects and environments
Group services into projects, give them
production,stagingor preview environments, and deploy into them. -
Deploy and roll back
Create a service, deploy a file, a directory or a component, activate, roll back, rebuild and delete.
-
Configure a service
Limits, access, environments and allowed callers, env vars and secrets, scaling and what takes effect when.
-
Logs, stats and usage
Tail and follow logs, read build logs, stats, events and usage, and debug a request by its task id.
-
AI assistants (MCP)
Connect Claude Code, Cursor or Claude Desktop to a node and let them deploy and debug with a token made for them.
Building services¶
-
Deno services
TypeScript and JavaScript handlers: Form A and Form B, request and response, env and secrets, outbound
fetch. -
WASM services
WASI P2 components exporting
wasi:http/incoming-handler: the contract, linked interfaces, lifecycle and limits. -
KV, SQL, blobs and other sub-services
Every built-in sub-service with a Deno and a Rust example: KV with
incrand TTL, SQL, blobs, queues, schedules, calls and bindings. -
Service calls and queues
Call another service in-process, control who may call whom, and hand work to a durable queue.
-
Schedules
Interval and cron schedules, and exactly what happens when a run is slow or the node was down.
-
WebSockets and durable objects
Accept WebSockets, keep per-room state in durable objects with storage and alarms, and move over from Cloudflare Durable Objects.
-
Custom domains
Path routes, wildcard subdomains and your own host names, with DNS TXT verification.
-
Optimize your service
Cold versus warm, reuse-safe code, cheap top levels, small bundles, batching, streaming and limits.
Languages and frameworks¶
Which languages and frameworks work on each runtime, with requirements, limitations and working skeletons: overview, Deno, WASM.
Running a node¶
For operators who self-host the runtime.
-
Self-hosting
One Linux machine: Docker Compose, a systemd unit, or a small VPS with automatic TLS.
-
Production deployment
A company runbook: proxy and TLS, backups, monitoring, upgrades, key rotation, capacity and incidents.
-
Resource requirements
CPU, RAM and disk for a node, what each service and sub-runtime costs, and how to measure it.
-
Performance tuning
Profiles, warm pools, caching and scheduler settings.
For providers¶
Companies that build a product on top of a node can give tenants an SDK that the runtime runs for them, with controlled access to their own API and without handing out credentials: Operator SDKs and bindings. Tenants: Use operator SDKs.
Which guide do I need?¶
| You want to… | Read |
|---|---|
| Get a key for a node and set up the CLI | Get access |
| Give CI or a colleague a narrower token | Get access |
| Keep apps, staging and production apart | Projects and environments |
| Let an AI assistant deploy and debug | AI assistants (MCP) |
| Deploy, update or roll back a service | Deploy and roll back |
| Change limits, env vars, secrets or who may call a service | Configure a service |
| See what a service is doing | Logs, stats and usage |
| Deploy a TypeScript service that calls an outside API | Deno services |
| Serve a hot, stateless endpoint with low overhead | WASM services |
| Store data | Sub-services |
| Use Hono, drizzle, Go, Python or C | Languages and frameworks |
| Make a service cheaper or faster | Optimize your service |
| Split an app into services that talk to each other | Service calls and queues |
| Process work in the background, with retries | Service calls and queues |
| Run a job every hour, or at 09:00 on weekdays | Schedules |
| Build a chat, a live dashboard or a multiplayer room | WebSockets and durable objects |
| Move a Cloudflare Durable Object | WebSockets and durable objects |
Serve a service at api.example.com |
Custom domains |
| Run a node on one machine | Self-hosting |
| Run a node for a company | Production deployment |
| Size a node | Resource requirements |
| Let tenants use your platform API safely | Operator SDKs and bindings |
Learn by building¶
The tutorials build complete apps from the runtime's sample/apps/ directory: a Telegram
bot, an event sign-up service, a live queue, a currency-rate poller and a WASM edge gateway. They use the features
these guides explain, in context.
For background on how things work, see Concepts; for exact fields, limits and error codes, see the Reference.