Cloudflare acquires Deno to simplify self-hosting for Workers and Durable Objects

Cloudflare announced that the Deno team is joining the company, marking a strategic shift to expand where developers can deploy serverless code. According to first-hand research published by Cloudflare, this integration is designed to radically simplify self-hosting for Workers and Durable Objects.

The primary goal of this consolidation is to allow developers to use the same primitives in more places. By bringing the Deno team under the Cloudflare umbrella, the company intends to bridge the gap between its managed cloud services and self-hosted infrastructure. This change addresses a long-standing limitation for users who want the consistency of the Cloudflare runtime but require the control or compliance features of self-hosted environments.

Context and background

Cloudflare Workers and Durable Objects are core components of the company’s serverless platform. Workers allow developers to run JavaScript, WebAssembly, and other languages at the edge, while Durable Objects provide scalable, consistent state storage. Historically, these services have been tightly coupled with Cloudflare’s global network.

The decision to integrate Deno stems from the technical relationship between the two projects. Deno, the secure runtime for JavaScript, TypeScript, and WebAssembly, was created by Ryan Dahl, the original creator of Node.js. Cloudflare has long used a modified version of the V8 engine and Deno’s underlying technologies to power its Workers runtime. By formally acquiring the team, Cloudflare seeks to unify the development efforts and reduce friction for users moving code between managed and self-hosted setups.

Who is affected

This development primarily affects developers and engineering teams that utilize Cloudflare’s serverless offerings. Specifically, it targets users who have previously been constrained by the inability to self-host Workers with the same ease and feature parity as the managed service.

Organizations that require data residency, specific compliance standards, or hybrid cloud architectures will likely see the most immediate benefit. These entities often face challenges when trying to replicate the edge-computing experience of Cloudflare Workers on their own infrastructure. The integration promises to streamline this process, allowing for a more consistent development experience regardless of where the code is ultimately deployed.

What should you do?

Developers should review their current deployment strategies for Workers and Durable Objects to identify any friction points related to self-hosting. Teams should monitor Cloudflare’s engineering blogs and release notes for updates on the timeline for self-hosting support. It is advisable to evaluate whether current workloads could benefit from the expanded portability of the runtime.

What to do and how to stay safe: Cloudflare

• Review current serverless architectures to identify workloads that could benefit from self-hosting capabilities.
• Monitor official Cloudflare announcements for technical documentation on deploying Workers in self-hosted environments.
• Evaluate compliance and data residency requirements to determine if self-hosting offers a competitive advantage for specific projects.
• Test the compatibility of existing codebases with the unified runtime primitives once beta tools or documentation are released.

Step-by-step guide: Cloud Misconfiguration Response: Containment, Recovery and Prevention Steps

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is the main benefit of Deno joining Cloudflare?

The main benefit is the ability to radically simplify self-hosting for Workers and Durable Objects, allowing developers to use the same primitives in more places.

Does this mean Cloudflare is shutting down its managed services?

No, the announcement focuses on expanding where developers can use the primitives, specifically enabling self-hosting, not replacing the managed cloud offering.

Who is the Deno team?

The Deno team is the group of developers responsible for the Deno runtime, which is now joining Cloudflare to help unify the development experience for Workers.