The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
On October 9, 2026, Deno announced that its entire team is joining Cloudflare. Ryan Dahl, the creator of both Node.js and Deno, will shift his focus to Cloudflare Workers, the open-source workerd runtime and self-hostable stateful applications. Deno will receive maintenance releases for one year, while Deno Deploy is scheduled to close after six months.
What Deno’s announcement means
This is a change in development direction, not an immediate deletion of the Deno project. Deno’s team is moving to Cloudflare, and official development of the Deno runtime will continue only through a planned one-year period of monthly bug-fix and security releases. After that maintenance window, Deno says it will stop its own runtime development. The code will remain open source, so other maintainers could continue the project.
Deno Deploy, the hosted service, has a shorter runway. Deno says it will continue operating for six months and then shut down. Paying customers are promised migration support for moving applications to Cloudflare Workers.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall| Project or service | Announced plan | What users should expect |
|---|---|---|
| Deno runtime | Monthly bug-fix and security releases for one year | Official Deno-led runtime development ends after that period; the repository remains open source |
| Deno Deploy | Continues for six months | Service shuts down afterward; paying customers receive migration assistance to Cloudflare Workers |
| Deno team | Joins Cloudflare | Future engineering effort moves to Workers infrastructure and open-source runtime work |
Why Ryan Dahl changed direction
Dahl’s explanation centers on compatibility. Deno began as a cleaner alternative to Node.js, with different defaults and a modern security model. But attracting users required increasing compatibility with the Node ecosystem. As Dahl told The Register, Deno had to “essentially backpedal on some of the original promises and become more Node compatible over time,” leaving it “as a kind of an alternative Node.js implementation.”
#1 Best Overall
That dynamic made maintaining a separate runtime less compelling. Dahl wrote that the team had decided to put its future work into a shared platform rather than continue developing “a separate runtime and hosting service.” His move therefore combines two decisions: stop pursuing Deno as an independent runtime-and-deployment stack, and apply the team’s experience to a broader distributed application platform.
The change also reflects Dahl’s continuing criticism of conventional server deployments. In comments quoted by The Register, he said that choosing Node.js for building servers was the wrong approach. The new work targets a different model: applications composed of short-lived compute, persistent objects and communication services that can run across a distributed network.
Rank #2
What Cloudflare is building with the former Deno team
Open-source workerd
Cloudflare describes workerd as the open-source runtime for its Workers programming model. The company says it is the same code used in production, rather than a separate compatibility implementation. Cloudflare originally open-sourced the runtime partly because customers wanted an escape hatch from a hosted service.
Cloudflare says Dahl and Bert Belder will lead an effort to make self-hosting workerd a first-class, supported way to build and run Workers applications. That wording describes a strategic and engineering commitment; it does not mean every Cloudflare-managed feature is already available as a turnkey self-hosted product.
Rank #3
Durable Objects and persistent state
Workers normally provide serverless JavaScript execution. Durable Objects add named, persistent objects that can coordinate state, handle requests sequentially where needed and maintain long-lived connections such as WebSockets. Together, those pieces target applications that need more than stateless request handlers, including collaborative sessions, real-time coordination and per-user or per-room state.
Where celld fits
celld is a Deno-originated open-source implementation that demonstrated how a self-hostable approach to Durable Objects could work. Cloudflare’s announced plan is to merge code and ideas from celld into workerd. The intended result is one open-source runtime and a clearer path for running Workers-style applications outside Cloudflare’s own network.
Rank #4
Can Cloudflare Workers be self-hosted?
Cloudflare’s answer is increasingly yes, but the practical status matters. The company is making self-hosted workerd a first-class use case and plans to incorporate celld’s work. That establishes the direction and the components involved. It does not establish that self-hosting currently provides feature parity with Cloudflare’s global service, identical operations, or the same managed integrations.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A self-hosted deployment would shift responsibility to the operator for infrastructure, upgrades, networking, observability, capacity and security. The benefit is control over where code and state run, along with an open-source runtime that can be inspected and adapted. The trade-off is that the operator no longer receives all of the convenience of Cloudflare’s managed edge automatically.
Best Value
What existing Deno users should do now
If you run the Deno runtime
- Continue using Deno during the announced maintenance period, while planning for a future in which Deno-led feature development stops.
- Track the monthly security and bug-fix releases and keep dependencies current.
- Document use of Deno-specific APIs, tooling and deployment assumptions so you can evaluate another runtime or a Workers-based migration later.
- Do not assume that open-source continuation will provide the same release cadence or governance after the official team steps away.
If you use Deno Deploy
- Inventory applications, domains, environment variables, data stores, scheduled jobs and WebSocket usage.
- Read Deno’s migration guidance when it becomes available and test the application on Cloudflare Workers before the six-month shutdown point.
- Pay particular attention to stateful components: a stateless request handler may migrate differently from an application relying on persistent sessions or Durable Objects-style coordination.
- Paying customers should use the migration support offered by Deno rather than waiting until the service is close to termination.
What this means for the JavaScript runtime landscape
The announcement narrows the number of actively developed, creator-led server-side JavaScript runtimes while strengthening the case for a Workers-compatible execution model. It also changes Deno’s governance story: the original team is no longer building an independent competing runtime, although the project itself remains available for community continuation.
For developers choosing among Node.js, Deno and Workers, the important distinctions are now deployment model, compatibility and migration effort, state and storage primitives, operational ownership, and who governs the project. This announcement supplies a clear change in deployment and governance; it does not provide a new benchmark showing that one runtime is faster than another.
Quick Recap
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.
