Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Deploy's six-month closure window differs from the runtime's one-year maintenance period.
- The runtime receives monthly bug fixes and security updates for a year; the team's own development then ends. Source remains open for others to continue.
- Paid Deploy customers moving to Cloudflare Workers receive migration support, with application process, scope, and fees unspecified.
- JSR continues and moves infrastructure, while rusty_v8 remains supported. Identify actual dependencies before deciding which applications must migrate.
Two different timelines matter most to users
Ryan Dahl announced on Deno's website October 9 that the entire team is joining Cloudflare and directing future development into a shared platform. Existing users face separate transitions: Deploy runs six more months before closing; runtime support continues one year.
Only relative periods are given, without an exact closing day, hour, time zone, or phased schedule. Use six months as a planning window, not a confirmed calendar instant or proof the service already stopped.
The runtime will receive monthly bug fixes and security updates that year, after which the team ends its own development. It remains open source and others are welcome to continue it. Installed programs are not said to stop automatically.
Identify which layer your applications use
The runtime executes JavaScript and TypeScript on computers or servers; Deploy hosts applications. Local Deno usage and an API hosted on Deploy require different work despite the related names.
Hypothetical example: a team uses Deno for local builds and Deploy for a customer-query API. The scripts need security-update and maintenance planning; the API needs hosting migration. Updating a script version does not move the hosted API or its data.
Inventory Deploy applications, Deno programs in your own environments, and JSR packages through project lists, deployment records, and dependency configuration. Assign owners and purposes instead of requiring immediate rewrites of every dependency named Deno.
What support is promised for paid customers moving to Workers?
The announcement promises migration support for paid Deploy customers moving to Cloudflare Workers. It gives no application route, service scope, completion time, or fees, and does not promise equivalent free-account support, automatic migration, or free target usage.
Teams relying on support can inventory applications, execution modes, data dependencies, and questions, then ask about applicable arrangements. Keep the support promise separate from your own acceptance; an announcement is not a completed migration.
No universal migration command or compatibility guarantee is provided. Before choosing a target, check runtime interfaces, external connections, and state storage. Actual dependencies determine necessary code changes.
How do you plan a reversible migration?
First list request entry points, custom domains, environment-variable names, external APIs, and persistent data locations from deployment and operations records. Record relationships only; keep secrets, tokens, and user data in controlled environments, not public tickets or articles.
Second reserve small-scale validation for the target host. Isolated samples can check requests, errors, connections, and state reads and writes before comparing features, limits, and cost. This is a proposed order, not deployments or compatibility tests performed here.
Third define data migration, traffic switch, observation period, and rollback owner. While keeping the old service, check both sides for unhandled duplicate writes, then retire it after stability. Automatic data export or preservation is not promised; include backups yourself.
Why should JSR and rusty_v8 be considered separately?
JSR is a package registry. The announcement says it continues operating with infrastructure moving to Cloudflare, unlike Deploy's six-month closure. Follow its notices rather than treating it as already unavailable.
rusty_v8 provides V8 bindings for Rust. Support continues with future workerd integration. That integration is future work, not an announced released version; check later releases against your versions and needs.
The useful deliverable now is a layered inventory and migration ownership, not a guessed closing hour. Add exact deadlines, support processes, and compatibility guidance to the same plan when announced, without relying on unpublished automation or grace periods.
Sources
Frequently Asked Questions
Will free Deploy accounts get the same personal migration support?
Only paid customers moving to Workers are explicitly promised support. Equivalent free-account help, application process, and scope need further official explanation.
Must every user choose Cloudflare Workers?
No universal requirement is stated. The announcement specifies support for paid customers moving there. Evaluate other targets by compatibility, data migration, and cost.
Are Workers and Durable Objects integrations delivered already?
The announcement describes future joint work with those teams, including rusty_v8 and workerd integration. It gives no launch date or universal account-availability guarantee.