§ Global Expansion & Region Scaling
Global Expansion Report
Region-aware architecture with per-region shard counts, tenant/partner counts, routing policies, and marketplace activity. Readiness assessment for new regions across EU, APAC, and LATAM.
6
Live regions
52
Total nodes
8
Tenants
5
Partners
8
Total shards
Region readiness summary
6
Live regions
0
Provisioning
3
Planned
Regions by continent
Asia Pacific
Europe
Latin America
North America
Region-aware onboarding
How region-aware onboarding works
Developers, advertisers, and partners select their region during onboarding. The system provisions resources in the nearest coordinator shard, configures routing policies for that region, and sets up marketplace presence. Privacy-tier enforcement ensures PHI-local-only tenants are restricted to their region. Failover routing policies redirect traffic to neighboring regions during outages.
| Developer onboarding | Region selection → nearest shard → node registration in that shard |
| Advertiser onboarding | Region selection → ad targeting rules default to that region |
| Partner onboarding | Region selection → integration config scoped to that region |
| Tenant provisioning | Region selection → coordinator shard mapping → quota enforcement |
| Privacy enforcement | phi_local_only tenants restricted to same-region nodes only |
| Failover routing | Each region has a failover_region in its routing_policy |
Expansion readiness — new regions
EU expansion
| Regions planned | eu-west (live), eu-central (live), eu-north (planned) |
| Data sovereignty | GDPR compliance required — privacy_tier: enhanced minimum |
| Shard allocation | 2 shards per region (10K nodes capacity) |
| Partner readiness | EU-based GPU vendors and cloud connectors needed |
| Estimated launch | Q1 2026 — pending partner agreements |
APAC expansion
| Regions planned | ap-south (live), ap-northeast (live), ap-southeast (planned) |
| Latency budget | 300ms intra-region, 800ms cross-region |
| Shard allocation | 3 shards for ap-southeast (high density expected) |
| Partner readiness | APAC cloud connectors and AI model providers needed |
| Estimated launch | Q2 2026 — pending data center provisioning |
LATAM expansion
| Regions planned | sa-east (planned) |
| Infrastructure | New coordinator deployment required |
| Shard allocation | 1 shard initial (5K nodes capacity) |
| Partner readiness | LATAM cloud connectors and monitoring tools needed |
| Estimated launch | Q3 2026 — pending infrastructure investment |