A field guide for European IT and security

Sovereign AI.
On infrastructure you choose.

Europe now scores cloud and AI services on who controls them. Most of that score is set by where your AI runs and which model it calls. OpenWork is the workspace built to run on whatever you pick.

What Europe is asking for

Two documents, one question: who is in control?

The Cloud Sovereignty Framework. Published by the European Commission in October 2025. It has eight objectives and five assurance levels. The Commission uses it to buy its own cloud services, and since June 2026 it encourages public and private organizations to use it too.

The Cloud and AI Development Act. Proposed by the Commission in June 2026 and not law yet. It would set four assurance levels and require public bodies in critical sectors to buy at level two or above.

Neither is the EU AI Act, which regulates how AI systems are built and used. Both score services and providers, and the buyer or an auditor assigns the level.

Read the framework · The Commission's explainer · The proposed act

The levels

Five steps, from no control to full control.

A buyer sets a minimum level for each objective. A service that falls short on any one of them is out. Most organizations need a higher level for some work than for the rest.

  1. SEAL-0

    No sovereignty

    Service, technology, and operations under non-EU control and non-EU law.

  2. SEAL-1

    Jurisdictional

    EU law applies on paper but is hard to enforce. Operations stay under non-EU control.

  3. SEAL-2

    Data

    EU law applies and can be enforced. Material non-EU dependencies remain.

  4. SEAL-3

    Digital resilience

    EU actors have real but not full influence. Non-EU control is marginal.

  5. SEAL-4

    Full digital sovereignty

    Complete EU control, EU law only, no critical non-EU dependencies.

The eight pieces

How far OpenWork gets you, piece by piece.

The framework was written for cloud services, and an AI workspace is one layer of yours. Pick your setup to see what OpenWork answers on each of the eight objectives, and what is left.

Where OpenWork runs

The control plane and gateway run on your own Kubernetes cluster in the EU.

Where the models run

Models run in an EU region of a large cloud, such as Amazon Bedrock.

This comparison assumes Enterprise controls are enabled where required. Internal mirrors, encryption, and your identity provider still need configuring.

78%of our workspace checks answered in this setup.

Answered today
78%
More with a different setup
1%
Open on our side
21%

