Gluon is the control layer for AI. It sits between your systems and the AI your people use, checks every answer and action against your rules and records it for your auditor.
Every team keeps its own sources.
Gluon applies one set of rules.
Gluon reads your sources where they are,
with the permissions they already have.
Every AI request
is checked against your rules.
Gluon sits between your sources and the Copilot, ChatGPT, Claude, Mistral or Ollama
Copilot
ChatGPT
Claude
Mistral
Ollama your people use. Before anything is answered or done, it decides which version applies, who may see it and what an AI agent may do, and records why.
Trace a request
An employee in the Netherlands asks whether they may fly business class to New York.
- The questionCan I fly business class to New York?Netherlands · intercontinental
- One appliesTravel policy NL 2026Gluon gives each one a verdict. Only one is in force for this employee.
- The answerBusiness class on intercontinental flights needs approval from your director.The answer comes from that policy alone, cited to the paragraph.NL 2026 · §4.2
- The approvalEUR 3,480§4.2 asks for the director. Nothing is paid until they approve.
Every node writes to one trail: the four sources and their verdicts, the citation, the checks and the hold.
Underneath your AI
Six steps, from your business written down once to answers that stay right. Each is a part of the platform, and every answer and action passes one decision point.
Model

Describe your business once, in a language your people and your AI share.
Connect

Read your sources where they are, with the permissions they already have.
Decide

Only what applies to this person, this team and this moment reaches the answer.
Act

Every action an agent wants to take gets a verdict before it runs.
Prove

Every answer and every action shows its work, in a trail nobody can rewrite.
Improve

Answers stay right while your sources and your rules change.
Same controls everywhere
A rule that widens access waits for security.
Policies are written as sentences; a change that widens access shows who would gain it and waits for a security approver.
What you may not see is withheld, and you are told why.
A marking on a field or a record masks or withholds it in chat, the API and MCP. A model receives only the markings that its route allows.
Every decision is a record you can verify.
Each record keeps who asked, through which channel, what was decided and what was withheld, chained by hash so a changed or missing one shows.
Your identity provider says who is asking, never the client.
People sign in through your identity provider; their groups and their device’s posture come from its claims, never from the client.
The same controls in every deployment.
In your data centre, your own cloud or hosted by us in Europe: policies, markings and audit are the same code in each.
Your stack
Gluon fits between what you already run: your documents and data, the models you choose and the assistants your people use. Your identity provider says who is asking, and your SIEM receives every decision.
Start with a question
- 01Choose one question and its outcome.
- 02Set the boundary and connect the sources.
- 03Test it with your people.
- 04Decide and go live.
See it decide on your own sources.
Start with one question that must be right, in your own environment.
Questions
Do we need Gluon if we already use Copilot, ChatGPT or RAG?
Yes. Assistants find information in your sources, but they cannot tell which version is in force or who a document applies to. Gluon sits underneath them and gives them only what applies. RAG finds passages that look like the question. Gluon first checks which sources have authority, which version applies and whether this person may see it. Retrieval then works only on that context.
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.
Is Gluon certified for the EU AI Act or ISO 27001?
No. Gluon is designed around eleven frameworks and holds none of their certificates. Your organisation is audited; Gluon supplies the controls and the evidence.
What does Gluon cost, and what if we stop?
If you run it yourself, Gluon costs nothing: the core is open source, and you pay only for your own infrastructure and operations. The enterprise price depends on where Gluon runs, how much of the implementation we take on, and the support and guarantees you need. You get one proposal with everything in it. If you stop, Gluon keeps running: you lose the service, not the product.
