Verify everything
Where Gluon runs, which measures it is built on, which documents you can read and how to report an issue.
Where it runs
You decide where Gluon runs. Questions, documents and decision trails stay in that environment.
| Three ways to run it | Your data centre | Your cloud | Hosted by us |
|---|---|---|---|
| Runs on | Your servers | Your tenant | Gluon, in Europe |
| Data stays | Next to your sources | In your cloud | In Europe |
| Controls | The same | The same | The same |
- Gluon chatChat
- Gluon DesktopDesktop
- CopilotMCP
- ChatGPTMCP
- ClaudeMCP
- Your appsAPI
- Your data centreOn-premises, next to your sources
- Your cloudPrivate or sovereign, in Europe
- Hosted by usManaged by Gluon, in Europe
- 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.
- 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.
Identity and access
People sign in through your identity provider; their groups and their device’s posture come from its claims, never from the client.
- Your identity providerEntra ID, Active Directory and LDAP groups, SCIM provisioning with break-glass accounts.
- Masking by policyA 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.
- Your modelsWhich model may receive which data is part of your rules, not ours.
Responsibilities
You run it, we host it, or we build the first use case with you. The code is the same in each; the duties differ.
You run itYour own environment
- Infrastructure
- WeThe Docker images, and the same updates we run ourselves.
- YouRun them in your cloud or data centre, with owners for backups, restores and monitoring.
- Sources and permissions
- WeGluon Connect reads your sources in place, with the permissions they already have.
- YouAgree identity groups, team scope, source permissions and sensitive-field policies before connecting a use case.
- Models
- WeGluon Gateway connects the model you choose, including models you host.
- YouChoose the providers, and which model may receive which data.
- Support
- WeIssues handled in the open. Support with an SLA when you add Enterprise.
- YouIncident response and capacity for your own environment.
We host itHosted by us in Europe
- Infrastructure
- WeWe manage Gluon for you, with the same updates as the open core.
- YouChoose the European environment Gluon runs in.
- Sources and permissions
- WeGluon Connect reads your sources in place, with the permissions they already have.
- YouAgree identity groups, team scope, source permissions and sensitive-field policies.
- Rules
- WeYour rules apply on every request, through one decision point.
- YouOwn the model: what applies, who may see what and which actions need a person.
- Support and guarantees
- WeSupport with an SLA, a data processing agreement and the answers your CISO needs.
- YouName the business, security and operational reviewers for each use case.
We implement itImplementation with us
- The use case
- WeHelp you choose one use case, with an owner and a clear outcome.
- YouName the owner, the team and the question that must be right.
- Sources
- WeConnect the sources involved, in your own environment, with the existing permissions.
- YouList the sources, document owners, user groups and sensitive fields.
- Rules
- WeSet up the rules with you, as a model in GOL.
- YouApprove the model: nothing is published before its owner and security approve it.
- Testing
- WeRefine the use case from your people’s questions and corrections.
- YouPrepare representative questions and expected sources, and agree the acceptance criteria.
- The decision
- WeShow the evidence for every answer.
- YouDecide on the date you set before expanding to another team.
What runs,
and what to confirm before go-live.
- Containers you can run
- Gluon ships as Docker images: one Rust service with the designer, the console and the chat, Postgres for the model and the audit log, and a storage adapter for retrieval.
- Application boundary
- Gluon combines one Rust service with a designer, admin console and employee chat, and runs the same code in Gluon Desktop. API and MCP expose governed knowledge to other applications. Source ingestion and marketplace connectors are separate integration responsibilities.
- Data and model services
- Postgres holds the master model and audit data. Retrieval uses a storage adapter. Language model access goes through a gateway, with provider choices and policy configured for the deployment.
- Security guarantees
- A data processing agreement and the answers your CISO needs.
- Operational ownership
- Assign owners for infrastructure, backups, restores, monitoring, model providers and incident response. Confirm data location, retention, support responsibilities and capacity against the actual environment.
Architecture
- One permission pathChat, API, MCP and the designer ask the same policy decision point.
- Existing permissionsRights from your source systems apply to users and agents, with their freshness checked.
- Masking by policySensitive fields are masked before they reach an answer.
- Decision trailEvery answer and action is recorded in a hash-chained audit trail.
- A kill switchAny action, source or model can be switched off at once.
- Public codeThe core is open source. Anyone can read what Gluon does.
- Rules in CEL
- Versions in SemVer
- Packages signed with Ed25519
- Masked, hidden or withheld
- Per model route
- The reason names the marking, never the content
- OCSF 1.3
- Splunk, Sentinel, Elastic
- Payloads encrypted and erasable
- OIDC with PKCE
- SCIM 2.0
- Entra Conditional Access
- Break-glass accounts
- Docker images
- Postgres
- Elastic or pgvector
- Open source, EUPL-1.2
Gluon holds no certificates yet. Your organisation is audited; Gluon supplies the controls and the evidence.Regulations and standards Everything about open source
Documents
Report a vulnerability
Email it to us, not to a public issue or a chat. We confirm your report, keep you informed and publish the fix.
- Email info@glu0n.comWhat is affected, how to reproduce it and the impact you expect.
- Keep it privateGive us reasonable time to publish a fix before you disclose the problem.
- We follow upWe confirm the report, keep you informed and credit you if you want to be credited.
The people who build Gluon read every report themselves.Email a security report