Ryan Dahl, the creator of Node.js, is joining Cloudflare along with the entire Deno company. The announcement landed on October 9, 2026, and sent Cloudflare shares (NYSE: NET) up 6% in the afternoon session. Deno, the JavaScript/TypeScript runtime Dahl built as a modern alternative to Node, will see its official development wind down.
That is the short version of a deal that reshapes the serverless JavaScript landscape. The team that spent years competing with Cloudflare’s Workers platform is now working inside it. Sources describe the move as an acquisition of the startup behind Celld, a self-hosted take on Workers.
TL;DR: Cloudflare has hired the entire Deno team, including Node.js creator Ryan Dahl, to simplify self-hosting Workers and Durable Objects. Deno Deploy shuts down in six months, while official runtime development winds down after one year of fixes. Cloudflare stock (NYSE: NET) jumped 6% on the announcement (FinancialContent, Oct 9, 2026).
What Exactly Did Cloudflare Announce About Deno?
Cloudflare announced that the Deno team is joining the company, according to the official Cloudflare blog. The stated goal is to radically simplify self-hosting Workers and Durable Objects, so developers can use the same primitives in more places. This is not just a talent hire. It is the absorption of an entire company built around a competing runtime.
The announcement came with clear timelines. Deno Deploy will close in six months, with migration support toward Workers. Official runtime development gets one year of fixes before winding down, after which the runtime shifts to community-maintained open source, as reported by DEV Community and AlternativeTo.
Cloudflare’s own announcement framed the deal around its Workers programming model. The company wants the primitives behind Workers and Durable Objects to run beyond Cloudflare’s own cloud. Dahl himself echoed this in his announcement post, writing that he is motivated by abstractions that give leverage at scale and calling the Workers model a hermetic computing abstraction that embodies Sun Microsystems’ old tagline, “The Network Is the Computer.”
Markets reacted immediately. Shares of Cloudflare jumped 6% in the afternoon session after the announcement, according to FinancialContent’s market coverage. Investors apparently read the deal as a strengthening of the Workers platform rather than a defensive purchase.
Why Is Cloudflare Bringing the Deno Team On Board?
The core reason is self-hosting. Cloudflare’s blog states the team is joining to radically simplify self-hosting of Workers and Durable Objects, extending the same programming primitives to more places. Today, running a Worker outside Cloudflare’s infrastructure is not a simple task. The company wants to change that.
The New Stack adds important context: Deno built Celld, described as a self-hosted take on Cloudflare Workers. In other words, the Deno company had already been working on the exact problem Cloudflare now wants solved. Absorbing the team brings that expertise in-house rather than leaving it with a competitor.
There is an irony here that coverage did not miss. The New Stack’s headline calls Deno a startup that “copied” Cloudflare’s serverless playbook. Now Cloudflare is buying the copyist. The deal turns a parallel effort into an internal project.
Why does this matter to developers? Consider the current situation:
- Workers code runs natively on Cloudflare’s edge network
- Durable Objects provide stateful coordination for those workloads
- Self-hosting these primitives has required workarounds and custom setups
- The Deno company built Celld to address self-hosted execution
- Dahl publicly endorses the Workers model as a scalable abstraction
- The combined teams will work on making these primitives portable
Technobezz reports that Ryan Dahl and Bert Belder will lead work improving self-hosting for apps built on Workers. Leadership continuity from Deno’s founders suggests this is a technical mission, not an acqui-hire aimed at quietly shelving the technology.
Who Is Ryan Dahl and Why Does His Move Matter?
Ryan Dahl created Node.js. That single fact explains most of the attention this deal has received. Node.js remains one of the foundational technologies of modern web development, and Dahl’s later project, Deno, was born as a modern and more secure alternative to Node, as the announcement coverage put it.
Dahl confirmed the move himself. “I, along with the rest of the Deno company, am joining Cloudflare!” he wrote in his announcement post. He explained his motivation: abstractions that give leverage at scale. He described the Cloudflare Workers programming model as a hermetic computing abstraction that truly embodies the old Sun Microsystems tagline “The Network Is the Computer.”
That endorsement carries weight. The creator of Node.js, who once walked away from that ecosystem, is now betting on Cloudflare’s model. When the person who defined server-side JavaScript praises a platform’s computing abstraction, developers pay attention.
Dahl is not alone. Bert Belder, his longtime collaborator, is also joining, with both leading the self-hosting work according to Technobezz. The official Deno account announced the news with enthusiasm: “We are excited to announce that Deno is joining Cloudflare!”
His move matters for a second reason: the fate of Deno as a runtime. The creator is leaving the project he founded. Official development continues for only one more year of fixes. The community will inherit the codebase afterward. For teams that chose Deno because of Dahl’s involvement, his departure is a signal worth weighing carefully.
What Happens to Deno Deploy and the Deno Runtime?
Both get explicit end dates. Deno Deploy, the hosting platform, will close in six months. AlternativeTo and byteiota both report that migration support toward Workers will be available during that window. Developers running production workloads on Deploy have half a year to move.
The Deno runtime itself follows a slower path. Official development will cease after one year, during which the runtime receives fixes. After that period, the project shifts to community-maintained open source, according to DEV Community’s coverage. The code does not disappear. Active stewardship by the original team does.
Here is what the timeline looks like:
| Milestone | Timeline | Detail |
|---|---|---|
| Team joins Cloudflare | Announced October 9, 2026 | Entire Deno company hired |
| Deno Deploy closure | 6 months | Migration support toward Workers provided |
| Runtime fixes end | 12 months | One year of official fixes |
| Runtime afterward | Ongoing | Community-maintained open source |
| Stock reaction | Same day | NET up 6% in afternoon session |
For developers, the practical question is which path to take. byteiota framed it bluntly: Deno Deploy shuts in six months, the runtime ends in twelve, and developers need to act now. Options include migrating Deploy workloads to Workers, continuing on the runtime and accepting community maintenance, or moving to another runtime entirely.
Teams using Deno outside of Deploy face a softer decision. The runtime keeps working and receives fixes for a full year. Community-maintained open source projects survive in many forms. But the departure of the founding team and the one-year fix window together suggest planning a transition rather than assuming business as usual.
What Is Celld and How Does It Fit Into the Deal?
Celld is the connective tissue of this acquisition. According to The New Stack, Ryan Dahl’s Deno built Celld, a self-hosted take on Cloudflare Workers. The project aimed to let developers run Worker-style code on their own infrastructure instead of relying on Cloudflare’s cloud.
That mission is precisely what Cloudflare now wants to advance internally. The company’s blog announcement says the team is joining to radically simplify self-hosting Workers and Durable Objects so the same primitives work in more places. Celld represents prior art in exactly that direction, built by the people who designed the runtime underneath it.
The fit becomes clearer when you look at what each side brings:
- Cloudflare brings the Workers and Durable Objects programming model
- The Deno team brings runtime engineering experience from building Deno
- Celld demonstrates self-hosted execution of Worker-style workloads
- Dahl brings the design philosophy behind Node.js and Deno
- Belder brings systems engineering leadership, now directing self-hosting work
- Combined, the teams aim to make Workers primitives portable beyond Cloudflare’s edge
The New Stack’s framing captures the reversal: the startup that copied Cloudflare’s serverless playbook is being absorbed, and its own runtime is winding down. Celld’s approach, validated by its creators joining the original platform, now informs how Cloudflare plans to open its model to self-hosters.
For developers watching this deal, Celld is the reason to be optimistic. This is not a team hired for résumés and then disbanded. It is a team whose self-hosting product maps directly onto Cloudflare’s stated goal. The work has a clear destination: Workers and Durable Objects that run in more places than Cloudflare’s own network.
How Did Developers and the Market React?
The reaction split into two channels: financial markets cheered, while developer communities started planning migrations. Cloudflare (NYSE: NET) shares jumped 6% in the afternoon session after the company announced that the Deno team had joined its platform to simplify self-hosting Workers and Durable Objects (FinancialContent, October 9, 2026). Investors clearly read the move as a win for the Workers ecosystem.
Among developers, the tone was more mixed. Ryan Dahl announced the move on X, writing that he is motivated by abstractions that give leverage at scale and describing the Cloudflare Workers programming model as a hermetic computing abstraction that embodies Sun Microsystems’ old tagline, “The Network Is the Computer.” The official Deno account confirmed the news the same day.
The mixed feelings make sense. On one side, some of the most experienced runtime engineers in the JavaScript world now work on open self-hosting primitives. On the other, an independent runtime that many teams rely on just got a hard deadline. Coverage from byteiota framed it bluntly: Deploy shuts in six months, runtime development ends in twelve.
So who actually wins here? Short-term, Cloudflare. Medium-term, developers who want Workers-style primitives outside Cloudflare’s cloud. The losers are teams betting on Deno as an independent platform.
What Should Deno Developers Do Now?
The deadline situation dictates priorities. Deno Deploy will close in six months, with migration support to Cloudflare Workers offered to developers (AlternativeTo). If an application runs on Deploy today, that is the tightest clock in the entire transition, and planning should start immediately.
A practical order of operations:
- Audit which workloads run on Deno Deploy versus self-hosted Deno.
- For Deploy workloads, review the Workers migration support Cloudflare is offering and estimate porting effort.
- For self-hosted Deno, identify runtime-specific APIs your code depends on.
- Track the one-year window of official runtime fixes and avoid building new projects against APIs scheduled to change.
- Watch the Cloudflare blog for updates on self-hosting Workers and Durable Objects, since that is where the team’s future work lands.
- Evaluate whether Workers primitives can replace Deno-specific tooling in your stack.
- For long-lived internal tools, budget time for a runtime decision before the official support window closes.
After the year of fixes ends, active development shifts to a community-maintained open source model (DEV Community). That means security patches and new features depend on volunteer maintainer capacity rather than a funded company team. In my opinion, any production dependency on community-maintained infrastructure deserves a documented exit plan.
The good news: migration support exists for the platform closing soonest. The harder question is what happens to the runtime itself once company-backed development stops.
Does This Change the JavaScript Runtime Landscape?
Yes, in a structural way. Deno was created by Ryan Dahl, the creator of Node.js, as a JavaScript/TypeScript runtime positioned as a modern alternative (KuCoin news). With the entire Deno company absorbed into Cloudflare, the runtime stops competing as an independent platform and its team starts building toward a different goal: radically simplifying self-hosting of Workers and Durable Objects so developers can use the same primitives in more places (Cloudflare blog).
The New Stack described the irony directly: Ryan Dahl’s Deno built Celld, a self-hosted take on Cloudflare Workers, and now Cloudflare is absorbing the team while Deno’s own runtime is wound down. The serverless playbook Deno copied is now the playbook its creators will extend.
What does the map look like after this? Consider the shifts:
- One independent, company-backed JavaScript runtime disappears from the field.
- The Workers programming model gains the engineers who built Node.js and Deno.
- Self-hosted serverless becomes a first-class Cloudflare engineering goal rather than a community afterthought.
- Community-maintained Deno continues as an open source project, dependent on contributor capacity.
- The distinction between “Cloudflare-only” and “portable” serverless narrows as the same primitives are pushed to more environments.
For developers, the practical consequence is convergence. The abstractions Dahl praised — hermetic computing, network-distributed computation — were the shared DNA between Deno’s ambitions and Workers all along. Now the people and the platform are in the same building.
What Does Self-Hosting Workers and Durable Objects Actually Mean?
Per Cloudflare’s own blog post, the Deno team is joining “to radically simplify self-hosting Workers and Durable Objects, so developers can use the same primitives in more places.” That sentence is the entire thesis of the acquisition, and each part matters.
Workers are Cloudflare’s functions-as-a-service primitives. Durable Objects provide stateful building blocks for applications built on Workers. Today, developers who want those programming models generally run them inside Cloudflare’s infrastructure. Self-hosting means running the same model on your own infrastructure instead — your servers, your network, your constraints.
Why does that need a dedicated team? Because making a cloud-native programming model portable is genuinely hard work. It requires packaging the runtime, the state layer, and the deployment story so that a developer gets comparable behavior outside the original cloud. This is exactly what Deno’s Celld project explored: The New Stack describes it as a self-hosted take on Cloudflare Workers, built before the acquisition.
Dahl’s own framing on X adds context. He called the Workers programming model a “hermetic computing abstraction” and invoked the old Sun Microsystems line, “The Network Is the Computer.” In that view, where the code physically runs matters less than the consistency of the abstraction. Self-hosting extends the reach of the abstraction rather than diluting it.
For developers, the promised end state is simple to state: write against Workers and Durable Objects once, run them in more places. Whether the execution matches the ambition will only become clear as the team ships.
Is This the End of Deno as an Independent Project?
For company-backed development, yes — on a published timeline. DEV Community’s coverage states that Cloudflare is ending active Deno development and shifting the project to community-maintained open source. AlternativeTo and byteiota both report the runtime receives one year of fixes after the team joins, while Deno Deploy closes in six months.
The full sequence, as reported:
- The entire Deno company joins Cloudflare, including Ryan Dahl and Bert Belder (KuCoin, Technobezz).
- Deno Deploy shuts down in six months, with Workers migration support for hosted apps.
- The Deno runtime receives one year of official fixes.
- After that year, official development ceases and the project continues as community-maintained open source.
- The team’s engineering effort moves to self-hosting Workers and Durable Objects at Cloudflare.
Does “community-maintained” mean Deno vanishes? No. The code remains open source, and the DEV Community headline explicitly frames the outcome as a shift to community maintenance rather than deletion. But there is a real difference between a runtime with a funded team and one sustained by volunteers, and teams with production dependencies should plan accordingly.
There is also a historical symmetry worth acknowledging. Dahl created Node.js, then created Deno as a modernized alternative. Now the Deno chapter as an independent company closes, and its creator moves to extending the Workers model he publicly praised. Endings in software are rarely total; they are usually transitions of people and ideas. This one is unusually well documented, with dates attached.
Frequently Asked Questions
How long will the Deno runtime receive official updates?
According to AlternativeTo and byteiota coverage, the Deno runtime gets one year of fixes after the team joins Cloudflare, after which official development ceases. Cloudflare’s own blog confirms the team is joining to simplify self-hosting Workers and Durable Objects, not to continue the standalone runtime.
What happens to Deno Deploy?
Coverage from AlternativeTo and byteiota states that Deno Deploy will close in six months, with Workers migration support offered to developers. Developers hosting on Deploy therefore face the tightest deadline in the transition and should begin migration planning first.
Who is joining Cloudflare from the Deno company?
The entire Deno team is joining Cloudflare, including creator Ryan Dahl and Bert Belder, per KuCoin news and Technobezz. Dahl announced the move on X, citing motivation from abstractions that give leverage at scale and calling the Workers programming model a hermetic computing abstraction.
Why did Cloudflare stock move on the announcement?
FinancialContent reported that Cloudflare (NYSE: NET) shares jumped 6% in the afternoon session after the company announced the Deno team joined its platform to simplify self-hosting. The market reacted positively to the acquisition news.
Summary
The Deno acquisition is a rare case where every major fact comes with a date attached. Here are the takeaways:
- The entire Deno team, including Ryan Dahl and Bert Belder, has joined Cloudflare to radically simplify self-hosting Workers and Durable Objects.
- Deno Deploy closes in six months, with migration support to Workers offered; the runtime gets one year of official fixes before shifting to community-maintained open source.
- Cloudflare stock (NYSE: NET) rose 6% in the afternoon session on the announcement.
- Deno’s Celld project was already a self-hosted take on Workers, making the team a natural fit for Cloudflare’s new direction.
If you run workloads on Deno Deploy, start your migration review now — it has the shortest deadline. And if you have been waiting for a portable version of the Workers model, watch the Cloudflare blog: that is exactly what this team was hired to build.
What do you think — is community maintenance enough for a runtime this widely used? Share your take in the comments.