Cloudflare Acquires Deno to Make Workers Self-Hosting

On Friday, October 9, 2026, Cloudflare announced that it is acquiring Deno, the startup behind the Deno JavaScript and TypeScript runtime, and that the entire Deno team will join the company. The news came in a joint post by Ryan Dahl, a Deno co-founder and the creator of Node.js, and Kenton Varda, Cloudflare's principal engineer for Workers, published on the Cloudflare blog. Dahl wrote a matching note on the Deno blog. Financial terms were not disclosed.

Related reading: Jellyfin 12.0 drops the 10 prefix, rewrites the library and gets a new look · Microsoft's Project Zenith Wants Windows to Be Ready-to-Code. Developers Aren't Convinced.

The move puts one of the best-known independent runtimes inside the platform it spent years competing with. Deno launched as a rewrite of the ideas behind Node.js: secure by default, with TypeScript built in and a standard library shipping out of the box. Cloudflare Workers runs JavaScript on the company's edge network rather than on a server the developer owns. The people who built the alternative will now work on Cloudflare's runtime. TechCrunch reported the acquisition as a bid to improve the Workers programming model.

Deno had raised $26 million in total, including a Series A led by Sequoia, according to TechCrunch's 2022 coverage. It was a small company by cloud standards, and it never turned its developer goodwill into a large hosting business. Its hosted product, Deno Deploy, competed directly with Workers and with other edge platforms.

What happens to the runtime and its hosting service

The runtime survives, with a clock on it. Cloudflare said it will keep the Deno runtime maintained with roughly 12 months of bug fixes and security patches, then end its own development of it. That does not close the code. The project stays open source, and anyone can keep building on it after Cloudflare stops. But a maintained branch with a known end date is a different thing from an actively developed one. Teams that have shipped on Deno now have a reason to plan an exit, or to maintain a fork themselves.

Deno Deploy, the hosted service, will shut down. Cloudflare's post describes the team's focus moving to Workers without pinning a date, and third-party reporting puts the wind-down at about six months, which would land near April 2027. Either way, the commercial side of Deno is ending while the open-source side continues.

That split is the crux of the deal. Cloudflare is not buying a hosting business to run alongside its own. It is buying a team and folding its work into Workers, and it is being explicit that the standalone products had reached their limit.

Why Cloudflare says it made the deal

Varda framed the acquisition as an answer to the problem of lock-in. He wrote that there is "a popular theory" that Cloudflare "made Cloudflare Workers work differently from other cloud platforms in order to create 'lock-in'," and argued the opposite: "being open source and giving people an escape hatch is good business." His argument is that letting customers leave is part of what makes them willing to stay.

That argument only works if there is somewhere to go. The catalyst was celld, an open-source implementation that runs Workers applications, including Durable Objects, on a developer's own machines. It ships as a single Rust binary under the Apache-2.0 license. Varda said the Cloudflare team was delighted when Deno released it in August: "when the Deno team released celld in August, we were delighted."

Durable Objects are the stateful part of the Workers platform, and according to The New Stack, workerd's support for them had been limited to a single instance. That was enough for local testing but not for scaled self-hosting, and closing that gap is what celld was built to do.

Why self-hosting is the real subject

Self-hosting is the term Cloudflare keeps returning to, and it is the part of the announcement with the longest consequences. Workers is a managed service: developers upload code and Cloudflare runs it, which is what makes the platform convenient and also what makes leaving it expensive. Running the same code elsewhere has meant rewriting it, because Workers differs from other serverless platforms in ways that reach into how applications are structured. celld showed that the difference is not fundamental. It runs Workers applications, Durable Objects included, on hardware the developer controls, which is the evidence Cloudflare needed that its runtime can travel.

That evidence matters to Cloudflare because lock-in is a standing criticism of edge platforms, and it matters to developers because the choice between convenience and portability is usually one they have to make early, before they know how the project will grow. If workerd becomes self-hostable as a supported feature, the same code can run in a small deployment and on Cloudflare's network, and the decision to use Workers starts to look reversible.

What it means for Deno users

