Skip to content
Platform status · live checks
main-compute

Sovereignty · Architecture

The boundary is the product.

Sovereignty is not a region dropdown. It is who can route a request, read a key or compel a copy. MainAI keeps all three inside the EU.

EU production footprint54.6° N / 15.6° E
MainAI site EU capacityNo fallback outside the EEA

Production footprint inside the European Union:

  • Copenhagen: EU ingress + operator
  • Skanderborg: GPU region · sk1
  • Frankfurt: EU peering
  • Amsterdam: EU peering
01

No US control plane

Authentication, routing, metering and billing run on infrastructure we operate. A request does not need a US region to complete.

02

Prompts stay transient

Prompt and completion bodies transit memory and are not written to the portal database. We store token counts and request metadata.

03

Data processing addendum

A GDPR Article 28 DPA ships with invoiced plans. It names subprocessors, breach windows and deletion duties.

04

Danish jurisdiction

Contracts are governed by Danish law. The processor is established in the EU and answers to a European supervisory authority.

01 / Request path

Read the diagram. Then the contracts.

Requests enter through an EU ingress and cross a private network to isolated GPUs in sk1, Skanderborg. Model hosts expose no public port. Token counts come back; prompt bodies do not get stored on the way.

01 · client

Your application

OpenAI SDK · EU client

02 · EU ingress

Public API

TLS · identity and key checks

03 · private path

Isolated model pool

No public GPU port · private credentials

Three hops · no public model portRead the threat model

No public model port

You talk to the API, never to a GPU host. Model pools accept only private traffic, so there is no second public surface to defend.

Processor terms, not a PDF afterthought

The DPA incorporates the EU Standard Contractual Clauses and defines breach notice, audit and deletion.

A short subprocessor list

Four EU contracting entities. Invoiced accounts get 30 days' notice before a new one is added.

02 / Subprocessors

Who touches what.

The list stays deliberately short. Card data goes to Stripe; encrypted backups go to an EU AWS region; email goes through an EU relay. Inference stays on infrastructure we operate.

Subprocessors, purpose, location and role
EntityPurposeLocationRole
MainAIInference hosting, EU ingress and operator accessDenmarkController / processor
Stripe Payments Europe, Ltd.Card payments, subscriptions and invoicesIrelandPayment processor
Amazon Web Services EMEA SARLEncrypted off-site database backupsEU region, SwedenInfrastructure subprocessor
EU SMTP relayVerification, reset and invoice emailEuropean UnionEmail subprocessor
All EU-established or EU-regionalSubscribe to changes

03 / Documents

The paperwork behind the path.

Data processing addendumArt. 28 terms, SCCs, subprocessor consent and deletion.Retention schedulePer-data-class windows, including the legal minimum for invoices.Private connectivityTunnel, egress allow-list and firewall-lock options.Security postureControls, threat model, disclosure and certification roadmap.

Need a review call with the operator?

We will bring the diagram, DPA and subprocessor list.

Talk to an engineerSecurity posture