Skip to content

The platform's AI layer

AI we run ourselves.

Our models run on our own GPU servers in Germany, behind our own gateway. We fine-tune them in house, and a verification layer catches invented answers before they reach you. Your data stays inside our data center.

The decisive test

Is a server “in Frankfurt” enough? No.

The decisive test for sovereignty is not “where are the servers?” but “whose law governs the operator?”. If the parent company is incorporated in the US, the US CLOUD Act (2018) can compel disclosure, regardless of physical location. An “EU region” inside a US hyperscaler does not neutralise this.

In 2025 a major US provider confirmed before a French Senate committee that it cannot guarantee data is kept beyond the reach of US authorities, even for “sovereign” offerings. The CJEU's Schrems II ruling (2020) likewise shows EU-US data transfers are legally fragile.

  • Operator, stack and jurisdiction in EU hands
  • No US CLOUD Act access to your data
  • EU Data Act (since 2025) as an added safeguard
EU law · EU operator Your data at rest and in transit within the EU Open models Teuken · Mistral · Qwen · Llama, self-hosted Own GPU servers · Germany EU operator, no rented hyperscaler hardware Operator, stack and jurisdiction in EU hands US operator CLOUD Act (2018) "EU region" does not neutralise this
THE SOVEREIGN STACK

No US cloud. No US jurisdiction.

Sovereignty built into the architecture

Open models Teuken-7B (OpenGPT-X/Fraunhofer), Mistral, Qwen and Llama, open weights under permissive licences, self-hosted.
Own servers in Germany Our own GPU servers in German data centres, no US cloud, no rented hyperscaler hardware. Inference with vLLM, data at rest and in transit within the EU.
Honest compliance We design your solution to GDPR and frameworks like BSI-Grundschutz and ISO 27001, without faking certificates we don't hold.

Law & standards

Compliance lives in the architecture, not in the fine print.

The EU AI Act has applied since 2025: bans on certain practices since February 2025, obligations for foundation models since August 2025; from August 2026 it becomes largely applicable. We classify your applications into the risk tiers and use ISO/IEC 42001 as a practical roadmap. Privacy and traceability are part of the design from day one.

  • EU AI Act: risk classification & documentation
  • GDPR: personal data stays in your control
  • BSI C5 & ISO 27001 for secure operations
  • ISO/IEC 42001 as an AI management system
EU AI Act

The legal reality, in order

Why jurisdiction, not server location, became the decisive question.

2018
US CLOUD Act
US providers can be compelled to disclose data, regardless of where servers stand.
2020
Schrems II (CJEU)
EU-US data transfers ruled legally fragile.
2025
EU Data Act
New obligations on data access and provider switching.
2025
Senate testimony
A major US provider confirms it cannot keep data beyond US reach, even in “sovereign” offerings.
2026
EU AI Act
Largely applicable from August 2026: risk tiers, documentation, labelling duties.

Frequently asked

Questions about sovereign AI

Does on-premise alone make it GDPR-compliant?

No. On-premise is a strong foundation, but compliance comes from architecture, processes and documentation. We design both together, technology and verifiability.

Which models do you use without US dependency?

Open models under permissive licences such as Teuken-7B, Mistral and Qwen. We host them ourselves via vLLM; there are no API calls to US providers.

Is self-hosting performant enough?

Yes. With vLLM (PagedAttention, continuous batching) open models from 7B to 70B reach very good throughput. That covers most enterprise workloads comfortably.

What is the difference between data residency and sovereignty?

Data residency only says where data sits. Sovereignty says whose law governs the operator. Your AI is sovereign once operator, stack and jurisdiction all sit in the EU.

The real test is jurisdiction, not where the server stands

Many vendors point to data centres in Germany and call that sovereign. But data residency and sovereignty are not the same question. What matters is which law binds the operator. A provider under US jurisdiction falls under the CLOUD Act of 2018. It compels US companies to hand over data even when that data physically sits in Frankfurt. Server location alone does not protect against this.

The European legal picture reinforces the point. The Schrems II ruling of 2020 sharply restricted data transfers to the United States, and the EU Data Act, in force from 2025, adds further obligations around data access and provider switching. Anyone running AI in a regulated sector needs a technical answer to this, not only a contractual one.

That is why we build a stack with no US dependency. Open-weight models such as Teuken-7B from the Fraunhofer-led OpenGPT-X project, Mistral and Qwen run on our own servers in Germany, served through the vLLM inference engine. No US cloud, no US API by default. Your data stays with you or inside our EU infrastructure. This is data sovereignty, not ownership of the software.

We stay honest about the limits. On-premise deployment does not by itself produce GDPR compliance. The GDPR, the EU AI Act, BSI IT-Grundschutz and the ISO 27001 and ISO 42001 standards are the framework we implement for you, technically and organisationally, for public authorities, healthcare and law firms. Beyonetix itself is not certified against any of these standards. We build the conditions; the certification rests with you and your auditor.

Sovereign AI, in your hands

Let's talk about a sovereign setup for your organisation.