Deno Joins Cloudflare: Deno Deploy Has Six Months, the Runtime Has One Year

Deno Deploy will shut down six months after October 9, 2026, the day the Deno team announced it is joining Cloudflare. The Deno runtime gets one more year of bug fixes and security updates, and then its development ends.

Cloudflare and Deno published joint announcements that day. Ryan Dahl, who created both Node.js and Deno, and Bert Belder will lead a new Cloudflare effort to make self-hosted workerd a supported way to run Workers-style apps. This post covers what happens to each Deno product, who is exposed, what self-hosted workerd means for lock-in, and where this leaves the JavaScript runtime picture. It closes with two other Cloudflare updates from the same week.

The short version: if anything you run sits on Deno Deploy, plan a move now. Neither post gives a calendar date, so treat early April 2027 as the working deadline. JSR keeps running. Fresh is not mentioned. Sites built with Astro or Next on Node, Cloudflare Workers or Vercel see no change today. Sites using Netlify or Supabase edge functions should watch what those vendors say, since both are built on Deno.

What Cloudflare and Deno announced on October 9

The Cloudflare announcement is a joint post by Kenton Varda and Ryan Dahl. It says "The Deno team is joining Cloudflare." Neither post gives a price or deal terms. The New Stack reported that terms were not disclosed.

The plan centers on workerd, the open-source runtime behind Cloudflare Workers. Cloudflare says it is "the same code we run in production," and not a separate copy. Dahl and Belder will lead "a new effort to make workerd self-hosting a first-class supported way" to run apps built for Workers.

The other piece is celld. The Deno team released celld in August. Cloudflare describes it as "one binary, written in Rust, with object storage as its only external service dependency." It runs Workers apps and Durable Objects on your own machines. Cloudflare says the teams are "merging workerd and celld," which means moving celld’s code and ideas back into workerd.

No dates are attached to that work. Cloudflare says, "We’ll have more announcements about this work in the coming months."

What happens to Deno Deploy, the runtime, JSR and Fresh

Ryan Dahl’s post on the Deno blog carries the product details. The Cloudflare post does not cover them. Here is what each product gets, and what the posts leave out.

On the runtime, Dahl writes: "We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates." He adds: "Deno will remain open source, and we welcome others who want to continue its development."

Fresh, the Deno web framework, gets no mention beyond site navigation. Its own site, as of October 15, shows a "Fresh 2.3 is here!" banner and no notice about Cloudflare. Fresh lists Cloudflare Workers as one of its deploy targets. It is still built on Deno.

Planning around the Deno Deploy shutdown

The Deno post says: "Deno Deploy will continue operating for six months before shutting down." It does not give a date. Six months from October 9 lands in early April 2027, but that is our reading, not Deno’s.

For agencies, the first job is an inventory. Deno Deploy is easy to forget because it is often used for small things: a webhook handler, a form relay, a preview site, a scheduled script. Check every client account, not just the ones you set up.

Then sort each project by what it depends on.

• Plain request handlers that use web-standard APIs usually move to Cloudflare Workers with modest changes. Deno Deploy and Workers both build on web-standard request and response APIs.
• Projects that use Deno KV or other Deno Deploy services need a new data store. The announcement says nothing about Deno KV.
• Projects tied to the Deno runtime itself can run in a container on any host while the runtime still gets fixes. That buys time, not a long-term home.

Paying customers should contact Deno about the promised migration support before choosing a target.

Does anything change today for Astro, Next and headless CMS sites?

For most nonprofit and association sites, no. A headless CMS front end built with Astro or Next.js usually runs on Node, on Vercel, on Netlify or on Cloudflare. None of those hosting paths change with this news. Cloudflare Workers and Cloudflare Pages keep running as before. Our Cloudflare Pages explainer and Astro explainer cover where those products sit.

Three groups should pay closer attention.

Fresh sites. Fresh is built on Deno. The runtime still gets security fixes for a year, so nothing breaks soon. But a Fresh build started today will outlive its runtime’s core team unless the community picks it up. For new client work, that is a reason to choose something else.

