EU-hosted. No server-side model. Open by default.
The things your procurement team asks about on call #2. Data residency stated plainly, model traffic that never reaches our infrastructure, and data connectors you can inspect.
Trust · Sovereignty · Openness
Each pillar has a concrete answer. Where something is planned rather than shipped, the label says so.
EU-hosted infrastructure
The gateway and the MCP server fleet run on Hetzner in the EU. Cloudflare provides edge and TLS termination in front, under SCCs and the EU-US Data Privacy Framework — we state that plainly rather than claiming nothing ever crosses a border.
- Hosted on Hetzner in the EU
- Cloudflare edge/TLS under SCCs · EU-US DPF
- GDPR-compliant DPA for all paid tiers
- Swedish entity, EU law governs
Bring your own AI client
You connect your own AI client — Claude Desktop, Microsoft Copilot Studio, Cursor, or a custom MCP client. Ansvar runs no server-side model: model traffic flows directly from your client to your model provider. We never see or proxy it, and your model bill stays on your account.
- Works with any MCP-capable AI client
- OAuth 2.1 — PKCE + Dynamic Client Registration
- No server-side model at Ansvar
- Model traffic never proxied or stored by us
Open source data layer
Open legal connectors are inspectable end to end. Audit every pipeline and verify how we reach each source — nothing about it is hidden. Signed, reproducible builds are not in place today; we will say so here when they are.
- Apache 2.0 connectors where source licensing permits
- Deterministic citation validation, verifiable
- MCP servers store no client data
Defense in depth
Every request crosses three control planes before it reaches your data. A tamper-evident audit trail records every transition across all of them.
- RequestFrom your AI client
- S1Network perimeter
- TLS 1.3 · Cloudflare + nginx
- Docker network isolation
- Automated vuln scanning
- S2Identity & authZ
- OAuth 2.1 · PKCE · DCR
- Per-request tier authZ
- SCIM: planned
- S3Data plane
- EU-hosted · Hetzner
- Secrets in HashiCorp Vault
- Forensic audit logging
- Customer dataEU-hosted · minimised — MCP servers store none
Where we stand on frameworks
Honest labelling. We tell you what is certified, what is aligned, and what is in progress — because the difference matters in procurement.
EU-hosted infrastructure, model traffic that never reaches us
Two data paths, stated plainly. Infrastructure data sits on Hetzner in the EU behind Cloudflare's edge; model traffic flows directly between your AI client and your model provider.
EU-hosted infrastructure
- Gateway and MCP server fleet hosted on Hetzner in the EU
- Cloudflare provides edge and TLS termination under SCCs / EU-US DPF
- Secrets in HashiCorp Vault, Docker network isolation between services
- Forensic audit logging on every request
- MCP servers store no client data
Your model traffic
- Your AI client calls your model provider directly
- No server-side model at Ansvar — we never see or proxy model traffic
- What we do see: the MCP tool calls your client sends the gateway (queries, lookups)
- Your provider's retention terms and your model bill stay between you and them
- MCP-first architecture — no vector store, no RAG copy of your data
Questions we answer before the DPA is signed
If yours isn't here, request the security questionnaire. We return it within five business days for paid-tier evaluations.
Do you train on our data?
No. Ansvar runs no server-side model and never sees model traffic — it flows directly from your AI client to your model provider. Customer data is never used for training, evaluation, or fine-tuning. Your provider's own retention terms apply on that direct path.
How is our data isolated?
MCP servers store no client data. What the gateway does hold — account and entitlement records, audit logs — sits on EU-hosted infrastructure with Docker network isolation between services and secrets in HashiCorp Vault.
What's your incident response?
72-hour notification to customer admins for any security incident affecting customer data, aligned to GDPR Art. 33 timelines.
Do you support SSO and SCIM?
SSO: yes — sign in with Microsoft Entra ID, Google, or username and password. SCIM 2.0 is planned; it is not built today.
Can we self-host?
No. The gateway is a hosted EU service — there is no self-hosted or air-gapped offering today. Open-source connectors are inspectable on GitHub, but we do not ship reference architectures for running the platform yourself.
What about penetration testing?
Our first third-party pentest is planned for 2026. No report exists yet — we will not claim one until it does.
Didn't see your question? .