On October 9, 2026, Deno announced that its entire team is joining Cloudflare. Ryan Dahl, who created both Node.js and Deno, will shift his focus to Cloudflare’s Workers platform and open-source runtime work. Deno is not disappearing immediately: its runtime will receive monthly bug-fix and security releases for one year, while Deno Deploy is scheduled to operate for six more months before shutting down.
What happens to Deno now?
Deno’s own runtime development will end after a one-year maintenance period. During that year, the project says it will continue monthly bug-fix and security releases. Afterward, Deno remains open source, so other maintainers could continue development, but the original Deno team will no longer be responsible for building the runtime.
As an Amazon Associate I earn from qualifying purchases.
Deno Deploy, the company’s hosted service, has a shorter timeline. It is scheduled to continue for six months and then shut down. Paying customers are expected to receive migration support for moving applications to Cloudflare Workers.
| Component | Announced plan | What it means |
|---|---|---|
| Deno runtime | Monthly bug-fix and security releases for one year | Official development then ends; the code remains open source |
| Deno Deploy | Continues for six months | Service shutdown follows, with migration help for paying customers |
| Deno team | Joins Cloudflare | Future work moves to Workers infrastructure and open-source runtime projects |
Why Ryan Dahl is leaving Deno’s separate-runtime strategy
Deno was created as an alternative to Node.js, with different defaults and a modern JavaScript and TypeScript experience. Dahl now says that attracting users required Deno to become increasingly compatible with Node.js. In an explanation quoted by The Register, he said the project had to “backpedal on some of the original promises and become more Node compatible over time,” leaving Deno as “a kind of an alternative Node.js implementation.”
#1 Best Overall
That compatibility pressure changed the trade-off behind maintaining a separate runtime. Instead of continuing to develop both an independent runtime and an independent hosting service, Dahl says the team will put its future work into a shared platform that combines compute, storage and communication.
The move also reflects Dahl’s broader view of server development. In comments quoted by The Register, he said that choosing Node.js for building servers is the wrong choice. That statement is an opinion, not a benchmark result, and the announcement does not provide a new performance comparison among Node.js, Deno and Workers.
What Cloudflare is building with the former Deno team
Workerd as a supported self-hosting runtime
Cloudflare says Dahl and Bert Belder will lead an effort to make workerd a first-class, supported way to build and run applications using the Workers programming model. Workerd is Cloudflare’s open-source Workers runtime, and Cloudflare says it is the same runtime code used in production.
Cloudflare says it open-sourced workerd partly because customers wanted an escape hatch from a hosted service. That distinction matters: open-source code alone does not automatically make a platform easy to operate, but the announced goal is to provide a supported self-hosting path rather than limiting the Workers programming model to Cloudflare’s network.
Durable Objects and persistent state
The technical focus includes Workers together with Durable Objects. Workers supplies serverless JavaScript execution, while Durable Objects provide addressable, persistent state and coordination. The model can support applications that need WebSockets, consistent state for a given object and communication between connected clients.
Deno’s celld project demonstrated an open-source, self-hostable approach to Durable Objects. Cloudflare plans to merge code and ideas from celld into workerd. The stated objective is a more complete self-hosted implementation of the Workers model, including its stateful components, rather than a runtime that only executes isolated request handlers.
Can Cloudflare Workers be self-hosted?
Cloudflare’s announced direction is yes, with an important qualification: self-hosting is being made a first-class supported use case, not presented as a finished, universally available product today. Workerd already exists as open-source runtime code, and Cloudflare says the production service uses that same code. The next phase is to combine workerd with the former Deno team’s work on celld and improve the operational path for running Workers-style applications outside Cloudflare’s hosted network.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Today’s foundation: workerd is open source and is described by Cloudflare as the production Workers runtime.
- Planned expansion: celld’s implementation and ideas are to be merged into workerd.
- Target use case: organizations should be able to run the Workers programming model, including stateful Durable Objects, under their own operational control.
- Evidence limit: the announcement does not specify a final release date, supported operating systems, production service-level commitments or a complete feature-parity matrix for self-hosted deployments.
What developers using Deno should do
If you run Deno locally or self-host your own servers
There is no immediate requirement to abandon Deno. The runtime is scheduled to receive monthly bug-fix and security releases for one year, and its source remains available afterward. Teams should nevertheless identify dependencies on Deno-specific APIs, tooling and release ownership, then decide whether to stay with community maintenance or plan a migration.
If you use Deno Deploy
Deno Deploy users face a fixed service deadline: the hosted platform is scheduled to shut down after six months. Paying customers are expected to receive migration support to Cloudflare Workers. Before migrating, inventory domains, environment variables, secrets, scheduled jobs, storage, WebSocket behavior and any deployment-specific APIs. A basic source-code port may not cover differences in state management or platform bindings.
If you are evaluating Workers for a new application
The announcement makes Workers more relevant to teams that want edge-style serverless execution but also require a path to run the runtime themselves. The practical decision is whether to use Cloudflare’s managed network now, wait for the self-hosting work to mature, or select another runtime whose operational model already matches your requirements.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What this means for the JavaScript runtime landscape
Deno’s original team is not simply moving from one hosted service to another. The change shifts engineering effort from maintaining a separate Node-compatible runtime toward an open-source implementation of Cloudflare’s distributed application model. That model combines execution with persistent state and communication primitives, especially through Durable Objects.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →For developers, the key governance change is that Deno’s future is no longer directed by its founding team. The project can continue as open source, but its roadmap, release cadence after the one-year maintenance window and compatibility priorities will depend on whoever takes over. Cloudflare, meanwhile, is positioning workerd as both the runtime behind its hosted Workers service and the basis for supported self-hosted deployments.
Quick Recap
Key dates and decisions
- October 9, 2026: Deno announces that its team is joining Cloudflare.
- For the next year: Deno plans monthly bug-fix and security releases for the runtime.
- After that maintenance year: official Deno runtime development ends, although the source remains open.
- For the next six months: Deno Deploy continues operating.
- After six months: Deno Deploy is scheduled to shut down; paying customers are offered migration support to Cloudflare Workers.
- Following the transition: Cloudflare plans to merge celld work into workerd and make self-hosting Workers and Durable Objects a first-class supported scenario.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
