Data residency: Swiss-only mode

Laya Studio answers your questions on GPUs located in Switzerland, keeps its account database in Zurich, and never writes the content of a request to disk. Turn on Swiss-only mode and a request can never leave the country, not even as a failover.

Where does my request go?

Flip the switches to see what happens to a request in each case.

Authorization: Bearer lsk_live_…
x-laya-residency: ch

Per request: the x-laya-residency header

One switch per workspace (or the x-laya-residency: ch header per request) and requests are only ever answered in Switzerland. If the Swiss pool is unavailable you get an error, never a silent detour abroad. It is an add-on: +15% credits per request, still about 20% below Jev.

curl -i https://api.laya.studio/v1/systemone \
  -H "Authorization: Bearer $LAYA_API_KEY" \
  -H "Content-Type: application/json" \
  -H "x-laya-residency: ch" \
  -d '{"state":"Patient reports chest pain since this morning.","questions":{"urgent":{"type":"noul","instructions":"Does this need same-day attention?"}}}'

The header can only make a request stricter. If your workspace already has Swiss-only mode on, every request is Swiss-only whether or not you send it.

Per workspace: the dashboard toggle

To make every request from a workspace Swiss-only, open Dashboard → Settings → Data residency and switch it on. Owners and admins can change it. No code changes are needed.

Verify: the x-laya-region response header

Our primary inference pool runs on dedicated GPUs located in Switzerland. Every API response tells you where it was processed in the x-laya-region header.

HTTP/2 200
content-type: application/json
x-laya-region: ch

The free demo on the quickstart always runs Swiss-only, and shows this header next to every answer.

What we store, and where

• GPUs in Switzerland

  Our primary inference pool runs on dedicated GPUs located in Switzerland. Every API response tells you where it was processed in the x-laya-region header.

• Swiss-only mode

  One switch per workspace (or the x-laya-residency: ch header per request) and requests are only ever answered in Switzerland. If the Swiss pool is unavailable you get an error, never a silent detour abroad. It is an add-on: +15% credits per request, still about 20% below Jev.

• Zero content retention

  The text and questions you send are processed in memory and discarded when the answer is returned. They are never written to a database or log, and never used to train anything. One exception to know about: the optional chat agent (POST /v1/ask, the MCP ask tool, dashboard Chat) first passes your prompt to a third-party language model to plan the questions, in the US by default and in Switzerland under Swiss-only mode.

• Account data in Zurich

  Accounts, API keys (stored only as SHA-256 hashes), credit balances and usage metadata live in a Postgres database in the AWS Zurich region (eu-central-2).

• Minimal metadata, 30 days

  For billing and debugging we keep request metadata only — time, status, number of questions, latency — for 30 days. Daily totals are kept for invoicing.

• Encrypted end to end in transit

  All traffic uses TLS. The API gateway runs on Cloudflare’s network, which forwards requests encrypted and does not store their content; the GPU servers accept requests only from our gateway.

Built for sensitive data

No retention plus Swiss processing makes Laya Studio a fit for sensitive text such as patient messages, clinical intake notes, HR cases or financial correspondence — the kind of data that should not sit in a US AI provider’s logs.

• Patient message triage
• Clinical intake routing
• Pharmacovigilance signal screening
• HR and legal case sorting
• Insurance claim classification

Legal basis and limits

Retries under Swiss-only mode: see errors and retries.