Self-hosted Cloudflare Workers-compatible platform with Workers、KV、D1、R2、DO、Queues、Workflows、Cron、Cache、Images、Vectorize、AI Search、Artifacts、Static Assets、Service Bindings、Dynamic Workers、LogTail、Gateway in one Rust binary.
★ 3,691⑂ 106👁 29⑃ 114● 86▤ 18
+20
日增长
3,691
stars
106
forks
29
watchers
114
prs
86
issues
18
releases
README
One binary. One daemon. Isolated instances.
A self-hosted, Cloudflare Workers-compatible platform for a single machine.
Website
· Docs
· Compatibility
· Architecture
English · 简体中文
---
The Workers platform, running on your hardware
You already know how to write Cloudflare Workers. open-compute runs the compatible Workers programming model — module workers, familiar bindings, and cf workflows — on a single machine you own.
One binary. One shared daemon. One object authority per instance. Local filesystem is the default; S3-compatible storage is optional.
No Kubernetes. No Redis. No service mesh. No distributed control plane to babysit. No vendor lock-in.
Everyone else open-compute
───────────── ────────────
gateway + router ┌──────────────┐
control plane │ │
scheduler service ═══ │ ocd (1 bin) │
Redis / Valkey cluster │ │
Postgres └──────────────┘
K8s + operators + SQLite + Local/S3 objects
Why open-compute
workerd is a runtime, not a platform. It executes isolated Workers brilliantly — and stops there. No multi-tenant routing, no durable state, no scheduling, no deployment lifecycle, no control API. Everyone who wants Workers on their own infrastructure has to build that layer.
open-compute _is_ that layer — and it ships as one file.
- One binary, everything inside. Runtime, control plane, scheduler, and every product binding. Copy it to a host, point it at a directory, and you are serving traffic.
- Fast because it's workerd. Worker code runs on a pinned, checksum-verified workerd fork. Isolates start in milliseconds — not one process or container per request.
- Nothing else to run. SQLite owns platform metadata and Local storage owns object bytes by default. S3-compatible storage is optional; neither mode needs a database or cache sidecar.
- Pinned and verified. The runtime and its assets are fixed and verified at build and startup. Production startup stays offline.
- Yours completely. You own the code, data, and machines. External services are optional and explicitly configured.
Compatibility
Write standard module workers (export default { fetch }) with the bindings you already know. Supported means the documented public API matches Cloudflare. Single-node differences are listed in the compatibility guide. A running daemon reports its surface with ocd capabilities --json. If behavior differs from Cloudflare, please open an issue.
| Supported | Partial | Not yet |
| ------------------------------------------------------------- | ------------Top issues
#128test: qualify Python Workers frameworks, bindings, RPC, and networking end to end3 comments · 2026-09-26#148Support custom-domain HTTP Host routing behind external reverse proxies without managed Gateway1 comments · 2026-10-08#201ocd 0.4.0: each HTTP request adds ~5-7 MB to the embedded workerd's anonymous memory, never reclaimed (idle memory is flat)0 comments · 2026-11-14#200D1: ALTER TABLE RENAME TO / RENAME COLUMN / DROP COLUMN fail with 9100008 (0.4.0)0 comments · 2026-11-13#199Durable Object disk watermarks should use absolute free space, not a percentage0 comments · 2026-11-08#159Upgrade blocker: built-in Dashboard alone prevents v0.2.2 → v0.3.0; need a data-preserving transition0 comments · 2026-10-12#157bug: idle workerd memory grows with every Durable Object alarm-repair wake-up and is not released0 comments · 2026-10-11
Latest release
open-compute 0.4.0 v0.4.0 2026-10-31Open Compute 0.4.0 adds Container execution and snapshot paths for single-machine deployments. Publication requires every revision-bound release qualification job to pass. What's new - The implementation adds an operator-owned Container Broker and immutable Container targets. Code-only deployment keeps the current execution. Image or resource deployment creates a new target and retires the previous execution. - Durable Object containers gain process lifecycle, HTTP and WebSocket transport, exec streams, named images, inactivity policy and snapshot code paths. The local product cases e
News & coverage (9)
Hacker NewsOpen-Compute: Celld Alternative▲ 1 · 0 comments · 2026-10-09DiarioBitcoinGitHub Universe 2026 pone el foco en la evolución de toda la pila tecnológica2026-10-28irblog.prnewswire.comAMI Contributes its Tektagon OpenEdition Platform Root of Trust Firmware Code Base to the Open Compute Project2022-10-18PC WorldMicrosoft cloud server designs for Facebook’s Open Compute Project2014-01-27The GitHub BlogGitHub Universe 2026: Evolving every layer of the stack2026-10-28Microsoft AzureAdvancing hardware security with open-source Integrated HSM technology2026-10-13Engineering at Meta BlogOCP Summit 2026: Powering AI with Open Innovations in Scale-Up, Scale-Out, and Scale-Across Networks2026-10-12HPCwireNvidia to Nab Hugging Face, the ‘GitHub for AI,’ for $12.9B: Report2026-08-27NVIDIA DeveloperNVIDIA Contributes NVIDIA GB200 NVL72 Designs to Open Compute Project | NVIDIA Technical Blog2024-10-15