Skip to content
gluon

AI Grounding

Copilot, ChatGPT, Claude and your own assistants get your organisation’s knowledge, with your permissions and your rules applied first.

Copilot
  • CopilotOver MCP
ChatGPT
  • ChatGPTWhere your people ask
Claude
  • ClaudeOver MCP
Your own agents
  • MCPOver MCP or the API

Keep your assistants

They ask Gluon through MCP or the generated API, with the permissions of the person they act for.

  • Read your sources where they are.SharePoint, Confluence, databases and MCP servers stay where they are. Gluon reads them in place, with the permissions they already have.
  • Apply the permissions first.The assistant gets the rights of the person it works for, never more, from the same decision point as chat.
  • Serve the assistant over MCP.Copilot, Claude and your own agents call the tools your model exposes, with the permissions of the person they act for.
  • Name the source in the answer.The answer names its source and version, and the trace shows what was read and how old it was.
Two colleagues going through a notebook together beside a laptop.

The assistant gets the rights of the person it works for, never more, from the same decision point as chat.

How AI Grounding works, step two

How it works

Read your sources where they are.

Phase 02 · Connect. SharePoint, Confluence, databases and MCP servers stay where they are. Gluon reads them in place, with the permissions they already have.

Who it is for

Questions

Which assistants can use Gluon?

Copilot, ChatGPT, Claude and your own assistants get your organisation’s knowledge, with your permissions and your rules applied first. Your own applications reach it through the generated API and MCP server.

Do we need Gluon if we already use Copilot or ChatGPT?

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.

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.