Geo-Aware LLM Request Routing on the Einstein Generative AI Platform
The Einstein generative AI platform routes large language model (LLM) requests to
servers that are closest to where your Einstein generative AI platform instance is located.
Geo-aware routing includes LLM API requests made by Einstein generative AI features that use the
Einstein generative AI platform.
Required Editions
Available in: Enterprise, Performance, and Unlimited
Editions with an Einstein for Sales, Einstein for Platform, Einstein for Service,
Einstein 1 Service, or Einstein GPT Service add-on. To purchase add-ons, contact
your Salesforce account executive.
Supported Models
Geo-aware routing is available to these models,
provided that the models are available in the relevant regions.
OpenAI models (such as GPT-4 Omni). These geo-aware models use OpenAI or Azure OpenAI to
service LLM requests. The same underlying model is used by OpenAI and Azure OpenAI. See
Geo-Aware Routing for OpenAI and Azure OpenAI.
Anthropic models (hosted on Amazon Bedrock)
Availability
Geo-aware routing is available to:
AI agents
Salesforce applications and features that use OpenAI and Anthropic models through the
Einstein generative AI platform
Customers who use OpenAI and Anthropic models through Models API or Prompt Builder.
To find out whether geo-aware routing is enabled for any specific Salesforce AI
feature, refer to its documentation or contact your Salesforce account
executive.
Proximity and Routing
Proximity to the nearest LLM server is determined
by the region in which your Einstein generative AI platform instance is located. If you
enabled the Einstein generative AI platform on or after June 13, 2024, then your Einstein
generative AI platform region is the same as your Data 360 region (Data 360: Data Center Locations). Otherwise, contact your Salesforce
account executive to learn where it’s provisioned.
Routing in the Models API
If you use the Einstein generative AI
platform directly through Models API, then it's recommended that you use model API names for
geo-aware models.
To track whether an Einstein feature supports
geo-aware LLM request routing, see the feature's documentation.
Geo-Aware Routing for OpenAI and Azure OpenAI A geo-aware model, such as GPT 4 Omni, uses OpenAI or Azure OpenAI to service LLM requests. The same underlying model is used by OpenAI and Azure OpenAI.
Geo-Aware Routing for Anthropic LLM requests for Anthropic on AWS Bedrock are routed to the nearest AWS data center where a model endpoint is available.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.