Deno is joining Cloudflare
- ID
- 33624
- Status
- summarized
- Published
- 09 Oct 2026, 8:50 PM
- Fetched
- 09 Oct 2026, 10:28 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/deno-joins-cloudflare/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 6.0
- Created
- 09 Oct 2026, 10:28 PM
- Tags
- Audience
- developersvibe_codersdatabase_learnerssaas_founders
What happened
Cloudflare announced that the Deno team is joining Cloudflare and that workerd and celld will be merged, aiming to simplify self-hosting Workers and Durable Objects so the same primitives work in more places. Ryan Dahl and Kenton Varda frame the value around Durable Objects: each is a distributed singleton with its own SQLite database, single-threaded JavaScript execution, WebSocket handling, and synchronous local SQLite, so one DO per chat channel can shard data and connections. Dahl points to a separate Deno blog post for what happens to the Deno runtime; this post gives no timeline, pricing, or API details and cuts off while discussing running the model outside Cloudflare.
Why it matters
If you run Deno in production or build on Cloudflare Workers/Durable Objects, do not change migration or deployment plans from this post alone: the only concrete technical claim is a workerd+celld merge for self-hosting, while Deno runtime changes are deferred to Dahl's separate post. Wait for that Deno blog post before evaluating lock-in, pricing, or self-hosting; database learners can note the SQLite-per-Durable-Object sharding pattern, but it is not a new feature release here. There is no Malaysia-specific policy, funding, or infrastructure detail in the text.
Discussion angle
Would a merged workerd/celld self-hosted Durable Objects runtime actually reduce Cloudflare lock-in for a small SaaS, or does the value still depend on Cloudflare's managed Queues, KV, and Workflow API?