Choose a deployment
Proxy and Admin share one data plane. Choose the runtime and database first, then use deployment instructions matching the same release.
| Option | Database | Suitable needs | Guide |
|---|---|---|---|
| Self-hosted Docker / Node | Postgres or MySQL | Existing container platforms, private networks and explicit backup/data placement | Docker |
| Cloudflare Workers | D1 | Edge execution with platform resource and plan constraints | Cloudflare |
Both options run models, REST tools and supported MCP capabilities. Verify upstream reachability, regional availability and WebSocket paths in the actual environment.
Local evaluation and production
Section titled “Local evaluation and production”Use Quick start for a local evaluation. For production prepare:
- Matching Proxy, Admin and migration versions connected to the same database.
- A strong Admin password and secure handling of provider credentials and named integration keys.
- HTTPS, backups, health checks and real tests for the client protocols in use.
- An upgrade and maintenance procedure.
See the deployment reference for supported combinations. This site summarizes choices; database commands and platform settings live in the release-specific repository docs.