The Deno Team Is Walking Into Cloudflare

By Siam Sukkhee Trading Co., Ltd — 2026-10-09 — Hacker News

Deno was supposed to be the better version. When Ryan Dahl built it years back—the same person who created Node.js, mind you—the pitch was clean: JavaScript done right. No more assembling your own infrastructure piece by piece. Simple modules, real security guarantees, a complete toolchain out of the box.

It didn't quite work that way.

The team spent years questioning the foundations. How should modules be distributed? What security can a JavaScript runtime actually provide? What belongs in a complete toolchain? They built something that worked, but the success became a problem. Users wanted Deno's improvements while still plugging into the existing JavaScript ecosystem. So they spent more time building compatibility with Node.js than building Deno itself.

Making things simple for users meant hiding complexity underneath. Operate that platform for a few years and you realise how much complexity remains hidden. That's when Dahl started thinking about something else: celld. Building on top of Cloudflare's Workers, it lets developers assemble distributed applications from the start. The scaling lives in the programming model now, not in infrastructure each application has to bolt together on its own.

That progression—Deno to Deno Deploy to celld—is why today makes sense. Or at least, that's the story.

Today the entire Deno team joined Cloudflare. All of it. They're folding themselves into the Workers and Durable Objects teams, planning to merge Dahl's celld system with Cloudflare's workerd runtime. One platform. One bet.

Which means Deno the runtime gets a sunset. The community can fork it, maintain it, resurrect it if they want. But Cloudflare's not maintaining it anymore. Deno Deploy shuts in six months.

Actually, that's not quite right. It's not dead—it's being migrated. Paying customers get moved to Cloudflare Workers. JSR, the package registry Deno built, stays alive under Cloudflare's roof. The infrastructure doesn't vanish; it just stops being Deno's problem.

What excites Dahl now—what he's genuinely excited about—is AI agents running at scale. Durable Objects have the right properties: cheap serverless execution, persistent state, WebSockets, a high-level interface. Build agent harnesses on that. Run them on your own infrastructure instead of begging Cloudflare for resources. That's the move.

People who've bet their businesses on Deno have some decisions to make in the next year. People who haven't started yet probably shouldn't. But for Dahl and the team, the cage built itself. The way forward wasn't Deno anymore. It was bigger. Cloudflare bigger.

Source: "Deno is ending its separate runtime and hosting roadmap to help Cloudflare address a specific gap: running Workers and Durable Objects across self-managed infrastructure." — RuntimeWire

Tags: zinc smelting industry news