Data Regions
Data residency options, cloud regions, and business continuity measures.
Available Regions
Future AGI operates on Amazon Web Services (AWS) infrastructure. All data processing and storage occurs within your selected region.
| Region | AWS Region | Availability |
|---|---|---|
| United States | us-east-1 (Ohio) | All plans (default) |
| European Union | eu-west-1 (Frankfurt) | Enterprise plans |
Your region is selected during organization creation and determines where all trace data, evaluation results, datasets, and project metadata are stored and processed. Data does not leave your selected region for processing purposes.
Connecting SDKs to Your Region
When initializing the Future AGI SDK, specify your region endpoint:
# US region (default)
fi.init(api_key="your-api-key", base_url="https://api.futureagi.com")
# EU region (Enterprise)
fi.init(api_key="your-api-key", base_url="https://api.eu.futureagi.com")All SDK telemetry, API calls, and dashboard access will route through your designated regional endpoint.
Choosing a Region
Consider the following when selecting your data region:
- Latency — Choose the region closest to your application infrastructure to minimize trace ingestion latency and dashboard load times.
- Compliance — Organizations subject to GDPR, Schrems II, or other data residency requirements should select the EU region to ensure all data remains within the European Union.
- Team location — Dashboard performance is optimized when your team accesses Future AGI from the same geographic area as your data region.
Region migration is available upon request for Enterprise customers. Contact your account team to coordinate a migration plan.
Business Continuity
Future AGI infrastructure is designed for high availability and resilience:
- Multi-AZ deployment — All critical services are deployed across multiple AWS Availability Zones within each region, providing fault tolerance against individual data center failures.
- Uptime SLA — We maintain a 99.9% uptime SLA for all paid plans, backed by service credits.
- Recovery objectives:
- RPO (Recovery Point Objective): 10 minutes — in the event of a disaster, no more than 10 minutes of data may be lost.
- RTO (Recovery Time Objective): 12 hours — full service restoration within 12 hours of a major incident.
- Backups — Automated daily backups of all databases and storage layers, retained for 30 days. Backups are encrypted and stored within the same region as the source data.