Trust centre · Data residency
Data residency & sovereignty
What runs where, on whose hardware, and the commitment that customer traffic never leaves the EEA — with a region header on every response so you can check it yourself.
Placement
What runs where
| Layer | Where it runs |
|---|---|
| Inference | NVIDIA DGX Spark systems AxForge owns and operates, in Sweden (eu-se-1 · Stockholm). eu-es-1 · Málaga is live for the platform; more EU regions are in deployment. |
| Facility | A controlled-access facility in Sweden. We publish no further physical detail; detailed physical and technical measures live in a private TOMs annex, available under NDA/DPA. |
| EU edge | Hetzner Online GmbH (Germany): TLS termination, reverse proxy and this static site. TLS 1.3. |
| Edge → inference | Encrypted private WireGuard tunnel between the EEA edge and the inference hardware. |
| Account, billing & log data | Held and processed in the EEA. Retention limits per the retention schedule. |
Ownership
Owned hardware, not rented compute
AxForge inference runs on machines AxForge bought, owns and operates — not resold hyperscaler capacity, and no third-party compute for inference. Serving is transparent: named models on named machines (NVIDIA DGX Spark, GB10), so you know exactly what runs where. The model catalogue lists what is served; the subprocessor register lists who else touches traffic — today, only the edge layer.
Boundary
No processing outside the EEA
There is no outside-EEA processing and no outside-EEA failover — not as a fallback, not under load, not during an outage. The commitment, in full: If all EEA capacity is unavailable, requests queue or fail — they are never routed outside the EEA.
Data flow
The path of a request
Customer → EEA edge · Hetzner · TLS 1.3 → WireGuard private tunnel → AxForge GPU · Sweden → Response
| Step | What happens |
|---|---|
| Request path | Customer → EEA edge (Hetzner, Germany — TLS 1.3) → encrypted private WireGuard tunnel → AxForge GPU (Sweden) → response. |
| What is recorded | Metadata only — token counts, timestamps, status — kept under the retention table. Prompt and completion bodies stay in memory and are discarded when the request completes. |
Verification
Verify it yourself
Every API key is pinned to an EU region, and every response echoes the x-axforge-region header back to you — residency is a header you can read on each call, not a paragraph you have to trust. Request and response shapes are in the regions & data handling docs.
Related
Nearby in the trust centre
Version 0.1 (launch draft) · Effective 2026-08-26
- 2026-08-26 — first published version of this page.