Laya Studio
Get an API keyGet a key
Swiss hostingAnswered on GPUs in Switzerland. Nothing you send is stored.
ProductTry it liveQuickstartSwitch from JevPricingStatusAPI reference
LearnWhat is Laya?What is Jev?Fast vs slow AITrustworthy confidenceNo made-up answersAll explainers
CompareLaya vs JevLaya vs ChatGPT-style classifiersJev alternativesSupport triageContent moderationMultilingual intake
ResourcesGlossaryAll use casesBlogFAQ
Pricing
Log in

Status

Operational (degraded redundancy)

Checked . Every reload runs a fresh health check against each GPU pool.

Answering, reduced redundancyRegion: Switzerland · liveCheck again

Components

Each GPU pool is probed live when this page loads.

API gateway (Cloudflare edge)Global edgeOperational:Serving
Primary GPU poolSwitzerlandOperational:Ready · 360 ms probe
Cloud GPU pool (autoscaling)European UnionDown:Unavailable — traffic fails over automatically

Routing mode: auto. Requests fail over between GPU pools automatically; a pool being down only reduces redundancy.

How failover and Swiss-only mode work

Two rules decide where a request is answered. Here is what happens when a pool has a bad minute.

Default: fail over, keep answering

  1. Your request
  2. Swiss GPU pool
  3. If busy or down: cloud pool

Requests go to the primary pool in Switzerland first. If it is saturated or unhealthy, the gateway retries on the autoscaling cloud pool, so the answer still arrives. Every response names where it was processed in the x-laya-region header.

Swiss-only mode: never leave the country

  1. Your request
  2. Swiss GPU pool
  3. If down: a clear error

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.

More on Swiss data residency