Deno team joins Cloudflare as companies combine runtimes for Workers self-hosting

Cloudflare and Deno announced on October 9, 2026, that the Deno team will join Cloudflare. The companies say they will combine Deno’s celld project with Cloudflare’s workerd runtime, with the goal of improving how customers self-host Workers and Durable Objects.

The announcement is best described as the Deno team joining Cloudflare. The primary announcements do not explicitly establish that Cloudflare legally acquired Deno, and they do not disclose the transaction’s financial terms.

A focus on self-hosted Workers

Ryan Dahl and Bert Belder will lead the work to make workerd self-hosting a first-class supported deployment model, according to the announcements. The technical effort will merge celld, from Deno, with workerd, Cloudflare’s runtime project.

The stated objective is to improve self-hosting for Workers and Durable Objects. These are planned outcomes of the integration rather than measured results: the announcements do not claim that the merger has already improved performance, scalability or adoption.

The move brings Deno’s team and relevant projects into Cloudflare’s work on the Workers programming model. However, the supplied announcements do not describe the exact legal structure of the arrangement or identify which corporate entities or assets, if any, are being transferred.

Deno runtime support will last one year

Deno said its runtime will continue to receive support for one year after the announcement. During that period, support will consist of monthly bug-fix and security releases.

After the one-year period, official development of the runtime will end. Deno will remain open source, meaning the announcement does not describe the codebase as being closed or removed. It does, however, mark the end of Deno’s planned official development and scheduled release support.

The announcement does not provide a more precise calendar date for the end of that support period. The one-year timeframe should therefore be understood as a stated support window beginning with the October 9 announcement, rather than as a separately specified shutdown date.

Deno Deploy will shut down after six months

Deno also announced that Deno Deploy will continue for six months before shutting down. Deno said it will provide migration support for paying customers moving to Cloudflare Workers.

The announcements do not provide a precise calendar shutdown date. Based on the stated timeline, the shutdown is expected approximately six months after October 9, 2026, but that should not be treated as a contractual date supplied in the announcements.

The Deploy decision is the most immediate customer-impacting part of the announcement. Customers using the service will need to plan for a move to Cloudflare Workers within the announced transition period, while paying customers are promised migration support.

The supplied material does not independently establish a separate claim about a July 20, 2026, Deploy Classic shutdown, so that claim is not part of this announcement’s confirmed timeline.

JSR will continue under Cloudflare infrastructure

JSR will continue operating, and its infrastructure will move to Cloudflare, according to the announcements. The material does not say that JSR will be discontinued as part of the transition.

That creates a different path from the Deno runtime and Deno Deploy. The runtime has a defined period of bug-fix and security support followed by the end of official development, while Deploy has a six-month continuation period before shutdown. JSR, by contrast, is described as continuing with its infrastructure moving to Cloudflare.

What users should take from the announcement

Deno users and customers are facing different timelines depending on which part of the ecosystem they use. Deno Deploy customers have the shortest stated window, with the service scheduled to shut down roughly six months after the announcement. Paying customers are expected to receive migration support for a move to Cloudflare Workers.

Users of the Deno runtime have a longer transition period: one year of monthly bug-fix and security releases, including security updates, followed by the end of official development. The runtime will remain open source after that point, but the announcement does not promise continued official releases beyond the one-year period.

JSR users are not told to migrate away from the service. Instead, the announcement says JSR will continue operating while its infrastructure moves to Cloudflare.

What remains unclear

The announcements establish the team move, the planned runtime integration and the product timelines, but they leave several transaction details unspecified. No financial terms are disclosed in the primary announcements. That absence does not establish that no terms were disclosed elsewhere, only that the supplied primary posts do not provide them.

The legal structure of the arrangement is also not stated in the verified material. For that reason, describing the event as an acquisition could overstate or mischaracterize what has been announced. The confirmed description is that the Deno team is joining Cloudflare.

The technical benefits are similarly prospective. Cloudflare and Deno say the celld and workerd projects will be merged to improve self-hosting of Workers and Durable Objects, but the announcements do not provide measured results from that work.

For now, the clearest practical consequences are the transition schedules: Deno Deploy is planned to shut down after six months, the Deno runtime will receive official bug-fix and security support for one year, and JSR will continue while its infrastructure moves to Cloudflare.