In June 2018, Ryan Dahl walked onto a stage at JSConf EU in Berlin and spent his talk listing the things he regretted about Node.js, the JavaScript runtime he had created nine years earlier. Near the end, he showed the room a small prototype that was meant to fix those mistakes. He called it Deno.
Eight years later, Deno as a standalone product is coming to an end. On October 9, 2026, Dahl announced that the entire Deno team is joining Cloudflare. The New Stack reported the deal as Cloudflare acquiring Dahl's startup. Neither company disclosed a price.
The news matters to anyone who builds for the web. Deno Deploy, the company's hosting service, will shut down in six months. The Deno runtime gets one more year of bug fixes and security updates, and then official development stops. Here is what happened, how Deno got here, and what founders and developers should take from it.
Deno is joining Cloudflare. Deno Deploy shuts down in about six months, the Deno runtime gets monthly fixes for one more year, and the JSR package registry keeps running on Cloudflare.
What Deno and Cloudflare Announced
The news came in two posts on the same day. On the Deno blog, Dahl wrote that "the entire Deno team is joining Cloudflare to take that work further." On the Cloudflare blog, he co-wrote a longer post with Kenton Varda, the engineer behind Cloudflare Workers, explaining the technical plan.
That plan centers on two pieces of software. The first is workerd, the open-source runtime that powers Cloudflare Workers, which Cloudflare released under the Apache 2.0 license in September 2022. The second is celld, a self-hostable version of Workers and Durable Objects that the Deno team released in August 2026. It is written in Rust, ships as a single binary and needs only object storage to run.
Dahl and his co-founder Bert Belder will now lead an effort to merge celld into workerd, so developers can run Cloudflare's programming model on their own servers. "We're joining Cloudflare to make the Workers programming model a mainstream way to build servers," Dahl wrote. Varda added that the self-hosted version will not be a copy: "This is not a parallel implementation, it's the same code we run in production."
What Happens to Deno's Products
"We know this is a consequential change for people who have built on Deno," he wrote. These are the commitments in his post:
- Deno runtime: monthly releases with bug fixes and security updates for one more year. After that, development ends. The code stays open source and others are welcome to carry it on.
- Deno Deploy: keeps running for six months, then shuts down. Paying customers get help moving to Cloudflare Workers. No exact shutdown date has been published.
- JSR: the TypeScript-first package registry keeps operating, with its infrastructure moving to Cloudflare.
- rusty_v8: support continues, with work toward integrating it into workerd.
The announcement made no specific commitment on Fresh, the Deno web framework, or Deno Sandbox, its newer product for running untrusted code from AI agents. If you rely on either, plan as though their future is open.
How Deno Got Here
Dahl built Node.js in 2009, and it became one of the most widely used tools in software. By 2018 he had a list of regrets: weak security, a messy module system and a heavy build process. Deno was his answer, with TypeScript support built in and no access to files, the network or environment variables unless the user grants it.
Deno 1.0 shipped on May 13, 2020. In March 2021, Dahl and Belder formed the Deno Company with a $4.9 million seed round from investors including Shasta Ventures, Rauch Capital, Long Journey Ventures and the Mozilla Corporation. In June 2022, Sequoia led a $21 million Series A, with Insight Partners, Netlify and Automattic among the backers. That brings Deno's disclosed funding to about $26 million.
The company then spent years fighting for adoption against a giant it had helped create. Deno 2, released on October 9, 2024, added backward compatibility with Node.js and npm, because developers would not leave their existing packages behind. Dahl's farewell post admits as much: "Compatibility with Node.js became an important part of that work too." As recently as June 2026, Deno 2.9 added native desktop apps. Four months later, the team chose a different path.
Deno by the Numbers
| Milestone | Date | Detail |
|---|---|---|
| Node.js regrets talk at JSConf EU | June 2018 | Deno first shown in Berlin |
| Deno 1.0 released | May 13, 2020 | First stable runtime |
| Deno Company seed round | March 29, 2021 | $4.9 million |
| Series A led by Sequoia | June 21, 2022 | $21 million |
| workerd open sourced by Cloudflare | September 27, 2022 | Apache 2.0 license |
| Deno 2 with Node and npm support | October 9, 2024 | Backward compatibility |
| Deno Deploy generally available | February 3, 2026 | Hosted platform |
| celld released | August 2026 | Self-hosted Workers and Durable Objects |
| Team joins Cloudflare | October 9, 2026 | Terms not disclosed |
| Deno Deploy shutdown | About April 2027 | Six months after the announcement |
| Runtime development ends | About October 2027 | After one year of fixes |
The 2027 dates are estimates based on the windows in Dahl's post. Neither company has named exact days.
Why This Matters
For Cloudflare, the deal brings in one of the best known teams in JavaScript at a time when its developer platform is a growing part of its pitch. It also helps answer a long-running criticism of Workers: that building on it locks you in. In the joint post, Varda rejected that idea and pointed out that some former customers have already moved off Cloudflare using the open-source workerd. A first-class self-hosted version makes that argument much stronger.
For developers, it is a reminder of how hard it is to build a new runtime. Node.js has had more than 15 years of packages, tutorials and hiring pipelines. Even with its creator in charge, a cleaner design and Sequoia money, Deno ended up spending much of its energy on matching Node. Bun, the other challenger, took a similar route: Anthropic acquired it in December 2025 to power Claude Code. Both of Node's best known rivals now live inside bigger companies.
It also fits a wider pattern in 2026. When Arena raised $200 million at a $3.1 billion valuation, investors were paying for the tools around AI models. The Deno deal shows the other side: a respected tool company deciding its best path forward is inside a bigger one.
Lessons for Founders
Founders building developer products, whether in San Francisco, London or Lagos, can take three lessons from Deno.
- Compatibility beats purity. Deno launched as a clean break from Node and later had to add Node and npm support to grow. If your users have years of work in an existing tool, meet them there from day one.
- Follow what your own product teaches you. Running Deno Deploy showed the team how much complexity sat under cloud hosting, and that lesson produced celld. The idea that got them a deal with Cloudflare came from operating their own service, not from the runtime they set out to build.
- Plan the wind down as carefully as the launch. Deno gave users a six month runway for Deploy, a year of security fixes for the runtime, migration help and a future for JSR. That is how you keep the trust of developers who bet on you.
What to Watch Next
Watch for three things. First, the exact Deno Deploy shutdown date and how smooth the move to Workers is for paying customers. Second, whether a community fork takes over the Deno runtime once official development ends. Third, the first release of a self-hosted workerd with celld inside, which Cloudflare says will come with more announcements in the coming months. If you run production apps on Deno Deploy, start your migration plan now rather than in March.
For more on how big platforms are reshaping startups this year, read our story on how Manus raised $500 million after China blocked its sale to Meta.
Frequently Asked Questions
Did Cloudflare acquire Deno?
The entire Deno team, including founders Ryan Dahl and Bert Belder, is joining Cloudflare, and The New Stack reported the deal as an acquisition. Both companies announced it on October 9, 2026. Financial terms were not disclosed.
When will Deno Deploy shut down?
Deno says Deno Deploy will keep operating for six months from the October 9, 2026 announcement and then shut down, which points to around April 2027. Paying customers will get migration support to Cloudflare Workers.
Is the Deno runtime dead?
Not yet. Deno will ship monthly bug fix and security releases for one more year. After that, official development ends, but the code remains open source and anyone can continue it.
What happens to JSR?
JSR, the JavaScript and TypeScript package registry created by the Deno team, will keep running. Its infrastructure is moving to Cloudflare.