Edge functions on Netlify and Supabase. Netlify’s 2022 launch post says its Edge Functions are "built on Deno." Supabase’s Edge Runtime describes itself as "a web server based on Deno runtime." Neither company has commented in anything we found as of October 15. Both platforms can carry the runtime themselves or switch, and their customers will want to know which. Our post on edge versus serverless functions explains where edge functions fit.

Small Deno scripts. Build tools, linters and CLI scripts written for Deno keep working. Plan to move them during the next year of maintenance releases.

Self-hosted workerd and the lock-in question

For agencies that recommend Cloudflare to nonprofit clients, the lock-in question comes up often. A board or IT committee wants to know what happens if the vendor relationship ends. Self-hostable workerd is Cloudflare’s answer.

Cloudflare makes that case directly. Varda writes that "we have former customers that migrated away from us by using workerd." The workerd repository lists three uses: an application server for self-hosting Workers apps, a local development tool, and a programmable HTTP proxy. It is licensed Apache 2.0.

There are real limits today, and Cloudflare names them.

• Durable Objects. workerd supports them “only in a single-instance way, good enough for local testing,” per the Cloudflare post. That is the main gap the new effort targets.
• Security. The workerd README carries the warning “`workerd` is not a hardened sandbox.” It says you must run it inside a secure sandbox, such as a virtual machine.
• celld is beta. The celld site lists version 0.6.2 as beta. It warns that self-hosting “doesn’t guarantee reliability.”

So the exit door exists, but it is narrow for apps that lean on Durable Objects. For a typical association site using Workers for redirects, forms or API proxies, workerd is already a workable fallback. Write that into the architecture notes you hand clients. It is a useful line in a procurement answer.

Where this leaves the JavaScript runtime landscape

Server-side JavaScript now has a different shape than it did a year ago. Each of the main runtimes has a new owner or a new schedule.

The Node.js release schedule announcement says "No more odd/even distinction – Node.js 27 will become LTS." We covered what that means for version choices in our post on Node’s annual release model.

Bun’s own post from December 2, 2025, says "Bun stays open-source & MIT-licensed" and "The same team still works on Bun." That is the reverse of what happened to Deno, where the team moves on and the code stays open.

Node, Deno and workerd all run on Google’s V8 engine, the one inside Chrome. Bun uses Apple’s JavaScriptCore. Our guide to browser engines in 2026 covers how few engines now carry the web.

For agencies, the practical read is simple. Node remains the safe default for long-lived client work. The Workers model is now backed by two teams who both wrote JavaScript runtimes. Deno’s ideas continue inside workerd, but Deno Deploy and the Deno runtime as products are ending.

Two more Cloudflare updates from the same week

Transformers for Logpush (October 12). Cloudflare’s Transformers post explains a feature that filters, reshapes and redacts logs before export. "A Transformer is a SQL query written for a specific Logpush dataset." The changelog lists it as generally available on September 30, on Free, Pro, Business and Enterprise plans. Each account gets 1 GB of transformation input a month, with more billed per GB. For organizations that ship logs to a SIEM, this is a way to strip personal data before it leaves Cloudflare.

Hyperdrive and MySQL (October 14). Cloudflare’s Hyperdrive MySQL post says MySQL support "is now generally available (GA)." Note the timing. The Hyperdrive changelog dates the GA to August 7, 2026, so the October post is an engineering write-up. It explains fixes for emoji corruption, character set resets and a rare caching bug. Hyperdrive lets Workers reach an existing MySQL database, which matters for teams with WordPress or Drupal data they want to read from the edge. Our post on EmDash and Cloudflare covers another Cloudflare CMS path.

What to watch next on Deno and Cloudflare

1. A firm Deno Deploy shutdown date and the migration process for paying customers.
2. Any word on Fresh, Deno KV and Subhosting. None is covered in the October 9 posts.
3. Statements from Netlify and Supabase on the runtime under their edge functions.
4. Whether the community forks Deno. Dahl invited others to continue its development.
5. The workerd and celld merge. Watch for multi-instance Durable Objects in self-hosted workerd.

Frequently Asked Questions