Swfte Connect / EU routing
EU-first routing: decide which models, which regions and which evidence
For European organizations, the questions about an LLM gateway are specific: where is the data processed, which providers can see it, and what can we show a reviewer. Connect gives you the controls to answer each one.
What EU-first means for a gateway
It is not a badge. It is a set of choices you make and can demonstrate.
EU-first routing means three things in practice. You choose which providers a workload may use, based on where they process data and under what terms. You keep the most sensitive traffic on models running in infrastructure you control. And you can produce a record of what was sent where. Connect is the place those choices are enforced, because every request already passes through it.
It also means being honest about limits. A gateway cannot change where a third-party provider processes data. It can only decide whether to send the request there. The rest of this page separates what Connect does today from what it is designed for.
How data is handled today
These statements match the trust centre.
- Storage location. Customer data in the managed service is stored in AWS eu-west-1 (Ireland).
- In transit. API traffic uses TLS 1.2 or later, with TLS 1.3 preferred.
- At rest. Databases are encrypted, most tables use a managed key, and object storage is encrypted.
- Other locations. Other data locations are agreed per dedicated deployment, not offered by default.
- Your keys. With bring-your-own-key, your provider keys and your provider agreements stay yours.
Customer-managed encryption keys are designed for dedicated deployments and are not generally available today. Zero-data-retention agreements with model providers are in progress. See the trust centre for the current position, which is the source of record.
Four routing patterns for European workloads
| Pattern | How it works | Status |
|---|---|---|
| Approved-provider chains | Define a routing rule whose fallback chain lists only providers you have approved. An outage then falls back inside the approved set. | Available: routing rules and fallback chains are part of Connect |
| European providers first | Prefer providers that are European companies or operate European regions, such as Scaleway, OVHcloud and Mistral, and verify processing location in each provider's terms. | Available as a routing choice; location is confirmed per provider |
| Self-hosted open-weight | Run open-weight models on GPUs in your own EU cloud or data centre and route sensitive traffic there. | Available, see Self-deploy |
| Region-enforced routing | The gateway refuses any provider outside a declared region. | Designed for, on request |
Note the last row. Today the way to keep traffic in a region is to curate the chains and providers a workspace can use. A hard region constraint, where the gateway itself rejects a non-compliant route, is designed for and arranged with the team.
Controls on what leaves
Provider choice is one control. Content is another.
- Redaction before dispatch. Content policies detect secrets and personal data patterns, such as email addresses, phone numbers and key material, and can redact them before a request goes to a model.
- Usage caps and alerts. Token and spend limits per workspace or per model, with email and webhook alerts, so a runaway workload is caught early.
- Rate limits. Concurrency limits per workspace protect both your budget and your providers.
- Audit events. Workspace-scoped action events and usage records give a reviewer a trail to start from.
- Data retention. Retention is defined by organizational policy, set in the Trust Profile of each AI system.
How this relates to European rules
The regimes below set obligations for organizations, not for a gateway. Connect provides controls and evidence that help you meet your own obligations.
Data protection rules shape where personal data may be processed and under which safeguards, which is why provider choice and data location matter. The EU AI Act sets obligations by role and risk class. Network and operational resilience rules apply to many regulated entities and their suppliers. The EU hub on this site explains each in plain language with primary sources; start with GDPR and AI and the EU-first AI hub.
Compliance-by-design. Swfte provides the technical controls, governance mechanisms and evidence required to deploy AI within an organization's applicable regulatory, security and policy requirements. The exact posture depends on the customer's use case, jurisdiction, deployment and configuration. Connect does not by itself make any deployment compliant with any regulation.
The evidence a reviewer asks for
| Reviewer asks | Connect control | Evidence |
|---|---|---|
| Which providers can see our data? | Approved-provider chains, BYOK | Routing rule definitions; the sub-processors list |
| Is personal data masked before it leaves? | Content policy redaction | Policy definitions and policy events |
| Who called which model? | Authenticated, metered gateway | Usage records per workspace |
| What did the system do? | Action audit events | Audit event export |
| What does it cost, and who capped it? | Usage caps and alerts | Cap configuration and alert history |
Assurance
Swfte does not hold a SOC 2 report or an ISO 27001 certificate and does not sign HIPAA Business Associate Agreements today. A SOC 2 Type I audit is in preparation; the trust page has the current status. The trust centre lists current documents and any item still in progress.
Frequently asked questions
Where is data stored when I use Swfte Connect?
Customer data in the managed service is stored in AWS eu-west-1 (Ireland). Other locations are agreed per dedicated deployment. A request sent to a third-party provider is processed by that provider under its own terms.
Can I make sure requests only go to EU providers?
You can curate the providers and fallback chains a workspace uses, prefer European providers and run your own open-weight models in an EU environment. A hard region constraint enforced by the gateway is designed for and arranged on request.
Does Connect make us compliant with GDPR or the EU AI Act?
No product does that by itself. Connect provides technical controls, governance mechanisms and evidence you can use within your own obligations. The posture depends on your use case, jurisdiction, deployment and configuration.
Can personal data be removed before a prompt reaches a model?
Content policies can detect common personal-data and secret patterns, and redact them before dispatch. You can add custom patterns for your own identifiers.
What about the strictest residency needs?
Self-deploy Connect with open-weight models on infrastructure you control, so prompts to those models never leave your environment. See the self-deploy page.
Connect in the platform
Models and routing layer
Connect as the model gateway and routing layer of the platform.
Sovereign infrastructure
Where AI runs, from managed to dedicated.
Dedicated cloud
Private capacity operated for you.
GPU and inference
GPU capacity for the models Connect routes to.
Deploy open-source models
The catalogue of open-weight models you can host.
LLM API guides
Provider and model reference pages.
Trust centre
What Swfte can show today.
Sub-processors
Providers and services Swfte itself relies on.
Route every model through one governed gateway
Start managed in minutes, or plan a deployment inside your own boundary with the team.