Deployment
Deploy Yoke — CLI, environment variables, single-tenant, multi-tenant, scaling, observability, and Docker.
This section covers running Yoke — as a library inside your server (the intended production path), and with the authoring CLI while you write the internal package.
Embed in your product
yoke-runtime in your binary — users never see Yoke.
Compile & deploy
yoke compile, dev, run, and deploy binaries.
CLI
Authoring command reference.
Environment
DATABASE_URL, YOKE_STORAGE, worker config.
Single-tenant
One runtime, one Postgres database.
Multi-tenant
Scale-to-zero compute with always-on Postgres.
Scaling
Horizontal workers and queue partitioning.
Observability
Metrics, health checks, logging.
Docker
Compose, executor image, control plane.
Deployment models
Intended production path. Your binary depends on yoke-runtime and calls YokeRuntime::start or start_colocated. Public HTTP is yours. Yoke ports stay private. See Embed.
Minimum production requirements
| Component | Requirement |
|---|---|
| Postgres | 16+, durable storage, backups |
YOKE_STORAGE | pg_sqlite or s3 (required) |
| Deno | 2.x (embedded at runtime; needed for dev) |
| Rust binary | yoke CLI, compiled deploy crate, or yoke-executor OCI image |
Quick production checklist
DATABASE_URL and run migrations (automatic on start).YOKE_STORAGE=pg_sqlite or s3 with YOKE_S3_BUCKET.yoke compile --crate) or a CLI crate (yoke compile).GET /metrics scraping for observability.