Cloudflare platform coverage.
Use your Worker code, cloudflare.config.ts, framework adapters, and bindings. See the current product status before deploying.
Works with your ecosystem
#1 Requires an external LLM API.#2 Requires operator-provided runtime or sidecar.#3 Partial or work in progress; see documentation.
Deploy, run, and operate Workers.
CF CLI + GATEWAY
Deploy once. Serve locally or over HTTPS.
- cloudflare.config.ts with cf CLI
- Immutable deployments and rollback
- Shared Gateway with local and optional public routes
$ ocd status
$ ocd cf deploy --prebuilt --mode production
✓ uploaded 12 modules
✓ deployment v42 active
✓ /api/* → v42
$ ocd caddy status
READY shared HTTPS GatewayWORKER RUNTIME
Cloudflare-compatible runtime and bindings.
- Fetch, Streams, Crypto, and WebSockets
- Familiar bindings exposed through env
- workerd isolates with Local or S3-backed authority
type Env = {
CACHE: KVNamespace;
DB: D1Database;
BUCKET: R2Bucket;
};
export default {
async fetch(request: Request, env: Env) {
const profile = await env.CACHE.get("user:42", "json");
const row = await env.DB.prepare("SELECT * FROM jobs").first();
await env.BUCKET.put("request.json", request.body);
return Response.json({ profile, row });
},
} satisfies ExportedHandler<Env>;NATIVE EXTENSIONS
Bridge Workers to native capabilities.
- Use ordinary Service Bindings and props
- Reach local hardware, private libraries, and daemons
- Direct workerd-to-Provider Cap'n Proto data path
[extensions.local-files]
path = "./extensions/files"
Worker
→ Service Binding + props
→ JavaScript facade
→ Cap'n Proto session
→ native Provider
ocd authenticates the session,
then leaves the business data path.OPERATOR UIWIP
Manage the platform visually.
- Cloudflare-style product workflows
- Switch between registered instances
- Same /client/v4 API as cf CLI and the official SDK

OCD
One daemon. Isolated instances.
- Supervised workerd and Gateway processes
- Health, backup, and recovery workflows
- Verified upgrades with automatic rollback
$ ocd status
READY workerd supervised
STORAGE local authority
$ ocd --instance production backup list --json
✓ snapshots verified
$ ocd upgrade --dry-run
✓ active instances ready to upgradeA compact stack for self-hosted Workers.

//001Isolates, not containers.
Native workerd isolation without a container per request.

//002One binary. No sidecars.
Runtime, control plane, storage integration, and Dashboard ship together.

//003Authority stays local.
SQLite is authoritative. Deployments are immutable. Artifacts are content-addressed.
Self-host for free.
Everything you need to self-host:
- Apache-2.0 open-source platform
- Compatible runtime and product bindings
- Community support on GitHub
A managed open-compute experience:
- Hosted open-compute infrastructure
- Managed upgrades and backups
- Cloud dashboard and team access
Everything in Self-host, plus:
- Deployment and migration guidance
- Security and production-readiness review
- Direct engineering support
SEP 10, 2026
0.1.4
SEP 10, 2026
0.1.4 adds a complete Cloudflare Artifacts implementation for self-hosted open-compute installations. Operators can create namespaces and repositories, use Wrangler and Worker bindings, push and clone through Git Smart HTTP, and include repository data in the existing snapshot and restore lifecycle.
SEP 09, 2026
0.1.3
SEP 09, 2026
0.1.3 adds a project-native Wrangler workflow for teams running Cloudflare-compatible Workers on a self-hosted open-compute instance. A repository can now keep an ordinary wrangler.jsonc, select a named open-compute target, and use pinned Wrangler commands without copying control-plane URLs or credentials into project files.
SEP 08, 2026
0.1.2
SEP 08, 2026
0.1.2 is the first release with a complete day-to-day operator workflow for a single-machine open-compute installation. You can now initialize an instance, run it as an OS service, inspect it, open its Dashboard, upgrade it, and uninstall it safely.