Overview
Daytona supports multi-region deployment, allowing you to create sandboxes in different geographical locations. This enables you to:- Reduce latency by placing sandboxes close to your users or data
- Comply with data residency requirements
- Distribute workloads across regions for better availability
Region Selection
Specify Target Region
When creating a sandbox, you can specify the target region:Environment Variable Configuration
Set the default region using environment variables:Multi-Region Deployment
Deploy to Multiple Regions
Create sandboxes in different regions for the same application:Region Information
Check Sandbox Region
Every sandbox has atarget property indicating its region:
List Sandboxes by Region
Region-Specific Use Cases
Data Residency Compliance
Ensure data stays within a specific region:Low-Latency Access
Create sandboxes close to your users or data sources:Multi-Region Testing
Test applications across different regions:Region Configuration
Available Regions
Region availability depends on your organization’s configuration. Common regions include:us-east- US East Coastus-west- US West Coasteu-west- Europe Westeu-central- Europe Centralap-south- Asia Pacific Southap-northeast- Asia Pacific Northeast
Default Region
If no region is specified:- The client uses the region from
DAYTONA_TARGETenvironment variable - If not set, uses your organization’s default region
Snapshots and Regions
Snapshots are region-specific. When creating a snapshot, it’s stored in the specified region:Resource Quotas
Resource availability and quotas may vary by region. Your organization may have:- Different resource limits per region
- Different available machine types per region
- Region-specific pricing
Best Practices
- Choose the right region: Select regions based on user location, data location, and compliance requirements.
- Use consistent regions: Keep related sandboxes (e.g., frontend and backend) in the same region for low latency.
- Label by region: Use labels to track which region each sandbox belongs to.
- Plan for snapshots: Remember that snapshots are region-specific and plan accordingly.
- Monitor costs: Different regions may have different pricing structures.
- Test multi-region: If deploying globally, test your application in all target regions.
- Consider data transfer: Moving large amounts of data between regions can be slow and costly.
Region Configuration Reference
DaytonaConfig
Environment Variables
| Variable | Description | Example |
|---|---|---|
DAYTONA_TARGET | Default region for sandboxes | us-east |
DAYTONA_API_URL | API endpoint URL | https://app.daytona.io/api |
DAYTONA_API_KEY | API authentication key | your-api-key |
Related
- Resource Management - Configure resources by region
- Custom Images - Build images in specific regions
- Monitoring - Track regional sandbox usage