cloudflare /workerd
The JavaScript / Wasm runtime that powers Cloudflare Workers
★ 9,194⑂ 838👁 71⑃ 7,029● 1,115▤ 651
+3
Daily
9,194
stars
838
forks
71
watchers
7,029
prs
1,115
issues
651
releases
README
👷 workerd, Cloudflare's JavaScript/Wasm Runtime !Banner workerd (pronounced: "worker-dee") is a JavaScript / Wasm server runtime based on the same code that powers Cloudflare Workers. You might use it: As an application server, to self-host applications designed for Cloudflare Workers. As a development tool, to develop and test such code locally. As a programmable HTTP proxy (forward or reverse), to efficiently intercept, modify, and route network requests. Introduction Design Principles Server-first: Designed for servers, not CLIs nor GUIs. Standard-based: Built-in APIs are based on web platform standards, such as fetch(). Nanoservices: Split your application into components that are decoupled and independently-deployable like microservices, but with performance of a local function call. When one nanoservice calls another, the callee runs in the same thread and process. Homogeneous deployment: Instead of deploying different microservices to different machines in your cluster, deploy all your nanoservices to every machine in the cluster, making load balancing much easier. Capability bindings: workerd configuration uses capabilities instead of global namespaces to connect nanoservices to each other and external resources. The result is code that is more composable -- and immune to SSRF attacks. Always backwards compatible: Updating workerd to a newer version will never break your JavaScript code. workerd's version number is simply a date, corresponding to the maximum "compatibility date" supported by that version. You can always configure your worker to a past date, and workerd will emulate the API as it existed on that date. Read the blog post to learn more about these principles. WARNING: workerd is not a hardened sandbox workerd tries to isolate each Worker so that it can only access the resources it is configured to access. However, workerd on its own does not contain suitable defense-in-depth against the possibility of implementation bugs. When using workerd to run possibly-malicious code, you must run it inside an appropriate secure sandbox, such as a virtual machine. The Cloudflare Workers hosting service in particular uses many additional layers of defense-in-depth. With that said, if you discover a bug that allows malicious code to break out of workerd, please submit it to Cloudflare's bug bounty program for a reward. Getting Started Supported Platforms In theory, workerd should work on any POSIX system that is supported by V8 and Windows. In practice, workerd is tested on: Linux and macOS (x86-64 and arm64 architectures) Windows (x86-64 architecture) On other platforms, you may have to do tinkering to make things work. Building workerd To build workerd, you need: Bazel If you use Bazelisk (recommended), it will automatically download and use the right version of Bazel for building workerd. On Linux, nothing else: the build downloads its own LLVM toolchain (clang, lld and libc++) and a De
Top issues
#854Issue with nodejs_compat + dynamic require of node:events29 comments · 2023-05-02#2586🐛 BUG: (macOS dev beta) `ERR_RUNTIME_FAILURE` error when using `wrangler dev`26 comments · 2024-07-13#6624Python Workers: NoGilError race condition during concurrent request initialization (preparePython)24 comments · 2026-04-21#2735win32 arm64 Support24 comments · 2024-09-18#4587support napi20 comments · 2025-07-22#1346crypto: 100,000 iterations of PBKDF2 is insecure19 comments · 2023-10-25#959🐛 Bug Report — Runtime APIs: unused SQL cursors lead to strange errors18 comments · 2023-08-02#4035Uncaught TypeError: The "superCtor.prototype" property must be of type object on `wrangler pages dev`17 comments · 2025-04-06
Discussions
#8115Future of workerd vs celld0 comments · 2026-10-30#7704Third-party attribution sources for workerd 1.20261006.1 native releases1 comments · 2026-10-12#7681Python Workers Free: minimal responses sometimes exceed the published 10 ms CPU allowance1 comments · 2026-10-09#6917Feature Request: Native Chaos Testing and Fault Injection in workerd0 comments · 2026-08-06#6858[RFC 10008] Roadmap for HTTP QUERY support in Cache API0 comments · 2026-07-04#6846Test0 comments · 2026-06-28#6825Temporal API1 comments · 2026-06-17#6811Feature request: support WASM js-string-builtins proposal2 comments · 2026-06-13
Latest release
v1.20261115.1 v1.20261115.1 2026-11-15What's Changed Rust JSG: bound jsg_traced!( X) by HoldsNoGcReferences by @littledivy in https://github.com/cloudflare/workerd/pull/8401 Detach a Rust JSG resource's Rcs before its Drop runs by @littledivy in https://github.com/cloudflare/workerd/pull/8403 Full Changelog: https://github.com/cloudflare/workerd/compare/v1.20261114.1...v1.20261115.1