The Deno Deploy shutdown will come six months from now, Deno announced on 9 October 2026, alongside news that its team is joining Cloudflare. The Deno runtime gets one more year of bug-fix and security releases before development ends. JSR, Deno’s package registry, continues and moves to Cloudflare.
What Cloudflare and Deno Actually Announced
Two posts went up on 9 October 2026: one on Deno’s blog by Ryan Dahl, the creator of both Node.js and Deno, and one on Cloudflare’s blog co-written by Dahl and Kenton Varda, the Cloudflare engineer behind its Workers platform.
Neither post uses the word “acquisition”. Dahl’s post says the Deno team is joining Cloudflare and that future development moves to a shared platform rather than “a separate runtime and hosting service”. Cloudflare’s post frames the move around engineering: the stated goal is to make self-hosting Workers and Durable Objects a first-class way to build and run applications. Several technology outlets nonetheless reported the deal as an acquisition. Neither company disclosed financial terms.
The technical centre of the deal is a merge. Cloudflare’s post states plainly that “we’re merging workerd and celld”, with Dahl and Deno co-founder Bert Belder leading the work. Workerd is Cloudflare’s open-source version of the Workers runtime; celld is Deno’s open-source implementation of Workers and Durable Objects, published under the Apache 2.0 licence in August 2026. Cloudflare’s post notes that workerd’s self-hosted Durable Objects support “is limited to a single instance”, which is the limitation the merge is meant to remove.
Which Deno Products Survive and Which Close
One product closes, one enters a maintenance window that ends, and one continues under Cloudflare’s infrastructure.
| Product | Status | Timeline as announced |
|---|---|---|
| Deno Deploy (hosting service) | Closing | Six months of operation, then shutdown. No calendar date given. |
| Deno runtime | Maintenance, then development ends | One year of monthly bug-fix and security releases. No calendar date given. |
| JSR (package registry) | Continuing | No end date. Infrastructure moves to Cloudflare. |
| Deno as an open-source project | Stays open source | No date. Deno invites outside maintainers. |
| celld | Merging into workerd | Further announcements promised “in the coming months”. |
Dahl’s wording on each point is specific. On the hosting service, Deno’s announcement says “Deno Deploy will continue operating for six months before shutting down” and that “we will provide migration support for paying customers moving to Cloudflare Workers”. On the runtime: “we will support the Deno runtime for another year with monthly releases containing bug fixes and security updates”, and “after that year we will end our development of the Deno runtime”. On the registry: “JSR will continue operating, with its infrastructure moving to Cloudflare”.
Deno’s post does not address Deno Subhosting or Deno Sandbox, two other products listed in the company’s own site navigation, and it does not mention Deno KV.
Why There Is No Shutdown Date Yet
Both deadlines were published as durations, not dates, and neither company has named the day either window opens or closes.
Counted from the 9 October 2026 announcement, six months lands in early April 2027 and one year lands in October 2027. Several outlets have printed “around April 2027” for the Deno Deploy closure on exactly that arithmetic. It is a reasonable inference, but it is an inference: neither Deno nor Cloudflare has confirmed that the clock started on the announcement date, and neither has published a cut-off.
As of 11 October 2026, the only timings on the record are “six months” for Deno Deploy, “another year” of releases for the runtime, and “the coming months” for the workerd and celld merge. Deno has not said what its migration support for paying customers will consist of, and Cloudflare has not published a Deno Deploy migration guide.
What Deno Deploy Users Need to Do
The practical position differs sharply between paying and free users, because only paying customers were promised help.
- Check your billing status: Migration support to Cloudflare Workers was promised to paying Deno Deploy customers. Deno’s post makes no equivalent commitment to users on free plans, who have the same six-month window and no stated assistance.
- Treat the window as already running: Because no start date was published, the safest assumption is that the six months began on 9 October 2026, which puts the outside edge in early April 2027.
- Inventory what is actually hosted on Deploy: The shutdown affects the hosting service only. Code written for the Deno runtime keeps running elsewhere, including on your own servers, for as long as that runtime is maintained.
- Consider self-hosting now if you want to skip the migration: Cloudflare’s post says that “if you can’t wait, you can start self-hosting celld or workerd today”. Both are open source under Apache 2.0, and celld is at an early release.
- Watch for migration details rather than assuming them: Neither company has described the shape of the migration support, so the scope of what paying customers receive is still unknown.
What Happens to the Deno Runtime After the Year
The runtime does not disappear when Deno stops developing it; it becomes an open-source project without a funded maintainer.
Dahl’s post is explicit that “Deno will remain open source, and we welcome others who want to continue its development.” It names no successor maintainer and no foundation, and sets no governance arrangement for the handover. That leaves the runtime’s future dependent on whether outside contributors take it up.
There is precedent in Dahl’s own history for a community fork changing a runtime’s direction. Node.js was forked as io.js in 2014 by contributors unhappy with its stewardship, and the two projects later merged under the Node.js Foundation. Whether anything comparable forms around Deno is unknown; what is on the record is only Deno’s invitation.
Cloudflare, for its part, is not promising to carry the runtime forward. Its interest, as its own post sets out, is the Workers programming model and the merge of workerd and celld, not the continuation of a second JavaScript runtime.
Frequently Asked Questions
When Exactly Is the Deno Deploy Shutdown?
No date has been published. Deno said on 9 October 2026 that Deno Deploy would operate for six months before shutting down, which puts the closure in early April 2027 if the clock started on the announcement. Neither Deno nor Cloudflare has confirmed a cut-off date.
Did Cloudflare Acquire Deno?
Neither company’s announcement uses the word acquisition. Both say the Deno team is joining Cloudflare, and no financial terms were disclosed. Several technology outlets described the deal as an acquisition.
Is the Deno Runtime Dead?
Not immediately. Deno will issue monthly bug-fix and security releases for one more year, then end its own development of the runtime. The code stays open source, and Deno has invited others to continue it, but no successor maintainer has been named.
What Happens to JSR?
JSR, Deno’s JavaScript package registry, continues operating. Its infrastructure moves to Cloudflare, and no end date was given for the service.
Do Free Deno Deploy Users Get Migration Help?
Deno promised migration support to paying customers moving to Cloudflare Workers. Its announcement makes no such commitment for users on free plans, who face the same six-month window.
