Skip to main content
Truefoundry’s globally distributed gateway is deployed across multiple regions and cloud providers to ensure high availability, low latency, and resilience against regional or cloud provider disruptions. The global gateway URL is https://gateway.truefoundry.ai.
gateway.truefoundry.ai is the unified endpoint for both the AI Model Gateway and the MCP Gateway.Whether you are routing LLM inference requests (OpenAI-compatible API, etc.) or connecting to MCP (Model Context Protocol) servers, all traffic goes through the same globally distributed infrastructure. This means MCP Gateway deployments benefit from the same multi-region, multi-cloud availability described on this page.
Architecture diagram showing the Control Plane in Ireland (Europe) managing configuration, with Gateway Planes handling LLM and MCP traffic across 14 global regions connected via NATS

Features

  1. Globally Distributed: Deployed across more than 12 regions around the globe and across 3 multiple cloud providers for maximum availability while minimizing latency.
  2. Automated Failover: All traffic is routed to the nearest gateway for minimum latency. In case of regional downtime, traffic is automatically routed to closest healthy regions ensuring uninterrupted service.
  3. Multi-Cloud Deployment: Distributed across multiple cloud providers to be tolerant to cloud provider-specific disruptions.
  4. Data Encryption: Data is encrypted at rest and in transit.
  5. Compliance: Truefoundry Infrastructure is SOC2, ISO27001, GDPR, and HIPAA compliant

Architecture

The SAAS global deployment follows the same Gateway Plane Architecture used across all Truefoundry deployments. It consists of two key components:
  • Control Plane — Manages all gateway configuration including models, users, teams, virtual accounts, rate-limiting, and routing configs. The SAAS control plane is hosted in Ireland (Europe).
  • Gateway Planes — Stateless, horizontally scalable gateway instances that handle all production traffic (LLM requests, MCP requests, etc.). These are deployed across the regions listed in the Regional Deployments section below.
The gateway planes subscribe to the control plane for configuration updates via NATS and perform all authentication, authorization, rate-limiting, and load-balancing checks in-memory with no external calls in the request path. For a detailed breakdown of the request flow, performance benchmarks, and FAQs, see the Gateway Plane Architecture page.
The specific regions and locations where gateway planes are deployed are subject to change based on Truefoundry’s internal infrastructure needs. Regions may be added, removed, or relocated without prior notice.

Global Deployment

For most use cases, we recommend using the global endpoint which automatically routes to the nearest healthy gateway:
DeploymentGlobal Endpoint
Global (Auto-routed)https://gateway.truefoundry.ai
Using the global URL (https://gateway.truefoundry.ai) is recommended as it automatically routes your requests to the nearest healthy gateway instance based on your geographic location to give you the minimum possible latency.

Regional Deployments

Each of the different gateway regions also have their own URLs as mentioned below. While you can use them for testing, we do not recommend pointing to them in production since they can be changed at any point by us if we are shifting regions or adding new regions.
Please do not use the regional endpoints in production since they are subject to change at any point without notice.We recommend using the global endpoint (https://gateway.truefoundry.ai) for production use. or the region specific endpoint described in the Multi-regional Deployments section.
Physical LocationRegional Endpoint
North Virginia, United States - (ORF)https://orf.gateway.truefoundry.ai
Toronto, Canada - (YYZ)https://yyz.gateway.truefoundry.ai
San Francisco, United States - (SFO)https://sfo.gateway.truefoundry.ai
Dallas, Texas, United States - (DFW)https://dfw.gateway.truefoundry.ai
London, United Kingdom - (LHR)https://lhr.gateway.truefoundry.ai
Madrid, Spain - (MAD)https://mad.gateway.truefoundry.ai
Gavle, Sweden - (GVX)https://gvx.gateway.truefoundry.ai
Sao Paulo, Brazil - (GRU)https://gru.gateway.truefoundry.ai
Cape Town, South Africa - (CPT)https://cpt.gateway.truefoundry.ai
Doha, Qatar - (DIA)https://dia.gateway.truefoundry.ai
Mumbai, India - (BOM)https://bom.gateway.truefoundry.ai
Singapore, Singapore - (SIN)https://sin.gateway.truefoundry.ai
Canberra, Australia - (CBR)https://cbr.gateway.truefoundry.ai
Sydney, Australia - (SYD)https://syd.gateway.truefoundry.ai

Multi-regional Deployments

Multi-regional endpoints automatically route your requests to the closest healthy gateway within a specific geographic region. If all regional locations are unavailable, traffic is routed to the designated fallback regions.
RegionMulti-regional EndpointPrimary LocationsFallback Locations
United Stateshttps://us.gateway.truefoundry.aiNorth Virginia (ORF), San Francisco (SFO), Dallas (DFW)Toronto, Canada (YYZ)
Europehttps://eu.gateway.truefoundry.aiLondon (LHR), Madrid (MAD), Gavle (GVX)Doha, Qatar (DIA)
Australiahttps://au.gateway.truefoundry.aiSydney (SYD), Canberra (CBR)Singapore (SIN)

Gateway Status Monitoring

Check Gateway Status

To track the status of each gateway deployment and receive real-time updates on service availability, visit our status page: Gateway Status Page: status.truefoundry.com You can expand the AI Gateway section to see per-region uptime:
AI Gateway expanded view showing per-region uptime for each gateway deployment

Subscribe to Status Updates

Stay informed about gateway availability by subscribing to status notifications:
  1. Visit the Gateway Status Page
  2. Click the Get Updates button in the top right
  3. Choose your preferred notification method:
    • Email notifications
    • RSS Feed
    • On a custom webhook
Truefoundry status page with the Get Updates button highlighted in the top right

IP Allow List

If you need to allow traffic from the Truefoundry Globally Distributed SAAS gateway to reach your infrastructure, you will need to add the gateway NAT IPs to your firewall allow list.
The complete and up-to-date list of gateway NAT IPs is available as a JSON file. Always use this JSON as the source of truth for your firewall configuration, as IPs may be added or changed when new regions are deployed.JSON endpoint: https://assets.production.truefoundry.com/nat_ip.json