Deno is joining Cloudflare, and Deno Deploy users now have six months to move

The entire Deno team is joining Cloudflare, and the announcement comes with two clocks attached. Deno Deploy, the company’s hosting platform, will shut down in six months. The Deno runtime itself gets one more year of maintenance releases, after which the Deno company stops developing it. For anyone who picked Deno as a deliberate alternative to Node.js, this is less a merger story than a migration notice.

What was announced

In a post on the Deno blog on October 9, Ryan Dahl wrote that the team will put its “future development work into this shared platform rather than continuing to develop a separate runtime and hosting service.” The concrete commitments are short:

• The Deno runtime receives monthly releases with bug fixes and security updates for one more year. After that, Deno’s own development ends. The runtime stays open source, and Dahl told The New Stack it remains MIT-licensed.
• Deno Deploy keeps running for six months, then shuts down. Paying customers get migration support for moving to Cloudflare Workers.
• JSR, the TypeScript-first package registry, keeps operating, with its infrastructure moving to Cloudflare.
• The team continues supporting rusty_v8, the Rust bindings to V8, and plans to integrate it into workerd, Cloudflare’s open-source Workers runtime.

Financial terms were not disclosed. Neither post says what happens to Fresh, Deno Subhosting, or Deno Sandbox, so teams on those products should wait for explicit guidance rather than infer it.

Why Cloudflare wanted the team

The strategic center of the deal is celld, an open-source project Deno released in August that recreates the Workers and Durable Objects programming model for self-hosted infrastructure. Cloudflare’s joint post says Dahl and co-founder Bert Belder will lead an effort to merge celld into workerd and make self-hosting “a first-class supported way to build and run apps using the Workers programming model.”

Kenton Varda, the Cloudflare engineer behind Workers, was unusually candid about why. “The Deno team understands how to create a good developer experience around a self-hosted runtime, something we never quite cracked with Workerd,” he wrote. Speaking to The New Stack, he framed portability as a commercial interest rather than generosity: a model exclusive to Cloudflare narrows the market, so making it run well elsewhere helps Cloudflare compete with the larger clouds. Dahl said a fleet of the combined runtime should need only a standard object storage bucket for coordination and storage, and that it is expected to stay open source, likely under Apache 2.0.

Cloudflare appears to be betting that the Workers API becomes more valuable as a portable standard than as a feature of one network. That is a credible bet, but it is still a plan: no shipping date was given beyond “more announcements” in the coming months.

What it means for Deno Deploy users

This is the group with a hard deadline. Six months from an October 9 announcement lands around April 2027, and neither post gives an exact shutdown date or describes how non-paying projects will be handled. The supported exit is Cloudflare Workers. Code written against web-standard APIs such as fetch, Request, and Response should move with modest changes. Code that leans on Deno-specific APIs, Deno KV, or Deno Deploy’s platform features is a rewrite candidate and should be inventoried now rather than in March. Frameworks that already target both runtimes, such as Hono, reduce that work.

What it means for teams on the runtime

The one-year maintenance window gives teams time, but it ends with no committed owner. Dahl told The New Stack that “anyone is welcome to carry it forward” and pointed to io.js as a precedent for a community-led continuation. Until a credible fork or foundation appears, new projects choosing Deno are choosing a runtime with an announced end of upstream development.

The less obvious exposure sits one layer down. Supabase Edge Functions run on a Deno-compatible runtime, and Netlify’s documentation describes its Edge Functions as running in a secure runtime based on Deno. Neither company addressed the change in the announcements reviewed here. Teams with significant code in either platform’s edge functions should watch for runtime roadmap statements from those vendors rather than assume either an immediate change or indefinite continuity.

The runtime field narrows

The New Stack notes that this follows Anthropic’s acquisition of Bun in December 2025, with a key difference: Anthropic committed to continuing Bun as an open-source runtime, while Deno’s standalone runtime is being wound down. The JavaScript server landscape is consolidating toward Node.js on one side and platform-owned runtimes on the other. Dahl argues that Deno’s ideas, from built-in TypeScript to permission controls to web-standard APIs, have already shaped Node. Its own runtime may not outlast them.

The signals to watch over the next quarter are an exact Deno Deploy shutdown date, guidance on Fresh and Deno KV, statements from Supabase and Netlify on their edge runtimes, and the first public release of the merged celld and workerd project. Stackmaven will check back on or around January 10.

Sources cited

1. Deno is joining Cloudflare (Deno blog) deno.com
2. Deno is joining Cloudflare (Cloudflare blog) blog.cloudflare.com
3. Cloudflare acquires Node.js creator's startup that copied its serverless playbook (The New Stack) thenewstack.io
4. Edge Functions overview (Supabase docs) supabase.com
5. Edge Functions overview (Netlify docs) docs.netlify.com