Skip to content
gluon

Every source connected

Your sources, read where they are.

Gluon Connect is how Gluon knows your systems: databases, MCP servers, folders and marketplace connectors, synced into memory or queried live when a question needs them.

Gluon reaches these itselfRead when someone asks. Added in three steps.

  • PostgreSQL
  • MySQL
  • SQL Server
  • MCP server
Gluon ConnectOne layerRead your sources where they are, with the permissions they already have.
  • SharePoint
  • OneDrive
  • Google Drive
  • Confluence
  • Microsoft Teams
  • Slack

Their connectors push to GluonIngestion and marketplace connectors run outside Gluon’s core and push to it.

Also through a connectorDocument managementIntranetServiceNowYour own source

0 documents moved out of their sourceGluon reads them in place, with their own permissions. No second source of truth.Records and vectors are reached through a storage adapter, Elastic or pgvector, and only behind the decision point.

Source states

A source is connected when its test passes, authorised when a deployed Capability names it, and ready to answer when a type, a Query or an enabled tool uses it.

October 2026PostgreSQL is verified end to end. MySQL, SQL Server and remote MCP servers are built and tested, and still to be walked live.

Pick a source Gluon reaches itself

Added in three steps.

Before you start

Ask for a read-only user. Gluon only reads.

Add a source
  1. Pick the typePostgreSQL
  2. Connect and test
  3. Choose what to use

Next action

Connect and test. Gluon saves the connection and tests it from the server.

PostgreSQL: Your sources. Added in three steps.

  • 3 steps to a new source

    Pick the type, connect and test, then choose what Gluon may read.

    Connect a database or an MCP server
  • 3 states between a source and an answer

    Connected when its test passes, authorised when a deployed Capability names it, ready to answer when a type, a Query or a tool uses it.

    Memory
The same three dots on the Sources page, captured for the manual.

Ready to answer

One connector layer for the sources you already have. Gluon reaches databases and MCP servers itself, and marketplace connectors push to it.

  1. 01Sources

    Connect a source in three steps.

    PostgreSQL, MySQL, SQL Server and MCP servers: pick the type, connect and test, choose what to use.

    Read in the manual
  2. 02Memory

    What Gluon read, and how fresh it is.

    Items by source and tool with their provenance and validity, marked when they changed at the source. Correct or wipe any item.

    Read in the manual
  3. 03Ontology builder

    Suggestions mined from your sources.

    A mining run proposes types and links from your sources. You check each one and send it to review.

    Read in the manual
  4. 04System map

    Everything you may see, in six views.

    Rings, Circle, Areas, Links, Timeline and a 3D orbit of types, records, sources, models and channels.

    Read in the manual

No migration

You set the trust level per source. It tells the Authority Graph how much weight an answer may give it.

Connectors are open source under Apache-2.0. Build one for your own source, or with us.

Read what is open source
Content
The knowledge itself. The documents stay at the source.
Permissions
Mirrored from the source, with their age checked. Gluon withholds stale permissions.
Deletions
What disappears at the source disappears from Gluon.
Status
Sync and freshness, with an alert when a source falls behind.
Secrets
Secrets stay in the key service: a pasted URL is split on save and the password is never stored or shown again.

Tools and models

A tool is one thing a source can do: a tested query on a database, a tool on an MCP server, a lookup in the ontology. Replace the model, keep the control: switching is a configuration change, not a rebuild of rights and rules.

3 kinds of tool

A tested query, a tool on an MCP server, a lookup in the ontology.

Review, try and enable tools

0 tools that change data while answering

Only read-only tools are called while answering. Actions go through action control.

Tool catalogueExample
NameKindEffectStateUsed by
erp-live/contracts-by-supplierQueryRead-onlyOnRenewal assistant
erp-live/open-receivablesQueryRead-onlyOnContract renewal desk
ontology/search_procurement_contractOntology lookupRead-onlyOnContract renewal desk
ontology/get_supplierOntology lookupRead-onlyOnRenewal assistant
crm/list_accountsMCP toolRead-onlyOffNewNo tool pack yet
crm/get_accountMCP toolUnknownOffNewNo tool pack yet
An example catalogue. A new tool starts switched off, so a tool pack never widens on its own. A tool whose server does not say it only reads is unknown, and is never called.

Swap models freely

Which model may see which data is part of your rules, not a setting at the vendor.

Model matrixExample
Sensitivity labelAzure OpenAIAmazon BedrockGoogle Vertex AIMistral AIAnthropicOllama
PublicunmarkedAllowedAllowedAllowedAllowedAllowedAllowed
Internalmarking:internalAllowedAllowedAllowedAllowedAllowedAllowed
Confidentialmarking:confidentialWithheldWithheldWithheldWithheldWithheldAllowed
Personal datamarking:piiWithheldWithheldWithheldWithheldWithheldAllowed
An example: you set these rules. Here unmarked and internal evidence may go to every model, and confidential and personal data only to the model in your own environment.
Environment
Your own environment, next to your sources.
Models
The language model you choose, connected through Gluon Gateway.
Model matrix
Which model may see which data is part of your rules.
Switching
You change the model in the configuration. Permissions and rules stay the same.

Questions

Do our documents have to move?

No. Gluon reads them in place, with their own permissions. There is no second source of truth to maintain.

Which sources does Gluon reach itself?

PostgreSQL, MySQL, SQL Server and MCP servers, in three steps. Ingestion and marketplace connectors run outside Gluon’s core and push to it.

What happens when a permission changes at the source?

Permissions are mirrored with their age checked. Gluon withholds a record whose permissions are stale.

Do we pay Gluon for Copilot, ChatGPT or Claude?

No. You buy your AI tools and models where you already do. Gluon works with the ones you choose.

Can we switch models?

Yes. Switching is a configuration change in Gluon Gateway. Your permissions and rules stay as they are.

Can a tool change data while answering?

No. Only read-only tools are called while answering. Actions go through action control.

Where it is used