workerd review
A self-hosted runtime for Cloudflare Workers applications, not a managed edge-functions service.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
workerd is Cloudflare's open-source JavaScript and WebAssembly server runtime, based on the technology powering Cloudflare Workers. It is designed for teams that want to self-host applications built for the Cloudflare Workers model, develop and test Workers locally, or run programmable forward and reverse HTTP proxy workloads. Builds and prebuilt binaries support Windows, macOS, and Linux, while fetch-based web platform APIs give applications a familiar interface for request processing and responses.
Its strongest fit is for teams assembling a Cloudflare-compatible runtime around their own infrastructure. workerd supports standard WHATWG ReadableStream and WritableStream APIs, response streaming, scheduled Worker handlers, HTTP socket serving, and Cap'n Proto text configuration. Wrangler and Miniflare extend the local development path, while npm and npx binaries provide another deployment route. For production, systemd support offers an operating model for services managed directly on a host rather than through a hosted edge-functions control plane.
The trade-off is that workerd is infrastructure, not a managed service. Teams choosing it take responsibility for runtime deployment and operation, including the selected build or binary workflow, configuration, proxy setup, and production service management. The published product details do not describe hosted pricing or an included request quota, so it is better suited to engineers who specifically need self-hosting and control over the runtime environment. Choose workerd for Cloudflare Workers compatibility, local development, streaming, scheduled execution, and programmable HTTP behavior; choose a managed edge-functions service instead if hosted operations are the priority.
workerd pros and cons
- Where it wins
- Runs JavaScript and WebAssembly with fetch-based web APIs
- Supports streaming, scheduled handlers, and HTTP socket serving
- Works with Wrangler, Miniflare, npm, and systemd
- Where it doesn't
- Requires self-hosting rather than a managed edge deployment
- Configuration uses Cap'n Proto text files
- Production operation centers on systemd and technical deployment workflows
workerd fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update