Teams running on Deno Deploy should inventory their workloads now. Runtime users have a longer support window, but need a maintenance plan too.
What changed
On October 9, Deno announced that its entire team is joining Cloudflare. Future development will focus on a shared platform involving Workers and Durable Objects rather than a separate Deno runtime and hosting service. Deno says it will issue monthly bug-fix and security releases for the open-source runtime for another year. Deno Deploy will continue for six months before shutting down, with migration support for paying customers moving to Cloudflare Workers. JSR will continue operating as its infrastructure moves to Cloudflare.
Why it matters
If your product uses Deno Deploy, map its routes, storage, environment variables and integrations before selecting a migration path; test behavior and costs on the destination platform. If you use only the runtime, record its support horizon and assess long-term maintenance options. The Cloudflare work is a stated direction, not a feature set to assume is already available.
This is an Indus Creatives editorial briefing based on the original announcement. The artwork is generated for illustration and does not depict the reported event.
Read the original at Deno
