# Deno joins Cloudflare — Deno Deploy will shut down and runtime development will end Deno's entire team is moving to Cloudflare to combine celld and workerd for self-hosted Workers. Deno Deploy has six months left, while the standalone Deno runtime gets one year of maintenance before the team stops developing it. The Cloudflare move is a hard migration deadline for Deno Deploy users and a major maintenance change for Deno runtime adopters. JSR will continue, and self-hosted distributed Workers are still a future plan. - Status: Active - Published: 2026-10-10T09:45:43+13:00 - Updated: 2026-10-10T09:45:43+13:00 - Categories: Web Development, Cloud & Infrastructure, Cloud Platforms, JavaScript - Tags: API migration, Cloudflare, Deno, Durable Objects, JavaScript, Workers - Canonical HTML: https://beyondthe.news/dossiers/deno-cloudflare-joins-deploy-shutdown-runtime-maintenance-workerd ## What changed On October 9, 2026 Ryan Dahl announced that the entire Deno team is joining Cloudflare. Instead of continuing to develop its separate JavaScript runtime and Deno Deploy hosting service, the team will focus on combining celld with Cloudflare's open-source workerd runtime to support distributed, self-hostable Workers and Durable Objects. Deno says Deploy will keep running for six months and then shut down, with migration help for paying customers moving to Cloudflare Workers. The Deno runtime will receive monthly bug-fix and security releases for one year; after that, the team will stop its development. The runtime remains open source and community continuation is possible. JSR will remain operational as its infrastructure moves to Cloudflare, and rusty_v8 support continues. ## Why it matters Builders have two different decisions. Deno Deploy users need a hosting migration plan before a hard service shutdown; runtime users need to reassess maintenance and security exposure once official development ends. The new Cloudflare effort could eventually let teams operate Workers and Durable Objects on their own machines rather than relying on one network, but that portability is a development objective, not a delivered compatibility guarantee. Deno's runtime is not being immediately removed or relicensed. ## Deno Deploy has a six-month exit window Deno's October 9 statement says the hosting service will continue for six months before shutdown. Paying customers are offered help migrating to Cloudflare Workers. Teams should inventory deployments, stateful services, secrets, domain routing, logs, storage and any runtime-specific APIs before choosing a replacement; compatibility is not promised to be automatic. ## Runtime maintenance is time-limited, not immediately withdrawn The standalone Deno runtime gets one year of monthly security and bug-fix releases. After that, the joining team will stop developing it, while the code remains open source. Existing Deno CLI and compiled-binary users therefore face a maintenance-owner question rather than an immediate breaking release. ## Cloudflare wants portable, self-hosted distributed Workers Cloudflare's workerd runtime is already open source, but its current self-hosted Durable Objects implementation cannot scale beyond a single instance in the way Cloudflare's hosted platform can. The teams intend to merge celld's distributed routing and storage design with workerd so self-hosters can run the Workers model across multiple servers. No production-ready merged distribution or migration date was promised. ## JSR and rusty_v8 follow different paths The JSR registry continues operating, with its infrastructure moving to Cloudflare. The team also plans to maintain rusty_v8 and work toward integrating it with workerd. Neither commitment means Deno Deploy or the standalone Deno runtime will keep receiving the same long-term development investment. ## Key details - Announcement date: October 9, 2026; entire Deno team joining Cloudflare. - Deno Deploy service to shut after six months; paying customers offered migration help. - Deno runtime gets monthly bug/security releases for one year, then team development ends. - Deno source remains open and community continuation is welcome. - JSR continues operating; infrastructure will move to Cloudflare. - Cloudflare and Deno intend to merge celld and workerd for distributed self-hosted Workers/Durable Objects. - The self-hosting merger is a plan, not a released compatibility guarantee. ## Builder takeaways - Inventory Deno Deploy applications now and test target-host compatibility before the six-month service deadline. - For standalone Deno applications, pin supported releases and define who will maintain runtime security after the one-year support period. - Treat Cloudflare Workers as a migration candidate, not a drop-in promise; verify filesystem, process, networking, persistence and deployment differences. - Keep JSR package availability separate from the Deno runtime/Deploy lifecycle in dependency plans. ## What to watch - Precise Deno Deploy shutdown date and documented migration path. - The final supported Deno runtime release and any community fork or stewardship transfer. - First production-ready merged celld/workerd distribution and Durable Objects portability tests. - Changes to JSR operations during Cloudflare infrastructure migration. ## Uncertainties - No exact shutdown calendar date or automated Deno Deploy migration guarantee is given in the October 9 announcements. - Cloudflare has not shipped the proposed merged self-hosted distributed runtime. - Long-term third-party maintenance of the open-source Deno runtime is not yet established. ## Sources - [Deno is joining Cloudflare](https://deno.com/blog/cloudflare) — Deno · primary · 2026-10-09T00:00:00+13:00. First-party lifecycle and support commitments. - [Deno is joining Cloudflare](https://blog.cloudflare.com/deno-joins-cloudflare/) — Cloudflare · primary · 2026-10-09T00:00:00+13:00. Detailed technical rationale and celld/workerd self-hosting roadmap. - [Deno joins Cloudflare to bring Workers to self-hosted infrastructure](https://runtimewire.com/article/deno-joins-cloudflare-self-hosted-workers) — RuntimeWire · independent · 2026-10-09T00:00:00+13:00. Independent summary of developer migration implications.