Multi-Region

TwinEdge Enterprise supports multi-region deployments for data residency, latency optimization, and disaster recovery.

Enterprise Feature

Multi-region deployment is available exclusively on Enterprise plans.

Overview

Multi-region enables:

• Data residency compliance: Keep data in specific geographic regions
• Reduced latency: Deploy closer to your devices and users
• Disaster recovery: Automatic failover between regions
• Regulatory compliance: Meet GDPR, data sovereignty requirements

Available Regions

Region ID	Location	Data Center
us-east	Virginia, USA	Azure East US
us-west	California, USA	Azure West US 2
eu-west	Ireland	Azure West Europe
eu-central	Germany	Azure Germany West Central
ap-southeast	Singapore	Azure Southeast Asia
ap-northeast	Japan	Azure Japan East

Region Configuration

Setting Organization Region

1. Go to Settings → Data Regions
2. View current region assignment
3. Click Change Region to migrate

Default Region

New organizations are assigned based on:

1. Account billing address
2. First data source location
3. Manual selection during signup

Viewing Region Status

{
  "organization_id": "org-123",
  "primary_region": "eu-west",
  "data_residency_enabled": true,
  "available_regions": ["us-east", "eu-west", "eu-central"],
  "endpoints": {
    "api": "https://api.eu-west.twinedgeai.com",
    "mqtt": "mqtts://mqtt.eu-west.twinedgeai.com:8883",
    "dashboard": "https://app.eu-west.twinedgeai.com"
  }
}

Data Residency

What Stays in Region

Data Type	Regional	Notes
Telemetry data	Yes	All sensor readings
Alerts	Yes	Alert history and rules
Dashboards	Yes	Dashboard definitions
User data	Yes	Profiles and preferences
ML Models	Yes	Trained models
Audit logs	Yes	All audit records
OTA packages	Yes	Firmware packages

What's Replicated

Data Type	Replicated	Notes
Organization settings	Yes	For failover
User credentials	Yes	For login continuity
Role definitions	Yes	RBAC configuration
API keys (metadata)	Yes	Key validation

Strict Data Residency

Enable strict mode to ensure no data leaves region:

1. Go to Settings → Data Regions → Compliance
2. Enable Strict Data Residency
3. Acknowledge limitations

Strict mode disables:

• Cross-region disaster recovery
• Global CDN for static assets
• Some third-party integrations

Region Migration

Planning Migration

Before migrating:

1. Review data volume: Large migrations take longer
2. Schedule downtime: Plan for maintenance window
3. Notify users: Communicate changes
4. Update integrations: API endpoints will change

Migration Process

1. Go to Settings → Data Regions
2. Click Change Region
3. Select target region
4. Review migration plan
5. Schedule migration time
6. Confirm migration

Migration Timeline

Data Volume	Estimated Time
< 100 GB	1-2 hours
100 GB - 1 TB	4-8 hours
> 1 TB	Contact support

During Migration

• Read-only mode: Data can be viewed, not modified
• Data ingestion paused: Buffer on edge devices
• Alerts active: Critical alerts still trigger
• Dashboard available: View historical data

Post-Migration

1. Verify data integrity
2. Update DNS records (if custom domain)
3. Update edge device configurations
4. Test all integrations
5. Resume normal operations

Multi-Region Architecture

Active-Passive

Default configuration:

• Primary region: Active, handles all traffic
• Secondary region: Standby, receives replicated data

┌─────────────────┐     Replication     ┌─────────────────┐
│   EU-WEST       │────────────────────>│   EU-CENTRAL    │
│   (Primary)     │                     │   (Standby)     │
│   Active        │                     │   Passive       │
└─────────────────┘                     └─────────────────┘
         ↑
    All Traffic

Active-Active (Available Soon)

For global deployments:

• Multiple active regions
• Geographic load balancing
• Local data processing

┌─────────────────┐                     ┌─────────────────┐
│   US-EAST       │<───────────────────>│   EU-WEST       │
│   (Active)      │    Replication      │   (Active)      │
└────────┬────────┘                     └────────┬────────┘
         │                                       │
    US Traffic                              EU Traffic

Edge Device Configuration

Regional Endpoints

Configure edge devices for specific regions:

# /opt/twinedge/.env
TWINEDGE_REGION=eu-west
TWINEDGE_API_URL=https://api.eu-west.twinedgeai.com
TWINEDGE_MQTT_URL=mqtts://mqtt.eu-west.twinedgeai.com:8883

