On October 9, Deno announced that its team is joining Cloudflare. For developers running Deno applications, the immediate planning problem is the difference between two deadlines: Deno Deploy will operate for another six months before shutting down, while the runtime will receive monthly bug fixes and security updates for another year. The team will then end its runtime development; the code will remain open source. Deno’s announcement sets out both commitments.
That gives a hosted application less time than a local script or a service running on infrastructure you control. Treating every Deno dependency as one migration project obscures the part with the earliest deadline.
My practical reading is to start with a deployment inventory. For each application, record where it executes, where persistent data lives, how scheduled work runs, and how traffic reaches it. Assign an owner and a migration rehearsal date to anything hosted on Deploy.
An illustrative example: a Deno command-line tool used in CI and a customer-facing API hosted on Deploy might share a language and dependencies. Their next decisions differ. The tool needs a maintenance plan for its runtime. The API needs a tested destination, a data transition, and a traffic cutover within the shorter hosting window.
Deno says paying Deploy customers will receive migration support toward Cloudflare Workers. That makes Workers a destination to evaluate. The announcement does not establish that every application’s storage, permissions, and execution behavior will transfer unchanged. A useful rehearsal should exercise a representative request and its state changes, then test recovery when the move fails.
Cloudflare also describes plans to combine workerd and celld to improve self-hosting of Workers and Durable Objects. Its announcement presents that as development ahead. I would evaluate the capabilities available today before making that future work a dependency of the migration.
The useful action this week is small: identify which applications depend on Deploy and schedule one migration rehearsal. That produces evidence for choosing a destination while there is still time to change the plan.