Deployment and regions
Where Kletso runs, what is cloud-hosted and what lives in your app, and the operational limits to plan for.
Hosted on Cloudflare
Kletso’s runtime and dashboard run on Cloudflare’s network: Workers for the API and dashboard, Durable Objects for conversations, D1 for the control plane, KV for cached configuration. There is nothing to install server side. Your app talks to api.kletso.ai; your team uses app.kletso.ai.
Domains
| Host | Purpose |
|---|---|
api.kletso.ai | Public API and realtime (/v1/*), demo backend (/demo/*), health (/health), discovery (/.well-known/kletso.json) |
app.kletso.ai | Dashboard |
kletso.ai | Marketing site and these docs |
Limits (defaults)
| Limit | Value |
|---|---|
| User messages per minute per end user | 30 |
| Components per surface / depth / size | 500 / 16 / 256 KB |
| Tool rounds per turn | 6 (agent setting) |
| History messages in prompt | 20 (agent setting) |
| Events replayed on reconnect | All events after the sequence you send |
| Session token | Short-lived, refreshed by the SDK |
Contact us for higher limits.
Data residency
Conversation state lives in Durable Objects placed near the first request. Control-plane data lives in D1. Region pinning and EU-only placement are Enterprise options in progress; see Roadmap.
Availability and status
The runtime exposes GET /health for your monitors. Deployments are zero-downtime: new Worker versions take over new requests while Durable Objects keep their state. We publish incidents at status.kletso.ai (planned) and by email to workspace owners.
Self-hosting
Kletso is built on Cloudflare primitives. A self-hosted option for Enterprise plans is on the roadmap; it will run the same Workers code on your own Cloudflare account with your own D1, KV and Durable Objects.