NewsCloud & DevOpsOpen SourceJavaScript

Cloudflare Acquires Deno: What Developers Must Do Now

Deno dinosaur mascot with countdown clock next to Cloudflare logo, representing the acquisition and migration timeline
Cloudflare acquired Deno in October 2026. Deno Deploy shuts down in 6 months, the runtime in 12.

Cloudflare acquired the Deno team on October 9, 2026. Ryan Dahl and Bert Belder — the engineers who built the runtime — are now working on Cloudflare’s Workers platform. Deno Deploy shuts down in six months. The runtime gets one more year of bug-fix releases, then Cloudflare stops developing it. If you’re running anything on Deno today, the clock has started.

What Cloudflare Actually Bought

The runtime is not what Cloudflare wanted. The real target was celld — a Rust binary Ryan Dahl built to enable self-hosting of Cloudflare Workers with distributed Durable Objects on S3-compatible storage. Think of it as the missing piece for running the Workers programming model outside Cloudflare’s network.

Dahl confirmed this framing: the runtime is no longer “where I can do the most important work.” Dahl and Bert Belder are now merging celld with Cloudflare’s existing open-source workerd project. The result — eventually — is a production-grade self-hosted Workers runtime. That’s the bet Cloudflare made. The Deno runtime was collateral.

This explains the sunset. Cloudflare isn’t hostile to the runtime; they’re just not resourcing something that doesn’t serve their platform goals. Vite and Astro, also acquired by Cloudflare in 2026, got “continued development and open-source governance” commitments. Deno got a sunset date. Worth noting the difference.

Two Clocks, Two Urgencies

There are two distinct timelines and developers are conflating them:

  • Deno Deploy: ~April 2027 (6 months) — Hosted apps on Deno Deploy need to move. Cloudflare is offering assisted migration to Workers for paying customers. This is the urgent one.
  • Deno runtime: ~October 2027 (12 months) — Monthly bug fixes and security releases continue. After that, the project is open source and on its own. Dev tooling running on Deno locally can wait.

If you’re only using Deno as a local runtime for scripts or tooling, you have a year. If you’re hosting anything on Deno Deploy, you have six months. Do not confuse these.

Check Your Exposure First

Before you decide anything, audit how deeply you’re tied to Deno-specific APIs. One command:

# Audit your codebase for Deno-specific API usage
grep -rn "Deno\." .

# Count occurrences to estimate migration effort
grep -rn "Deno\." . | wc -l

Code written against web standards plus npm packages ports quickly — sometimes in hours. Code using Deno.env.get(), Deno.serve(), Deno KV, or Deploy-specific primitives (cron, queues) requires actual rewriting. The count gives you a real estimate before you commit to a migration path.

Your Migration Options

Node.js 24+ is the default answer for most teams. Node absorbed Deno’s best ideas: native TypeScript stripping (run .ts files without a build step), built-in fetch, a native test runner, and a permission model. The irony is real — Deno pressured Node into shipping these features, then Node made Deno unnecessary for most use cases. One caveat: Node’s --experimental-strip-types only removes type annotations. Enums and decorators still need tsx or esbuild.

Cloudflare Workers is the natural landing spot for Deno Deploy users. Workers accepts Hono apps as a default export with wrangler tooling. Cloudflare wants these customers and is actively helping with migration. If you’re already in the Cloudflare ecosystem, this is the lowest-friction path.

Bun works if you want the fastest JS runtime available. It accepts the same Node-style entry file without extra dependencies. Worth evaluating if performance is a priority.

workerd (self-hosted) is installable via npm today but treat it as provisional until the celld merge completes. Not a production recommendation yet.

What’s Not Going Away

The JavaScript Registry (jsr.io) is staying live. JSR is a Cloudflare asset, not a liability — it’s a credible npm competitor and Cloudflare has no incentive to kill it. Packages published to JSR remain safe to depend on.

Community Forks: Watch, Don’t Depend

Two forks emerged within days of the announcement. Ende (an anagram of “Deno”) drops Node compatibility and removes Deploy, KV, and Jupyter integration — a return to Deno’s original philosophy. Dodo (github.com/are-we-dodo-yet/dodo) is a community-led fork aiming to decentralize maintenance. Neither has shipped a release yet. These are worth watching over the next six months, but they are not migration paths today.

The Short Version

  • Run the audit command. Count your Deno.* calls.
  • If you’re on Deno Deploy: start the Workers migration now. Six months is shorter than it sounds.
  • If you’re on the runtime only: you have a year. Node.js 24+ is the pragmatic move.
  • Don’t start new projects on Deno.
  • JSR is fine. Keep using it.
  • Watch Ende and Dodo, but don’t depend on them yet.

The Hacker News thread hit 1,315 points and 677 comments. Paul Webb’s summary was blunt: “YOU reimplemented Node and now you’re bored?” That’s harsh. It’s also mostly accurate. The runtime built to fix Node ended up competing with a version of Node it helped create. The engineering goes to a better-funded use case. The ecosystem manages the transition. That’s how this usually goes.

ByteBot
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

    You may also like

    Leave a reply

    Your email address will not be published. Required fields are marked *

    More in:News