Deno Joins Cloudflare, Deno Deploy to Close: What to Check

The Deno team said on October 9, 2026 that it is joining Cloudflare. Its hosting service, Deno Deploy, will shut down in six months, and the Deno runtime will receive fixes for one more year. The change reaches websites, APIs and apps built on Deno; a site running on WordPress or Drupal is not affected.

What we know

The announcement: Ryan Dahl wrote on the Deno blog on October 9, 2026 that the entire team is joining Cloudflare. Cloudflare published its own post the same day, signed by Kenton Varda and Dahl, whom it introduces as the creator of Node.js.
Deno Deploy: it will keep operating for six months and then shut down, according to the Deno post. Paying customers will get migration support to move to Cloudflare Workers.
The Deno runtime: it gets one more year of monthly releases with bug fixes and security updates. After that year the team will stop developing it. It stays open source, and the post invites others to carry it on.
JSR: the package registry keeps running and its infrastructure moves to Cloudflare, the same post says.
Why: Dahl says the team has decided to put its future work into a platform shared with Cloudflare instead of maintaining its own runtime and hosting service. According to Cloudflare's post, the plan is to merge celld, the project Deno released in August, with workerd, the open-source engine behind Cloudflare Workers, so that the same model can also be self-hosted.
What the posts leave out: the price and terms of the deal, exact shutdown dates, and what happens to free Deno Deploy accounts or to Fresh, the Deno project's web framework.

What changes and what doesn't

The calendar changes for anyone who depends on Deno. The posts give periods, not dates. Counted from October 9, 2026, Deno Deploy's six months run to April 2027 and the runtime's year runs to October 2027. That sum is this article's.

Nothing changes today: Deno Deploy is still up and the runtime is still being patched. It also does not touch anyone who uses Cloudflare for DNS or as a content delivery network, or sites built on WordPress, Drupal or a site builder on traditional hosting, none of which use Deno.

One caveat. Migration support is announced for paying customers and points to Cloudflare Workers. Cloudflare itself admits in its post that Workers is not perfectly compatible with traditional platforms, so moving an app may require code changes.

How to tell if it affects you

Ask whoever built your site or app. The exact question: "Does anything of ours run on Deno or sit on Deno Deploy?" Think of the small parts too: an API, a form handler, a scheduled job, an internal tool.
Look at the addresses. According to the Deno Deploy documentation, every app gets an address ending in ".deno.net", such as my-app.my-org.deno.net. If your site, a form or an integration calls an address like that, it depends on the service.
Look at the code. A "deno.json" file in the repository means the project uses Deno. Its absence proves nothing: according to the documentation, Deno also runs with just a "package.json".
If you are on Deno Deploy, ask for a dated plan. You have about six months. Pick the destination (Cloudflare Workers or another host), take a copy of any data stored in the service and leave time for testing.
Protect your SEO during the move. If the site changes hosting but keeps its domain and URLs, Google's guide to changing hosting asks you to test the new copy first, lower the DNS TTL at least a week ahead, confirm with Search Console's URL Inspection tool that Googlebot can get in, and keep the old hosting on until it stops receiving traffic. Google warns that crawling may dip for a few days and then recover.
If your site is served from a ".deno.net" address, don't wait. When the service is switched off that address will stop responding, and so will every link pointing to it and whatever Google has indexed there. Move it to a domain you own and 301-redirect from the old address while Deno Deploy is still running. This is this article's own inference: the posts do not mention those addresses.
If you run the Deno runtime on your own server, there is no rush: it will get security patches for a year. Put October 2027 in the calendar to decide whether to stay, should another team keep it alive, or to move to a different runtime.

Sources

Updates: the exact dates for the Deno Deploy shutdown and the end of runtime development will be added here when Deno or Cloudflare publish them.