What does "worldwide working" mean for a cloud account?

"Worldwide working" means the account has no geographic restrictions — you can launch resources in any supported region globally. Some accounts (particularly US/UK/CA accounts) are limited to specific regions for compliance reasons.

Why are some accounts US/UK/CA only?

US/UK/CA region restrictions are applied to accounts sourced through specific channels. These accounts still have full service access within those regions — they're often the highest-tier regions for performance and compliance.

Can worldwide accounts be used for APAC deployments?

Yes. Worldwide accounts can deploy to AWS ap-southeast-1 (Singapore), GCP asia-east1 (Taiwan), Azure Japan East, and other APAC regions without restrictions.

Is there a performance difference between regional and worldwide accounts?

No performance difference — the account restriction is geographic access only. A worldwide account deploys the same infrastructure as a US/UK/CA account when launched in US/UK/CA regions.

Do worldwide accounts support compliance frameworks like GDPR?

Yes. You can deploy resources in EU regions (AWS eu-west-1, GCP europe-west4, Azure West Europe) using worldwide accounts, satisfying GDPR data residency requirements.

🌍

Worldwide Cloud Accounts

Worldwide access accounts have no geographic restrictions — they can deploy resources in any available region globally. Some cloud accounts are limited to specific regions (e.g., US/UK/CA only). Worldwide accounts are suitable for global deployments across multiple continents.

Not all cloud accounts support all regions. Our worldwide-access accounts allow deploying to any supported region without geographic restrictions. Key use cases: global CDN origins, multi-region failover, latency-optimized deployments for international users, and compliance with regional data residency requirements.