Data Regions | Lakera API documentation

Lakera Guard allows you to control where your API requests are processed and where your logs are stored. These are two independent settings, giving you flexibility to optimize for both latency and compliance.

Processing Regions

The processing region determines where Lakera Guard runs its detectors on your screening requests. You control this by choosing which API endpoint to send requests to.

Available Endpoints

Region	Endpoint
US (multi-region)	`https://us.api.lakera.ai`
US East (N. Virginia)	`https://us-east-1.api.lakera.ai`
US West (Oregon)	`https://us-west-2.api.lakera.ai`
EU (Ireland)	`https://eu-west-1.api.lakera.ai`
Asia (Singapore)	`https://ap-southeast-1.api.lakera.ai`

It is your responsibility to use the correct endpoint for your desired processing region. Lakera does not automatically route requests to a specific region - requests are processed wherever they are sent.

Storage Region

The storage region determines where your Guard logs are persisted. You can configure this in the Lakera Dashboard under Settings > Data regions using the storage_region setting.

The default storage region is EU.

The storage region is set when the organization is created and cannot be changed afterwards. If you need logs stored in multiple regions, use separate organizations. Contact Lakera support for help with initial setup.

Allowed Processing Regions

The allowed_processing_regions setting lets you restrict which regions are permitted to process your requests. This is an enforcement mechanism, not a routing control.

If a request is sent to an endpoint in a region that is not in the allowed list, the gateway rejects it with a 4xx error.

You can configure this in Settings > Data regions in the Lakera Dashboard. If not set, all regions are allowed by default.

Platform Logs

The region field shown in the platform logs refers to the processing region, which can differ from the storage region. If you see unexpected region values in your logs, verify that your application is using the correct API endpoint.

Examples

Process and store everything in the EU

To guarantee that all requests are processed and stored in the EU:

Set allowed_processing_regions to ["eu-west-1"]
Keep the default storage_region (EU)
Point your application to https://eu-west-1.api.lakera.ai

With this configuration, any requests sent to other regions (e.g. us-east-1.api.lakera.ai) will be rejected with a 4xx error.

Global processing with US storage

To allow processing in any region (for lower latency) while storing all logs in the US:

Leave allowed_processing_regions unset (defaults to all regions)
Set storage_region to US
Use whichever regional endpoint provides the lowest latency for your application