Our own count for the workspace layer. It is not a SEAL level.

  1. SOV-1

    Strategic

    15% of the score

    4 of 6 answered

    Who owns and controls the provider, and whether you can keep running if it pulls out.

    Set by
    Your cloud provider and each software vendor

    • Answered: Runs on infrastructure you operate.
    • Answered: The desktop app is open source, under the MIT licence.
    • Answered: Each release of the control plane and gateway becomes MIT-licensed after two years. That is written into the licence.
    • Answered: A licence change never applies to a version you already run.
    • Open on our side: A vendor owned and controlled in the EU.Still open. OpenWork is made by Different AI, Inc., a US company.
    • Open on our side: Written terms for what happens if the vendor stops.Still open. Our standard terms do not cover this yet.
  2. SOV-2

    Legal and jurisdictional

    10% of the score

    4 of 5 answered

    Which law governs the provider, and whether an authority outside the EU could compel access to your data.

    Set by
    Where the service is operated, and by whom

    • Answered: The vendor operates no part of your deployment.
    • Answered: Usage logs stay in a database you run.
    • Answered: Files stay on the employee's computer.
    • Answered: Product analytics are optional and can be switched off.
    • Open on our side: A vendor that answers to EU law only.Still open. Different AI is a US company, so US law applies to us.
  3. SOV-3

    Data and AI

    10% of the score

    5 of 6 answered

    Who holds the keys, who can see data access and model use, where data is processed, and who controls the models.

    Set by
    Mostly your model and where it runs

    • Answered: You choose the model and the provider.
    • Answered: The gateway's request log records who used which model, not prompt or response bodies.
    • Answered: Organization audit history is available with Enterprise or a self-hosted entitlement, with recording enabled.
    • Answered: Provider keys and sign-in settings are encrypted with a key you hold.
    • Answered: Prompts are processed in the EU.
    • Not in this setup: The model runs on hardware you control.Needs a model you serve yourself.
  4. SOV-4

    Operational

    15% of the score

    7 of 9 answered

    Whether teams in the EU can run, support, and move the technology without a vendor outside the EU.

    Set by
    Who operates and supports each layer

    • Answered: Your own team installs and upgrades it, from a Helm chart with pinned versions.
    • Answered: You choose which desktop versions employees can install.
    • Answered: Deployment guides and source code are public.
    • Answered: Your configuration exports as one file and moves between OpenWork Cloud and self-hosted.
    • Answered: Teams, providers, and connections can be set up from a repeatable script.
    • Answered: Works behind your own certificate authority and proxy.
    • Answered: A diagnostics page shows whether desktops, AI providers, and connectors are working.
    • Open on our side: Support from a team based in the EU.Still open. Support comes from the OpenWork team. There is no EU support partner yet.
    • Open on our side: A long-term support release line.Still open. Fixes ship on the latest release. There is no long-term support line yet.
  5. SOV-5

    Supply chain

    20% of the score

    7 of 10 answered

    Where hardware and software come from, how software is packaged and updated, and how visible the suppliers are.

    Set by
    Your hardware, plus every piece of software on it

    • Answered: Every outbound host is published, per component.
    • Answered: A new enterprise install contacts no outside host until you link it to your organization.
    • Answered: Enterprise installs update from their own release channel, never the public one.
    • Answered: Application dependency manifests and lockfiles are public in the source repository.
    • Answered: The model catalog and helper package can come from your own mirror.
    • Answered: The chart and images can be mirrored into your own registry.
    • Answered: Desktop installers are served from inside your network.
    • Open on our side: A software bill of materials for each release.Still open. Not published yet.
    • Open on our side: Built and distributed on EU-controlled infrastructure.Still open. Releases are built and distributed through GitHub and npm.
    • Open on our side: A documented mirror for desktop updates.Still open. Without internet access you handle desktop updates through your own release process.
  6. SOV-6

    Technology

    15% of the score

    5 of 6 answered

    Open standards and APIs, licences that let you audit and change the software, and a visible architecture.

    Set by
    Each layer's standards and licence

    • Answered: Open protocols: MCP for tools, SAML and OIDC for sign-in, SCIM for provisioning.
    • Answered: Works with any OpenAI-compatible model endpoint.
    • Answered: All source code is public to read and audit.
    • Answered: The agent engine underneath, OpenCode, is open source.
    • Answered: The architecture and data flows are documented.
    • Open on our side: Every component under an open-source licence.Still open. The control plane and gateway are source-available under a commercial licence until each release turns MIT.
  7. SOV-7

    Security and compliance

    10% of the score

    5 of 6 answered

    Certifications, EU rules such as GDPR and NIS2, where security operations sit, and whether you can patch and audit on your own.

    Set by
    Your security operations and each vendor's audits

    • Answered: SOC 2 Type II and ISO 27001, with reports in the trust center.
    • Answered: Sign-in goes through your identity provider, so your own multi-factor and access rules apply.
    • Answered: A public security policy, with a private reporting address and stated response times.
    • Answered: Logs and monitoring stay in your own tools, through OpenTelemetry.
    • Answered: You can read the code and apply a patch yourself.
    • Open on our side: European cloud assurance evidence, such as a C5 attestation.Still open. Not held yet.
  8. SOV-8

    Environmental

    5% of the score

    2 of 2 answered

    Energy efficiency, hardware reuse, and emissions reporting.

    Set by
    The data centre you run on

    • Answered: Agents run on computers employees already have.
    • Answered: OpenWork adds no hosting of its own.

What is left

The last 22%.

You can close 1% by changing your setup. The other 21% is open on our side today.

Close more by changing your setup

Open on our side, in any setup

  • SOV-1 · Strategic

    A vendor owned and controlled in the EU.

    OpenWork is made by Different AI, Inc., a US company.

  • SOV-1 · Strategic

    Written terms for what happens if the vendor stops.

    Our standard terms do not cover this yet.

  • SOV-2 · Legal and jurisdictional

    A vendor that answers to EU law only.

    Different AI is a US company, so US law applies to us.

  • SOV-4 · Operational

    Support from a team based in the EU.

    Support comes from the OpenWork team. There is no EU support partner yet.

  • SOV-4 · Operational

    A long-term support release line.

    Fixes ship on the latest release. There is no long-term support line yet.

  • SOV-5 · Supply chain

    A software bill of materials for each release.

    Not published yet.

  • SOV-5 · Supply chain

    Built and distributed on EU-controlled infrastructure.

    Releases are built and distributed through GitHub and npm.

  • SOV-5 · Supply chain

    A documented mirror for desktop updates.

    Without internet access you handle desktop updates through your own release process.

  • SOV-6 · Technology

    Every component under an open-source licence.

    The control plane and gateway are source-available under a commercial licence until each release turns MIT.

  • SOV-7 · Security and compliance

    European cloud assurance evidence, such as a C5 attestation.

    Not held yet.

