Enterprise
For people who evaluate GrailAOS™ from the inside, in engineering, IT or security, and for models. A company has its own and its own operations console, with its brand, sign-in with its own identity and the data on its own infrastructure.
This page explains how GrailAOS is built. Who it is for, how to buy it and what the contract covers is explained by Omniatix™, which sells it, at omniatix.com/enterprise.Go to Omniatix Enterprise
The console
It is part of GrailAOS: the same console serves every , and each deployment puts its own name on it, for the people who operate an account and for the people who maintain the platform.
How to read the labels
What is not on this site is not claimed on behalf of GrailAOS: don't promise it. For other capabilities, ask Omniatix.
Operations console with demo data
Operations console with demo data
Operations console with demo data
Operations console with demo data
The operations console is part of GrailAOS: each solution with its status and versions, conversations from every channel, escalations, contacts, the calendar, knowledge, channels and devices, a status screen and a manual.
Limit From the account, versions and the calendar can be viewed but not edited.
Runs and approvals are shown under “Processes” and “Approvals” in the Omniatix Chat dashboard, in the operations console of a dedicated deployment, and in the Human Desk, with one permission to view them and another to resolve them.
Each account's team signs in by invitation or from the company's identity directory, each person with a role built from permissions by resource and action, two-step verification, and per-solution keys that are shown only once.
From the console, each account sets its own caps and usage notifications; whoever handles conversations gets a when an escalation comes in, and each solution sends a daily email report.
Platform administration, for the team that operates it: it edits a solution's documents and publishes its versions with preview, and , and shows users, organizations, and each 's usage and .
The offering
What Omniatix confirms as its enterprise offering, explained by how it is built, including what is sent to third parties.
Dedicated deployment: each company has its own runtime and its own console, from versioned images (the runtime's and its solution's), on or on a server running .
GrailAOS on a cloud's managed Kubernetes (Amazon EKS, Google GKE or Azure AKS), starting from the standard resources it runs on today in .
Custom branding in the console: each deployment sets its name, its logo for light and dark backgrounds, the sign-in page with its colors, and the branding of each web chat, without building another image.
Limit The console's colors and icon do not change, and the sign-in footer keeps the platform credit.
Sign-in with the company's identity: the console delegates sign-in to the customer's identity provider over , today with Amazon Cognito; it coexists with sign-in by invitation, and a person assigns the role inside the console.
Limit Over OIDC: the console does not speak directly.
Data on the customer's infrastructure: the database with the knowledge vectors, the , and the files are installed in their cloud or on their servers.
Limit Sent to third parties: each turn's context to the model, text to and voice, audio and email unless self-hosted, and WhatsApp through Meta.
Control
The same things that run in any deployment, for the people who evaluate security and operations.
What security and IT look at
Limit Masking is pattern-based: names are not masked, and the operator can turn it off.
Limit The turn in progress always finishes; usage notifications are off by default and, like the billed-amount cap, need billing turned on.
Limit The per-conversation queue and the shared turn queue are turned on in the deployment's configuration.
Limit If is lost, the deferred jobs held there are lost; the no-Redis mode is turned on by configuration.
Limit OpenTelemetry sends one span per agent turn: workflow runs are not sent.
On request
The list is built automatically from the site's claims.
It does not run today: Omniatix implements it if a customer asks for it, with no timeline. What is not listed here is not done on request.
What is available on request
Available on requestOther providers, through an OpenAI-compatible
Connecting agents to models from other providers through an OpenAI-compatible gateway: LiteLLM, OpenRouter, or any server that speaks that interface.
Available on requestCalling another solution
Calling another solution as if it were a tool.
Available on requestTelegram as a channel
Telegram as a channel.
Available on requestManaged Kubernetes: Amazon EKS, Google GKE or Azure AKS
GrailAOS on a cloud's managed Kubernetes (Amazon EKS, Google GKE or Azure AKS), starting from the standard resources it runs on today in k3s.
Available on requestA dedicated connector for a company system
A dedicated connector for a company system, such as its online store, its ERP, or its CRM, instead of connecting it through its API or an MCP server.
Context-aware support
A support assistant that Omniatix built with GrailAOS for the Omniatix Chat dashboard: it reads what the person shares and points to where to click, with safeguards that do not depend on the model.
Support that sees the screen, built with GrailAOS: it reads what the person shares (no video or screenshots, sensitive data masked), shows where to click without clicking for them, checks only their account's signals and hands off to a team member, who can ask permission each time to watch live.
Limit Turned on by configuration.
The same support runs in the console of a dedicated deployment, on the company's infrastructure: the screens each deployment protects are never shared, and handoffs are handled only by Omniatix, in an area the company's staff does not see.
Limit With sign-in through the company's identity provider, it does not hand off to a person yet.
Buying
Omniatix handles the commercial side, on its own site: who it is for, how to buy it and what the contract covers.
For an in-depth technical evaluation under , use the same request for more information. Go to the request
More information
What you've read is less than half. There are more than 180 capabilities that already run, with their details.