Cloudflare Acquires Deno

TL;DR

Buying for a business?Offer from Amazon

Get business pricing on office and shipping supplies

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

The Deno team is joining Cloudflare and will focus on a shared platform built around Cloudflare Workers and Durable Objects. Deno says it will support the runtime for one more year, while Deno Deploy will operate for six months before shutting down; JSR will continue.

Deno’s entire team is joining Cloudflare, where it will work with the Workers and Durable Objects teams on a shared platform for building distributed applications. Deno said it will stop developing its separate runtime after one more year of monthly bug-fix and security releases, while its hosting service, Deno Deploy, is set to shut down after six months.

Deno said the move reflects a decision to concentrate future development on a shared platform rather than maintain a separate runtime and hosting service. The team plans to combine its work with Cloudflare’s Workers and Durable Objects products. Deno describes the intended programming model as one that builds scaling into application development, instead of requiring each developer to assemble and operate the underlying infrastructure.

The transition has different timelines for Deno’s products. The runtime will receive monthly releases with bug fixes and security updates for another year, after which Deno will end its own development of it. Deno Deploy will continue operating for six months before shutting down. The company says it will provide migration support for paying Deploy customers moving to Cloudflare Workers.

Not every project is scheduled to end. Deno said JSR will continue operating, with its infrastructure moving to Cloudflare. It also plans to keep supporting rusty_v8 and work toward integrating it into workerd, Cloudflare’s JavaScript and WebAssembly runtime. Deno said the runtime will remain open source and that others are welcome to continue its development after the company stops maintaining it.

What Changes for Deno Users

For developers using Deno, this is both a team acquisition and a change in product direction. The Deno runtime is not being shut off immediately: the company has committed to a year of monthly maintenance releases. But the announcement sets an end point for Deno’s own runtime development, leaving its longer-term direction dependent on outside maintainers or a future arrangement not detailed in the post.

Deno Deploy customers face a nearer deadline. Its announced six-month operating period gives users time to plan a move, and Deno says paying customers will get migration support to Cloudflare Workers. The post does not promise that every application can move without changes, so customers may need to check how their workloads and dependencies map to the destination service.

The shift also brings Deno’s engineering work into a company that already operates a global developer platform. Deno says it wants the combined work to support applications on Cloudflare’s network or on customers’ own infrastructure. That is an ambition, not a detailed delivery plan: the announcement does not set out a release schedule or explain how the proposed shared platform will be packaged for users.

From Deno Runtime to Shared Platform

Deno was developed as a JavaScript and TypeScript runtime with a broader toolchain, including attention to security, module distribution, and compatibility with Node.js. In its announcement, the team describes that work as part of a wider effort to make server-side software easier to build and run.

The company traces its move through Deno Deploy, its application hosting service, and then celld, a project it says builds on the Cloudflare Workers programming model. Deno presents celld as a way to build distributed applications with less infrastructure work for each application. The acquisition places that effort alongside Cloudflare’s Workers and Durable Objects teams rather than continuing it as a separate Deno runtime and hosting product.

Deno also points to persistent state, serverless execution and WebSockets in Durable Objects as capabilities it wants to explore for AI agent applications. That is the team’s stated area of interest, not a claim that the acquisition has already produced a new agent platform. The source says more detail is available in a joint post by Deno’s Ryan Dahl and Cloudflare’s Kenton Varda.

““Today we’re announcing that the entire Deno team is joining Cloudflare to take that work further.””

— Deno

Details Still to Be Set

The source does not provide the announcement date, so the exact calendar dates for the one-year runtime support period and six-month Deploy shutdown period cannot be calculated from the supplied material. It also does not specify the precise final dates for releases or service access.

Deno has not described how the planned shared platform will work in practice, when it will be available, or what parts of celld will carry forward. The terms of the acquisition, including its financial value, were not included in the source. It is also unclear who, if anyone, will take on runtime development after Deno ends its own maintenance; the company says it welcomes other maintainers but does not name a successor.

The migration announcement applies specifically to paying Deno Deploy customers moving to Workers. The post does not detail migration support for other users, provide a technical compatibility guide, or explain what changes JSR’s move to Cloudflare infrastructure will involve.

Runtime and Deploy Timelines

Deno says it will continue issuing monthly runtime releases with bug fixes and security updates during the next year, then end its own runtime development. Users relying on Deno should watch for the company’s release notices and plan around that support window, while keeping in mind that the runtime will remain open source.

Deno Deploy is scheduled to keep operating for six months before shutdown. Paying customers can seek the migration support Deno has promised for moves to Workers. Deno has not provided a detailed migration timetable in the supplied announcement, so affected users will need further guidance on service dates and technical steps.

JSR is set to continue, with its infrastructure moving to Cloudflare, and Deno says it will keep supporting rusty_v8 while working toward an integration with workerd. The next substantive update is likely to clarify the shared platform’s scope and the practical arrangements for affected products, but no date for such details is given in the source.

Key Questions

Is Cloudflare acquiring Deno?

Deno says its entire team is joining Cloudflare. The supplied announcement does not state the financial terms or provide other transaction details.

Will the Deno runtime stop working now?

No immediate shutdown is announced. Deno says it will provide monthly bug-fix and security releases for another year, then end its own development. The runtime will remain open source.

When will Deno Deploy shut down?

Deno says Deploy will continue operating for six months before shutting down. The source provided here does not include the announcement date or a calendar shutdown date.

What happens to JSR?

Deno says JSR will continue operating, with its infrastructure moving to Cloudflare. The announcement does not give a timetable or describe the operational changes in detail.

Can Deno Deploy customers move to Cloudflare Workers?

Deno says it will provide migration support for paying customers moving to Workers. It has not supplied a detailed migration guide or confirmed whether every application can move without modification.

Source: hn