Skip to main content

Overview

The data region of an organization tells Galtea where it may process the data of that organization, such as the requests to model providers that run evaluations, generate test data and simulate conversations. An organization has one of two regions:
  • Global is the default. Galtea processes your data with its normal routing.
  • EU only asks that the processing of your data stays in the European Union. “EU-only processing” here has the meaning described in European models, EU-only processing, and the difference between them. It is a rule about where the processing happens, not about who the model provider is.
The region applies to the model calls that Galtea makes for your organization through its LLM gateway: the jobs of the AI services (test generation, evaluations by a judge model, conversation simulation, metrics, reports and the platform assistant) and the model calls of the platform API itself. The region of the organization that owns the data decides, not the region of the person who starts the job. A request that names no product yet, such as product setup, the form check, a cURL import, the model settings check and the platform assistant, uses the region of the signed-in user’s organization. If an EU-only call cannot be served in the EU, it fails instead of running elsewhere. A job fails. The way an API request fails depends on the call:
  • A model call that the API makes itself answers 503. This covers product setup, the form check, a cURL import, the model settings check, the test name and the production trace insights.
  • A request that the API passes to another AI service answers 502. This covers the metric completion, update and conversion calls, and the next simulated user message.
  • The platform assistant chat answers 200 and sends an error event with the code upstream_failure.
The region does not cover the calls that Galtea sends to your own endpoint, and it does not cover the public docs assistant, which has no organization. It does not yet cover the text-to-speech and telephony providers of voice tests, which synthesize and carry the audio. Speech-to-text already runs on an EU endpoint. It does not yet cover the decision model: the evaluations of classifier metrics, their “Test on a sample” preview and the applicability check run with the normal routing of the deployment, whatever the region.
The data region is an Enterprise feature. Contact support@galtea.ai to enable it for your organization.
The region does not change where Galtea stores your data. Storage stays in eu-west-1 for shared SaaS, in the region you choose for a private tenant, and in your own infrastructure when self-hosted. See Security assurance. The region covers data processing only.
This feature is not live yet. A deployment turns it on with a setting that is off by default. While the setting is off, the organization settings page shows no region and a request to change the region is refused.

Who can see and change it

  • Owners can see the current region on the organization settings page. They cannot change it.
  • Galtea staff change the region on request. Ask support@galtea.ai to switch it.
  • The region can only be changed on an organization with an active Enterprise subscription. An organization that is frozen must be unfrozen first.

What a switch means

The dashboard asks for a confirmation before it switches the region. Galtea records each change of value in the audit log, with the old and the new value. The two changes mean the following:
  • Global to EU only: from then on, Galtea processes your organization’s data in the EU only. Check that the models you use are available in an EU deployment, because a model that is not available there cannot serve your organization.
  • EU only to global: Galtea goes back to its normal routing, which may process your data outside the EU.
A change applies to processing that starts after it. It does not change processing that already ran.