Skip to content
gluon

Sovereign AI

Gluon runs in your own environment, on your own sources, with models you can replace. We build Gluon so that nothing depends on us.

  • Built in Rotterdam

    Gluon B.V. is a Dutch company, in Rotterdam.

  • Open source under the EUPL-1.2

    The European Union’s own licence, written by the European Commission.

    Open source
  • Runs in Europe

    In your own environment, next to your sources, or hosted by us in Europe.

    Hosted in Europe
  • Built around European law

    What each law asks, and where in Gluon it is answered.

    GDPREU AI ActNIS2DORA

Your environment

Whichever way it runs, the same controls apply, and you choose the models.

Where requests come from
  • Gluon chatChat
  • Gluon DesktopDesktop
  • CopilotMCP
  • ChatGPTMCP
  • ClaudeMCP
  • Your appsAPI
Where it runsIdentity and access
  • Your data centreOn-premises, next to your sources
  • Your cloudPrivate or sovereign, in Europe
  • Hosted by usManaged by Gluon, in Europe
One decision point
  • PoliciesWritten as sentences, with who gains access before one widens.
  • MarkingsSensitive fields masked by policy, the reason shown.
  • AuditAppend-only and hash-chained, streamed to your SIEM.Microsoft SentinelSplunk
  • Entra IDConditional Access and named locations
  • Active DirectoryLDAP and Active Directory groups
  • SCIMProvisioning, with break-glass accounts
  • OAuth 2.1PKCE for people, API keys for services
  • Azure OpenAI
  • Amazon Bedrock
  • Google Vertex AI
  • Mistral AI
  • Ollama

Models you chooseEach one sees only the markings you allow it.

How it works

  1. 01Keep your rules in your own files.

    Your model is written in GOL, plain files you own, and a version exports as a signed package.

    Phase 01 · Model
  2. 02Run it next to your sources.

    In your own environment, next to the sources you already have, or hosted by us in Europe. No forced migration.

    Phase 02 · Connect
  3. 03Choose the model, and what it may see.

    Gluon Gateway connects the providers you choose, including models you host. Which model may receive which data is part of your rules, and switching leaves them as they are.

    Phase 03 · Decide

Read first

Questions

Can we replace the model provider?

Yes. Switching a model through Gluon Gateway is a change in the configuration, and your rules and permissions stay as they are.

What happens if we stop?

Gluon keeps running. Your data, rules and decision trails stay where they are, and the code remains yours. You lose the service, not the product.

Where does Gluon run?

In your own environment, next to your sources, or hosted by us in Europe. Your documents stay where they are: Gluon reads them in place, with their own permissions.

Get started

You bring one question your team has to get right. The people who build Gluon sit down with you and build it together, in your own environment.

Two colleagues going through a notebook together beside a laptop.
  1. Choose one question and its outcome.

    With the people who build Gluon, you pick one question that must be right, with an owner and a clear outcome.

  2. Set the boundary and connect the sources.

    Name the sources, their owners and what must never be returned. Gluon connects them in your own environment, with the permissions they already have.

  3. Test it with your people.

    Your people ask real questions, including conflicting versions and requests outside their scope. Their questions and corrections show what to refine.

  4. Decide and go live.

    Business, security and operations judge the result against the outcome you set. Then the use case runs where your people work.