Automatic Region Detection

Edge devices can auto-detect optimal region:

region_detection:
  enabled: true
  fallback_region: eu-west
  prefer_low_latency: true

Failover Configuration

Configure failover for edge devices:

regions:
  primary: eu-west
  failover:
    - eu-central
    - us-east
  health_check_interval_seconds: 60
  failover_threshold: 3  # Failed checks before failover

API Endpoints by Region

REST API

Region	Endpoint
US East	https://api.us-east.twinedgeai.com/v1
US West	https://api.us-west.twinedgeai.com/v1
EU West	https://api.eu-west.twinedgeai.com/v1
EU Central	https://api.eu-central.twinedgeai.com/v1

WebSocket

Region	Endpoint
US East	wss://api.us-east.twinedgeai.com/v1/ws
EU West	wss://api.eu-west.twinedgeai.com/v1/ws

MQTT

Region	Endpoint
US East	mqtts://mqtt.us-east.twinedgeai.com:8883
EU West	mqtts://mqtt.eu-west.twinedgeai.com:8883

Compliance Certifications

By Region

Region	Certifications
US East	SOC 2, HIPAA, FedRAMP
EU West	GDPR, ISO 27001, SOC 2
EU Central	GDPR, ISO 27001, German data protection

Data Processing Agreements

Request DPAs for compliance:

1. Go to Settings → Legal
2. Click Request DPA
3. Select regions
4. Receive signed DPA via email

Disaster Recovery

RPO and RTO

Tier	RPO	RTO
Enterprise Standard	1 hour	4 hours
Enterprise Premium	15 minutes	1 hour

• RPO: Recovery Point Objective (max data loss)
• RTO: Recovery Time Objective (max downtime)

Failover Testing

Schedule DR tests:

1. Go to Settings → Data Regions → DR Testing
2. Schedule test
3. Review test results
4. Update runbooks as needed

Manual Failover

In case of region failure:

1. Log in to backup region: https://app.eu-central.twinedgeai.com
2. Go to Admin → Disaster Recovery
3. Click Initiate Failover
4. Confirm action
5. Update DNS/integrations

Monitoring

Region Health

Monitor region status:

GET /api/v1/regions/health
Authorization: Bearer YOUR_API_KEY

Response:

{
  "regions": [
    {
      "id": "eu-west",
      "status": "healthy",
      "latency_ms": 45,
      "last_check": "2026-01-06T10:00:00Z"
    },
    {
      "id": "eu-central",
      "status": "healthy",
      "latency_ms": 62,
      "last_check": "2026-01-06T10:00:00Z"
    }
  ]
}

Replication Lag

Check data replication status:

GET /api/v1/regions/replication
Authorization: Bearer YOUR_API_KEY

Response:

{
  "primary_region": "eu-west",
  "replicas": [
    {
      "region": "eu-central",
      "lag_seconds": 5,
      "status": "synced",
      "last_sync": "2026-01-06T10:00:00Z"
    }
  ]
}

Best Practices

Region Selection

1. Choose based on data location: Where is most data generated?
2. Consider user location: Where are most users?
3. Check compliance requirements: What regulations apply?
4. Plan for growth: Can you add regions later?

Performance Optimization

1. Deploy edge devices regionally: Match device region to cloud
2. Use regional endpoints: Configure correct API URLs
3. Enable CDN: For static assets (if permitted)

Compliance

1. Document data flows: Know where data goes
2. Regular audits: Verify data residency
3. DPA in place: Ensure legal coverage
4. Staff training: Educate on regional requirements

Troubleshooting

High Latency

1. Verify device is using correct regional endpoint
2. Check network routing
3. Consider region migration if latency persists

Data Not Replicating

1. Check region health status
2. Verify replication is enabled
3. Check for network issues between regions
4. Contact support if persists

Migration Issues

1. Check available disk space
2. Verify network connectivity
3. Review migration logs
4. Contact support for assistance

API Reference

List Regions

GET /api/v1/regions
Authorization: Bearer YOUR_API_KEY

Get Region Details

GET /api/v1/regions/{region_id}
Authorization: Bearer YOUR_API_KEY

Set Organization Region

PUT /api/v1/organizations/current/region
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "region": "eu-west",
  "migration_time": "2026-01-15T02:00:00Z"
}

Next Steps

• SSO Configuration - Regional SSO setup
• Audit Logging - Regional log retention
• RBAC - Regional access control