Sovereignty
One door out, and you hold the key
Sovereignty is not a promise in a contract. It is an endpoint every AI request in your company passes through, and behind it an architecture with no foreign dependency. This page shows both, layer by layer.
Layer by layer
Keera Gateway sits on top - the one place your rules are enforced. Nothing underneath it can route around them.
| Layer | Who controls it | Where it runs |
|---|---|---|
| The endpoint | Your versioned policy decides, per request, which model sees it. OpenAI-compatible, so it can be swapped out. | your tenant |
| Your data | Prompts and repository context live in the session only. Secrets and personal data drop out at the gateway. | your tenant |
| Audit log | Every request with identity, model and decision. It is yours, it goes to your SIEM, never a copy abroad. | CH only |
| Model weights | Open licence, downloadable by you. Nobody can withdraw them. | portable |
| Inference | bespinian, a Swiss company, on its own GPUs - no hyperscaler capacity. | Switzerland |
| Support access | Swiss-resident staff only, break-glass with your approval. | Bern |
Three questions that settle it
Ask them of every provider on your list. Ours included.
Do you know what your company sent to an AI yesterday?
With the gateway you do. Block direct egress at the proxy, and every request is in the log - instead of in a private account with a provider abroad.
Which foreign authority can compel disclosure?
None. bespinian has no US parent, no US subsidiary and no US sub-processors - the CLOUD Act has no addressee.
Can you keep working if the provider disappears tomorrow?
With Keera, yes: the gateway ships as a Helm chart, the weights are Apache-2.0, and the escrow agreement hands you both.
Sovereign does not mean sealed off
Sometimes a team needs a model that only exists abroad. The gateway turns that into a decision rather than a risk: you release it per team and data class, and what may not leave never reaches the border.
At peak, requests queue in Switzerland instead of quietly failing over abroad - it is written into the SLA. And because the address stays the same, you change the route without touching a single application.
Built from open source
Keera is not a black box. Your security team can read what runs on its machines instead of trusting a changelog.
- Keera Gateway - a Helm chart in your cluster, with an OpenAI-compatible API
- Qwen-Coder and Apertus - open-weight models, Apache-2.0
- vLLM and llm-d on Kubernetes - inference serving, scheduling and routing
Plus a signed SBOM per release and a tested runbook that migrates a tenant into your own cluster in less than two weeks.
Send us your risk questionnaire
We answer it in full before the first workshop - including the questions where the answer is “not yet”. Architecture, operations and data flows, laid out the way they are today.