Data Residency

Regional workspace placement, immutable region selection, and practical planning considerations for regulated deployments.

Platform API workspaces are created in a specific deployment region and retain that region for their lifetime. Region is a placement boundary for Amigo-managed workspace services; it is not a blanket statement that every external system involved in a workflow processes data in that region.

Regional Endpoints

Deployment region	Platform API endpoint
US East	api.platform.amigo.ai
Canada Central	api-ca-central-1.platform.amigo.ai
EU Central	api-eu-central-1.platform.amigo.ai
Australia Southeast	api-ap-southeast-2.platform.amigo.ai

api.platform.amigo.ai is the default US endpoint, not a global router. To create or access a workspace in another supported region, use the endpoint assigned to that regional deployment. The Platform TypeScript SDK defaults to the US endpoint and supports a custom base URL for regional deployments.

Regional service availability can differ. Confirm that the channels, connectors, models, and supporting services required by your deployment are available in the target region before provisioning production workloads.

Workspace Placement

The deployment handling workspace creation determines the workspace's region. The API does not accept a client-selected region value during creation, and attempts to change the region later are rejected.

This contract prevents a metadata update from implying that data moved when no migration occurred. Amigo does not currently expose a self-service cross-region workspace migration. Organizations operating in multiple regions should plan separate workspaces and configuration promotion for each region.

What the Boundary Covers

Region placement applies to Amigo-managed workspace data and regional services that are provisioned for that workspace. Workspace authorization remains a separate control: region placement does not replace tenant isolation, role-based access, or resource-level permission checks.

Some workflows intentionally communicate with systems outside Amigo's managed regional boundary, including:

• Customer-hosted EHR, CRM, and integration endpoints
• Telephony, messaging, email, and identity providers
• Customer-selected model or infrastructure providers
• Operator browsers and customer applications

Those systems have their own processing locations, retention policies, and transfer mechanisms. Connector traffic also follows the location of the customer endpoint. Review the complete data flow rather than treating the workspace region as an end-to-end residency guarantee.

Multi-Region Planning

For organizations serving more than one jurisdiction:

1. Choose the regional endpoint before creating each workspace.
2. Keep patient and operational data in the workspace intended for that jurisdiction.
3. Promote agent configuration separately to each workspace.
4. Provision regional channel resources and connector credentials independently.
5. Validate every subprocessor and external integration against the intended data-flow boundary.

Entities and conversations in separate workspaces remain separate unless your own integration deliberately transfers or reconciles them. Do not assume automatic cross-region identity matching or configuration synchronization.

Compliance Planning

Region choice is one input to a compliance program, not a certification by itself. Applicable requirements depend on the organization, data, purpose, external systems, and contractual terms involved in the deployment.

Before production launch, confirm with Amigo:

• The services available in the requested region
• The managed-data boundary for each channel and connector
• Encryption, retention, deletion, and backup requirements
• Required contractual terms and subprocessors
• Any approved cross-border transfer mechanism

See Compliance and Audit for documented platform controls, and Deployment Model for workspace-isolation patterns.