--- title: Deno is joining Cloudflare | daily.dev description: The entire Deno team is joining Cloudflare, shifting future development toward a shared platform built on the Cloudflare Workers programming model and Durable... canonical: https://daily.dev/posts/deno-is-joining-cloudflare-cxoxmkbrn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Deno is joining Cloudflare | daily.dev og:description: The entire Deno team is joining Cloudflare, shifting future development toward a shared platform built on the Cloudflare Workers programming model and Durable... og:url: https://daily.dev/posts/deno-is-joining-cloudflare-cxoxmkbrn og:image: https://api.daily.dev/og/posts/cXOxMKBrN.png og:image:alt: Deno is joining Cloudflare og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Deno is joining Cloudflare **[Deno](https://daily.dev/sources/deno)** · 3 min read · 0 upvotes · 0 comments ## Summary The entire Deno team is joining Cloudflare, shifting future development toward a shared platform built on the Cloudflare Workers programming model and Durable Objects, called celld. Deno runtime will get bug fixes and security updates for one more year before development ends, though it remains open source. Deno Deploy will shut down in six months, with migration support offered to paying customers moving to Cloudflare Workers. JSR will keep operating, moving its infrastructure to Cloudflare, and rusty_v8 support continues with integration work into workerd. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Is Deno Deploy shutting down? Yes, Deno Deploy will continue operating for six months before shutting down, as the Deno team joins Cloudflare and shifts focus to Cloudflare Workers. Migration support will be provided for paying customers moving their applications to Cloudflare Workers during this transition period. _Developers planning a Deno Deploy migration can track platform shifts like this on daily.dev._ ### Will the Deno runtime still be maintained now that the team joined Cloudflare? The Deno runtime will receive monthly releases with bug fixes and security updates for one more year after the team's move to Cloudflare, after which active development from the original team will end. Deno remains open source, and the team welcomes others to continue its development independently. _Teams relying on Deno in production can follow runtime support timelines like this on daily.dev._ ### What is celld and how does it relate to Cloudflare Workers and Durable Objects? Celld is a programming model built on top of Cloudflare Workers that lets developers build distributed applications with scaling built directly into the programming model rather than infrastructure each app must assemble itself. It combines the Deno team's work with Cloudflare's Workers and Durable Objects teams, and is especially aimed at supporting AI agent harnesses needing persistent state and WebSockets. _Engineers evaluating distributed app platforms can compare approaches like celld on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 328 comments across lobsters, hackernews (as of 2026-10-09). **TL;DR:** The dominant read is that this is an acquihire dressed up as a partnership: Cloudflare wanted the Deno team (and their celld tech) but is killing the Deno runtime and Deno Deploy, leaving users to migrate; reactions range from resigned shrugs to real frustration from invested users. **Sentiment:** 10% positive · 25% mixed · 65% skeptical **The case for** - Some see migrating off Deno as straightforward, especially with AI-assisted tooling, so the practical impact is overstated. - A few note celld being folded into workerd could yield a solid self-hostable alternative to Cloudflare's own infrastructure. - Some appreciate that Deno remains open source and could theoretically be picked up by the community. **The pushback** - Many call this a thinly veiled acquihire where Cloudflare wanted the team/tech (celld) but not the Deno product itself. - Frustration that the runtime's discontinuation after one year was buried in the announcement rather than headlined. - Users who went all-in on Deno (including some citing production migrations off Node) feel burned by the sudden sunset. - Skepticism that an open-source community fork will realistically sustain development once the core team moves on. - Broader distrust of chasing newer runtimes (Deno, Bun) over sticking with Node given repeated rug-pull-like outcomes. **By community** - lobsters (skeptical): Commenters frame the move as Deno being acquihired and effectively discontinued, with some side discussion on downstream impact for projects like yt-dlp. - hackernews (heated): A large, contentious thread mixing acquihire cynicism, anger from invested Deno users, runtime-wars debates (Bun vs Node vs Deno), and disagreement over how big a deal the migration really is. **Hottest debate:** Whether this is a cynical acquihire-and-kill move that burns users who bet on Deno, versus a routine and low-cost migration that's being overblown. **Open questions** - Will the open-source Deno runtime actually be picked up and maintained by the community after official development ends? - What will happen to companies and tools (e.g. yt-dlp, Slack plugins, Netlify/Supabase edge functions) that built heavily on Deno? - Is this acquisition-then-shutdown pattern a competition concern, and would it draw antitrust scrutiny? **Highlights** > Fundamentally this acquisition is not about Deno the open source project. It’s about buying an amazing team that has built a self-hosted version of Cloudflare Workers that actually doesn’t suck. And that is all about commoditizing the complement. Deno built celld, which implements the Workers and Durable Objects programming model with self-hosting in mind. Cloudflare says its own distributed infrastructure is too complicated for straightforward self-hosting, and it hadn’t successfully solved that problem. For customers who might be reluctant to commit to being locked in to Cloudflare’s infrastructure, having a rock solid self-hosted alternative reduces that reluctance. > — [ttul on hackernews](https://news.ycombinator.com/item?id=50021640) > "Deno is being discontinued and its development team will be acquired by Cloudflare" seems like the actual honest headline > — [mort on lobsters · 10 points](https://lobste.rs/s/8hauxs/deno_is_joining_cloudflare#c_h5qge0) > I lead a project built on Deno; it was not my call, just to be clear. Deno turned out unfortunately to be a miss and we had seen the writing on the wall. FWIW, we're moving to a much bigger Rust core program with node for JS user extensibility. (In other words, I'm not willing to risk using the deno_core crates.) The one silver lining here is that Deno had already increased their node/npm compatibility. Migrating off of the jsr ecosystem and back to npm is going to be less painful than one might imagine. I expect present LLMs to be sufficiently good at the task, for example. > — [cscheid on hackernews · 1 comments](https://news.ycombinator.com/item?id=50020993) > I feel it leaves a bitter flavor how Ryan Dahl pushed so hard for Deno and Deno Deploy for years, just to let them die within 1 year and 6 months respectively. Thankfully I don't have any codebases that heavily use Deno features, otherwise this would be a steep curve now. > — [bennett\_dev on hackernews · 4 comments](https://news.ycombinator.com/item?id=50020269) > On the [Cloudflare side](https://blog.cloudflare.com/deno-joins-cloudflare/) they explain a bit more in Cloudflares motives for buying Deno/sunsetting the runtime. Basically, they want to merge celld, an open source runtime for Durable Objects (basically, Cloudflare Workers with State), with the existing Cloudflare Workers runtime, workerd. What's kinda curious to me is that the celld runtime is only around 2 months old; Cloudflare says they're not buying out their competition, pointing to workerd being open source (and apparently being deployable by unnamed former clients), but it's pretty weird to both immediately buy out Deno for a newly launched product and to specifically cite that they're doing it for the one product tied to Cloudflare itself. It feels like there's a backroom conversation that's missing here, one we probably won't ever be privy to. --- wrt the Deno runtime itself, I wonder what this will mean for the yt-dlp project. A while ago they had to drop their own mini-JavaScript engine due to it becoming increasingly fragile and unmaintainable in the face of constant changes by Google, and just told people to install Deno as the "blessed" JavaScript engine. They'll probably have to start looking for a new recommended engine that meets those demands, which on their wiki probably will mean either node or QuickJS (as apparently Bun got deprecated due to excessive LLM usage - which got specifically highlighted over Deno, which also uses LLMs, but apparently to a lesser degree.) > — [noirscape on lobsters · 5 points, 1 comments](https://lobste.rs/s/8hauxs/deno_is_joining_cloudflare#c_zragav) **Source threads** - [lobsters](https://lobste.rs/s/8hauxs/deno_is_joining_cloudflare) · 18 points · 7 comments - [hackernews](https://news.ycombinator.com/item?id=50019911) · 184 points · 321 comments ## Similar posts on daily.dev - [Node.js creator liberates Durable Objects from Cloudflare](https://daily.dev/posts/node-js-creator-liberates-durable-objects-from-cloudflare-y12vjttqy) · DEVCLASS · 0 upvotes · 1 comments - [Introducing OpenWorkers – Self-hosted Cloudflare Workers in Rust](https://daily.dev/posts/introducing-openworkers-self-hosted-cloudflare-workers-in-rust-ag9dqgae1) · Hacker News · 34 upvotes · 3 comments - [Deno 2.9](https://daily.dev/posts/deno-2-9-8iwoplspk) · Deno · 139 upvotes · 18 comments --- Tags: [#javascript](https://daily.dev/tags/javascript), [#cloudflare](https://daily.dev/tags/cloudflare), [#deno](https://daily.dev/tags/deno) [View this post on daily.dev](https://daily.dev/posts/deno-is-joining-cloudflare-cxoxmkbrn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Deno is joining Cloudflare","url":"https://daily.dev/posts/deno-is-joining-cloudflare-cxoxmkbrn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/deno-is-joining-cloudflare-cxoxmkbrn"},"datePublished":"2026-10-09T13:00:27.424Z","dateModified":"2026-10-09T19:08:04.936Z","description":"The entire Deno team is joining Cloudflare, shifting future development toward a shared platform built on the Cloudflare Workers programming model and Durable...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/50c550e7a823d8db1da7f9ad30aae521?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/50c550e7a823d8db1da7f9ad30aae521?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Deno","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Deno","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/714ae5897f174e6c9c7ce75db092f9ce","url":"https://daily.dev/sources/deno"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/deno-is-joining-cloudflare-cxoxmkbrn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"javascript,cloudflare,deno","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Deno","item":"https://daily.dev/sources/deno"},{"@type":"ListItem","position":3,"name":"Deno is joining Cloudflare"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/deno-is-joining-cloudflare-cxoxmkbrn#faq","mainEntity":[{"@type":"Question","name":"Is Deno Deploy shutting down?","acceptedAnswer":{"@type":"Answer","text":"Yes, Deno Deploy will continue operating for six months before shutting down, as the Deno team joins Cloudflare and shifts focus to Cloudflare Workers. Migration support will be provided for paying customers moving their applications to Cloudflare Workers during this transition period. Developers planning a Deno Deploy migration can track platform shifts like this on daily.dev."}},{"@type":"Question","name":"Will the Deno runtime still be maintained now that the team joined Cloudflare?","acceptedAnswer":{"@type":"Answer","text":"The Deno runtime will receive monthly releases with bug fixes and security updates for one more year after the team's move to Cloudflare, after which active development from the original team will end. Deno remains open source, and the team welcomes others to continue its development independently. Teams relying on Deno in production can follow runtime support timelines like this on daily.dev."}},{"@type":"Question","name":"What is celld and how does it relate to Cloudflare Workers and Durable Objects?","acceptedAnswer":{"@type":"Answer","text":"Celld is a programming model built on top of Cloudflare Workers that lets developers build distributed applications with scaling built directly into the programming model rather than infrastructure each app must assemble itself. It combines the Deno team's work with Cloudflare's Workers and Durable Objects teams, and is especially aimed at supporting AI agent harnesses needing persistent state and WebSockets. Engineers evaluating distributed app platforms can compare approaches like celld on daily.dev."}}]} ```