Back to AI News
Simon Willison

Cloudflare Acquires Deno, Plans to End Runtime Development After One Year

Cloudflare is acquiring Deno and plans to build on celld, Deno's open source implementation of the Durable Objects pattern, to make workerd self-hosting a first-class way to run Workers apps. Cloudflare will support the Deno runtime for another year with monthly bug fixes and security updates, then end development, though Deno remains open source. Deno creator Ryan Dahl said he agreed with the decision, arguing Deno was pulled into the gravity well of Node compatibility and is no longer where he

AI Brief

It signals a major shift in the JavaScript runtime landscape and clarifies the future of Deno and the Durable Objects-style celld project.

Deno is joining Cloudflare

The Deno team released the first veRSIon of celld back in August - their open source implementation of the Durable Objects pattern from Cloudflare Workers.

Today, Cloudflare are acquiring Deno outright, with the goal of building on celld to "make workerd self-hosting a first-class supported way to build and run apps using the Workers programming model" (see the Cloudflare blog.)

The bad news is that Deno itself will not be maintained by Cloudflare beyond the next year:

We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates. After that year we will end our development of the Deno runtime. Deno will remain open source, and we welcome others who want to continue its development.

Deno (and Node.js) creator Ryan Dahl explained that decision in a comment on Hacker News:

It's a joint decision and I agree with it. I'm most invested in its success and have put the most work into it - and I no longer think it's where I can do the most important work. There are some good IDEas in Deno and it's well engineered - but it ultimately is not solving big problems. It has been sucked into the gravity well of node compatibility, which forces it to behave exACTly as Node does. Why reimplement Node? It works. Marginal performance or UX or security benefits are not enough.

I'm interested in building powerful new abstractions. celld has been working remarkably well, depending only on object stoRAGe for coordination and persistence. It is not just a slightly different API to interact with the file system or network - it's an entirely new model for server development.

My favorite feature of Deno has long been the permissions system, where you can run a Deno script and specify exactly which files and folders it can read and write to, and which network hosts it can access.

Node.js has a similar permissions model these days, added in Node v20.0.0 in April 2023 and declared stable in Node v22.13.0 in January 2025. They don't yet support allow-listing specific network hosts though - networking is either on or off.

Via Hacker News

Tags: cloudfront, javascript, nodejs, ryan-dahl, sandboxing, deno

Be the first to rate this article.

Comments & Questions (0)

Captcha
Please be respectful — let's keep the conversation friendly.

No comments yet

Be the first to comment!