Overview
open-compute runs the Cloudflare Workers programming model — module workers, familiar bindings and workflows — on a single machine you own. Its pitch: one binary, one shared daemon, one object authority per instance. Storage defaults to the local filesystem, with S3-compatible storage optional.
Why it exists
workerd is a runtime, not a platform. It executes isolated Workers but provides no multi-tenant routing, durable state, scheduling, deployment lifecycle or control API. open-compute is that missing layer, shipped as one file.
Highlights
- Everything in one binary — runtime, control plane, scheduler and product bindings. Copy it to a host, point it at a directory, and serve traffic.
- Fast because it’s workerd — Worker code runs on a pinned, checksum-verified workerd fork, so isolates start in milliseconds.
- Nothing else to run — no Kubernetes, Redis, service mesh or distributed control plane; SQLite holds platform state.
- No vendor lock-in — the same Workers code can run on your own hardware.