For years, we’ve been working to make building server software simpler. We questioned how modules could be distributed, what security guarantees a JavaScript runtime could provide, what belonged in a complete toolchain, and how easily an application could be distributed as a standalone executable. Compatibility with Node.js became an important part of that work too: our users wanted the Deno improvements while continuing to plug into the existing JS ecosystem. The team and community built a runtime that brought these capabilities together and challenged assumptions about what JS development could look like.
\nToday we’re announcing that the entire Deno team is joining\nCloudflare to take that work further.
\nOur ambition has always extended beyond the runtime. I wrote about this in my\nJavaScript Containers blog\npost: compute, storage, and communication working together, without every\napplication assembling its own infrastructure.
\nWith Deno Deploy, we took another step towards that\ngoal. We wanted to make running applications as straightforward as possible. But\nbuilding and operating Deploy also showed us how much complexity remained\nunderneath that developer experience. I wanted to simplify that layer, too.
\nThis led to celld. Building on the\nCloudflare Workers programming\nmodel, celld lets developers build distributed applications from the start while\nmaking the system simple to operate. What excites me greatly is that the scaling\nis built into the programming model, rather than infrastructure each app has to\nassemble itself.
\nThe progression from Deno to Deno Deploy to celld explains why this move makes\nsense to us. At Cloudflare we’ll combine our work with that of the Workers and\nDurable Objects teams. We\nwant to make this programming model the default way to build servers, whether\nyou run on Cloudflare’s network or your own infrastructure.
\nJoining also means choosing where to focus our effort. We’ve decided to put our future development work into this shared platform rather than continuing to develop a separate runtime and hosting service. We know this is a consequential change for people who have built on Deno.
\nTo everyone who contributed code, built businesses on Deno, reported problems, and trusted our direction: thank you. Here’s what this means concretely:
\nWe will support the Deno runtime for
another year with monthly releases containing bug fixes and security updates.\nAfter that year we will end our development of the Deno runtime. Deno will\nremain open source, and we welcome others who want to continue its\ndevelopment.
JSR will continue operating, with its infrastructure moving
to Cloudflare.
rusty_v8 and work toward integrating it intoworkerd .The need for better abstractions is especially acute with AI. Durable Objects bring together capabilities that are particularly useful for agent harnesses: inexpensive, serverless execution, persistent state, WebSockets, and a high-level JavaScript interface. This is what I’m most excited to explore and why celld focuses on Durable Objects.
\nKenton Varda and I explain more in our\njoint post on the Cloudflare blog.
","headings":[{"level":1,"text":"Deno is joining Cloudflare","id":"deno-is-joining-cloudflare"}]}}