For anyone running Deno today, the announcement sets a schedule rather than an ending. The runtime keeps receiving security patches for about a year, which covers the immediate risk of a known vulnerability going unfixed. What it does not cover is everything else that makes a runtime worth choosing: new APIs, performance work, and the steady stream of fixes that keep a language runtime usable against a changing ecosystem.

Deno's design softens the landing. The project shipped with a standard library and a set of web-standard APIs, so projects built on it are not locked into a proprietary framework. Much of that code runs on other runtimes already, and Deno Deploy users can move to Workers or to another edge host. The migration is work rather than a rewrite from scratch, which is the difference between an inconvenience and a crisis.

An open-source runtime under one vendor

Varda's plan is specific. Dahl and Deno co-founder Bert Belder will lead a new effort to make workerd, Cloudflare's open-source Workers runtime, a first-class, supported way to build and run Workers applications. The work will merge code and ideas from celld back into workerd. From a developer's point of view, that is the substance of the deal: the escape hatch moves from a third-party experiment into the mainline runtime.

Dahl put the ambition plainly. "We're joining Cloudflare to make the Workers programming model a mainstream way to build servers," he wrote.

"We're joining Cloudflare to make the Workers programming model a mainstream way to build servers." — Ryan Dahl, Deno co-founder

The open-source promise carries weight in Cloudflare's framing, so it helps to be precise about what it covers. workerd is already open source, and Cloudflare says the merged self-hosting path will be too. But running Cloudflare's platform on your own hardware is not the same as an independent platform. It reduces the risk of being stranded; it does not restore Deno as a competitor.

A pattern of buying developer tools

Deno is the third developer-tooling acquisition Cloudflare has announced in 2026, The New Stack noted. In January it bought Astro, the web framework. In June it bought VoidZero, the team behind Vite, Vitest, Rolldown and Oxc. In October it bought Deno. The three share a shape: small teams with outsized influence over how JavaScript developers build, absorbed into a company that wants that audience on its platform.

That pattern is why the Deno deal reads as strategy rather than rescue. Cloudflare's core business is selling a network, and Workers is how it sells compute on that network. Owning the toolchain developers reach for first gives Cloudflare a say in the defaults. Astro, Vite and now Deno all sit early in a project's life, which is when choices get made and habits form. Buying the maintainers is a cheaper path to that influence than trying to displace them.

Not every developer will read the deal that way. The runtime Deno users picked is now controlled by Cloudflare, and Cloudflare will decide what the next version looks like. Open source settles the licensing question, not the governance one: who sets the roadmap, whose fixes land, and which behavior counts as a bug.

Caveats

Some parts of the story are firm and some are not. The acquisition itself, the team move, the roughly 12-month maintenance window, and the open-source status of the runtime all come from Cloudflare's own post. The precise end dates, including for the Deno Deploy shutdown, come from third-party reporting rather than from Cloudflare, which describes the direction without committing to every date.

The price is unknown, so it is impossible to judge whether Deno's investors, Sequoia among them, made money on the sale. The self-hosting work is described as a coming effort, not a shipped feature. Cloudflare said it will have more to announce in the coming months, which is a promise with no date attached.

There is also a gap between the runtime's fate and its users' needs. Twelve months of patches keeps existing Deno applications running in the near term. It does not fund new features, and it does not answer what happens to the bugs and security issues that surface after the window closes. A community fork is possible, but whether anyone pays for it is a separate question from whether anyone wants it.

What to watch

The clearest signal will be when, and whether, workerd becomes self-hosting as a supported path. If Cloudflare ships that, the celld line of work becomes a real escape hatch and the anti-lock-in argument has something behind it. If the effort stays internal or slips, the acquisition will look more like a talent buy with an open-source gloss.

The second signal is the runtime's last year. Watch how much maintenance the project actually gets, and whether the community organizes a successor before the window runs out. The third is what Cloudflare buys next. Three developer-tool acquisitions in one year is a direction, and the next announcement will show whether Deno was the end of the sequence or another step in it.

For now, the clearest fact is the one Cloudflare stated first: the Deno team is joining the company that built the runtime Deno was meant to improve.

Feature image: HaeB, Wikimedia Commons, CC BY-SA 4.0.