Tell us your setup and the level you are working to. We will go through each open item with you: what we can commit to, what is planned, and what will stay open.

Same workspace, different level

Start where you are. Move up without changing tools.

Two setups we see in Europe. The workspace is the same in both. What differs is the model and who operates it, and that is what an assessor will look at first.

Workspace
EU residency on a large cloudOpenWork on your own Kubernetes cluster
Fully in-houseOpenWork on your own Kubernetes cluster
Models
EU residency on a large cloudAn EU region of a US cloud provider
Fully in-houseOpen-weight models on your own hardware
Sign-in
EU residency on a large cloudA cloud identity provider over SAML
Fully in-houseA self-hosted identity provider over OIDC
Agents run
EU residency on a large cloudOn employee computers
Fully in-houseOn employee computers
What sets the level
EU residency on a large cloudThe cloud provider: its owner and its law
Fully in-houseYour own operations and hardware supply

Which level either setup earns is your assessor's call.

Before you pick a workspace

Six questions to ask any AI vendor.

  1. Does it run entirely on infrastructure we operate?
  2. Can we use any model, including one we serve ourselves?
  3. Does it sign people in with our identity provider?
  4. Which hosts does it contact, and can each one be mirrored or turned off?
  5. Can we read the source and apply a patch without the vendor?
  6. What happens to our deployment if the contract ends?

Our answers are in the self-hosting guide, the outbound network list, and the air-gapped deployment guide. Certifications are in the trust center.

Know the boundary

A workspace. Not a sovereign cloud.

OpenWork does not supply your hardware, your data centre, or your models. Those set most of your level. A workspace can only avoid pulling it down: no required vendor cloud, no fixed model, no fixed identity provider.

OpenWork Cloud is our hosted service, operated by a US company. If you are working to a sovereignty level, self-host. And whatever you host, the model still sees prompts and the file content sent as context.

Plan a self-hosted deployment

Sovereign AI FAQ

Which sovereignty level is OpenWork?

None, and no software vendor can honestly give you one. Levels in the Cloud Sovereignty Framework are assigned by the buyer or an auditor to a whole service: the infrastructure, the operator, the models, and the software together. This page counts what OpenWork answers on each objective in the setup you pick and lists what is still open, so you can fill in your own assessment.

What does the percentage on this page mean?

It is our own checklist, not the Commission's scoring method. We group workspace checks under the framework's eight objectives. Checks have equal weight within each objective; the objectives use the framework's published weights. The percentage counts documented capabilities for the setup you pick, not a verification of your deployment. It is not a SEAL level or a Sovereignty Score. Your hardware, data centre, and model provider need a separate assessment; one critical gap can still rule out a service.

Is this the EU AI Act?

No. The EU AI Act regulates how AI systems are built and used. The Cloud Sovereignty Framework and the proposed Cloud and AI Development Act are about who controls the cloud and AI services you buy. An organization can be subject to both.

Can OpenWork run without contacting OpenWork's servers?

Self-hosted, the control plane and gateway run in your environment. By default the desktop app still fetches a model catalog, updates, and one helper package from public hosts; each can be mirrored. The air-gapped deployment guide lists what a fully isolated setup has to mirror, disable, or replace, including the parts that are not documented yet.

Which models can we use?

The ones you approve. The gateway supports major providers, including Amazon Bedrock in a region you choose, and OpenAI-compatible endpoints, which covers models you serve on your own hardware. Model choice decides most of the data and AI objective, so pick it before you pick a workspace.

Is OpenWork open source?

The desktop app is MIT-licensed. The control plane and gateway are source-available under the OpenWork Enterprise Edition licence: you can read and modify the code. Production use needs a subscription, except for organizations with up to five users excluding Enterprise Features. Evaluation, development, and testing exceptions also apply. Each EE release becomes MIT-licensed after two years.

From policy to practice

Give employees a path they can actually use.