// For companies

A team of agents for your company, in your own deployment.

Omniatix™ deploys GrailAOS™ for your company: your own platform and your own operations console, on the infrastructure that Omniatix operates or in your company's cloud or servers. We tell you from the start what data stays inside and what goes to third parties.

Request more information How it is built

What your company gets.

Your own deployment.

Your company has its own platform and its own console, on standard Kubernetes (tested today on k3s) or on a server with containers. Each deployment is set up with your team: there is no generic template.

On the infrastructure that Omniatix operates.

The network of each deployment starts closed and opens only what is needed, such as public ingress and outbound internet access. The database has a full backup every day and can be restored to an earlier point in time. On your infrastructure, the network and the backups are set up with your team.

Your brand.

Your name and your logo on the console and on the web chat, and your company's colors on the sign-in screen. The footer of the sign-in screen keeps the platform's credit.

Example

“Hi, I am Sofia, the assistant at My Company.”

Sign-in with your company's identity.

Your team signs in to the console with your company's identity provider, over OIDC, and each person has the role assigned to them inside. The console does not support SAML yet.

Your data on your infrastructure.

With a deployment in your cloud or your servers, the database, the knowledge, the cache and the files stay there. To be able to respond, some things go to third parties: what is sent to the model in each conversation; the texts prepared for search, which OpenAI processes; the audio that is transcribed, unless you use your own server; the texts converted to speech; email, unless it goes through your own server; and WhatsApp messages, which go through Meta.

The models.

The agents converse on Claude, by Anthropic. A failover for provider outages can be turned on, with another Anthropic account or through OpenRouter: it never acts silently, it warns and it is logged. If the provider starts failing, whoever operates your deployment gets an email.

Other model providers, on request.

What your security team looks at.

  • Each person joins by invitation and with a role, built from permissions per resource and action.
  • Secrets are stored encrypted with AES-256-GCM.
  • By default, each agent response leaves a trace of what it did and what it spent.
  • Usage caps are checked before each response and cut off at the next one.
// On request

Available on request.

“On request” means it does not run today and that Omniatix implements it if your company asks for it, with no set date.

+ Models from other providers, or models running on your own servers, connected through an OpenAI-compatible gateway, such as LiteLLM or OpenRouter.

+ The platform on your cloud's managed Kubernetes: Amazon EKS, Google GKE or Azure AKS.

The full list of what is available on request, with the status of each capability, is at grailaos.com. If you need something else, tell us and we will tell you whether we can do it.

// Who it is for

Some uses.

These are illustrative examples: none of these companies is a customer.

We define what each solution does with your team, and what an agent cannot resolve passes to a person.

The third-party brands that appear belong to their owners and are named only to tell the example.

// Illustrative example

My Store

It sells on its online store and on Mercado Libre, takes payments with Mercado Pago, keeps its stock in its management system and its customers in a CRM.

A day at My Store

  1. Before opening, yesterday's payments are reconciled with the sales. If something does not add up, a notice is left for the manager.
  2. Two sales came in on Mercado Libre. The chief of staff hands them to inventory, which reserves the goods in the management system.
  3. A customer asks on WhatsApp for a refund of ARS 180,000. Since it is over ARS 100,000, it waits for the manager, who gets a notice on their phone and approves it, and the customer gets the money back.
  4. The seasonal campaign is put together with the 3,000 customers in the CRM, each with their last purchase. At five, the campaign writes to them on WhatsApp.

The manager's assistant

The same platform that runs the business is the assistant of the person who runs it.

  1. At closing time, the manager asks their assistant: “remind me to call the supplier on Thursday at ten”. On Thursday at ten, the reminder shows up in the chat.
How it is built, at grailaos.com →
// Illustrative example

My Lender

It gives personal loans: the application comes in by chat, it checks the credit bureaus, puts together the file, a committee decides and it collects in installments.

A day at My Lender

  1. A person applies for a loan on WhatsApp. The chief of staff passes them to origination, which takes their details and starts the evaluation.
  2. The two credit bureaus are checked at the same time, and the file is put together with what they return.
  3. The committee decides: the analyst approves the file and, since the amount is over ARS 2,000,000, the risk manager gives the second signature.
  4. With both signatures, the lender's system makes the disbursement.
  5. Someone with an overdue installment replies to the reminder: they want to refinance. The collections agent passes the conversation to the person in collections.
How it is built, at grailaos.com →
// Illustrative example

My Distributor

It sells to the shops in its area: it takes orders on WhatsApp, keeps a running account for each customer and delivers every day.

A day at My Distributor

  1. The day's price list comes in.
  2. A grocery store orders twenty boxes of cooking oil and ten of yerba mate on WhatsApp. The orders agent confirms the day's prices and enters the order; the total comes from the management system.
  3. The order goes over the grocery store's credit limit: it waits for the credit manager, who gets the notice.
  4. The credit manager approves it with a comment, and the order goes into the delivery route.
  5. Tomorrow's delivery route is put together, area by area, and the warehouse manager confirms it.
How it is built, at grailaos.com →

What is agreed by contract.

We agree with your company, in writing and before signing, which regulations each deployment covers.

How it is contracted.

A one-time implementation, a monthly platform license and model usage at measured cost. We quote each project.

Omniatix is a product company: it licenses and operates its platform. It is not a consultancy or a software agency.

Tell us what your company needs.

If your company is evaluating GrailAOS, request more information on the grailaos.com form.

Request more information

For general inquiries: hi@omniatix.com