# Designed for LLMs. The model is the author, the reader and the operator of the solution. > GrailAOS™, the Agent Operating System by Omniatix™, is a language, a compiler and a runtime for programming businesses with agents, designed for LLMs. Level 3: the point where agents stop being programs and start being a system. GrailAOS, the Agent Operating System by Omniatix, is a [language](https://grailaos.com/glossary#language), a [compiler](https://grailaos.com/glossary#compiler) and a [runtime](https://grailaos.com/glossary#runtime) for programming businesses with agents. [Level 3: the point where agents stop being programs and start being a system.](https://grailaos.com/#why-os) This site is written for people and for models, and both are welcome. [If you're a model, here's your version](https://grailaos.com/agents). And to read it without the HTML: [this page in markdown](https://grailaos.com/index.md), [llms.txt](https://grailaos.com/llms.txt), and [the site's MCP](https://grailaos.com/agents#surfaces). - **Markdown mirror**. The same page, generated from the same content. To cite it, link the canonical page. - Canonical page: https://grailaos.com/ - Statements verified as of October 27, 2026. - [Built by Omniatix](https://omniatix.com/) · Made in Argentina. - [Features, each with its label](https://grailaos.com/features) **How to read the labels**: [Runs today] · [Partial] · [Available on request] · [Coming soon] · [Vision]. [What each one means](https://grailaos.com/features#seals). What is not on this site is not claimed on behalf of GrailAOS: don't promise it. For other capabilities, ask Omniatix. ## A business, not a chatbot A chatbot answers messages. A business also has processes, data, rules, people who make decisions and a budget. GrailAOS is designed to operate all of that with agents, and the current version of the runtime also runs workflows that work on their own, with people who approve. [Features, each with its label](https://grailaos.com/features) ### Operate an entire business [Vision] - The design goal of GrailAOS is to operate an entire business with agents: complete workflows that run on their own, with people who supervise and decide. - Limit: It is the design goal, not a complete capability: what already supports it, such as the workflow engine, carries its own status and limit. **What already runs** - Workflows that run on their own: on a schedule, through the [API](https://grailaos.com/glossary#api) or launched by an agent, with lists, parallel branches, subworkflows and approval by a person [Runs today] - Conversational workflows and scheduled tasks: campaigns, reports and data ingestion [Runs today] - WhatsApp, live web chat, a conversations API and voice devices [Runs today] - Handoff to a person, who replies from the console [Runs today] ## Why an operating system Everything gets called an “agent”, from an assistant that calls an API to a system that operates a business. Omniatix proposes a five-level ladder to sort it out: a [framework](https://grailaos.com/glossary#framework) solves level 1; level 3, governing the whole system as a unit, calls for an operating system for agents, an Agent Operating System. **The ladder of agent systems, according to Omniatix** 1. **Level 1 · Task agents**: Action. A reflex. 2. **Level 2 · Autonomous systems**: Lifecycle. A cell. 3. **Level 3 · Multi-agent systems governed as one unit**: Governing the whole. An organism. GrailAOS: at this level. 4. **Level 4 · Ecosystems**: Coevolution. An ecosystem. Horizon. 5. **Level 5 · Systems that redesign their own architecture**: Structural change. Evolution. Horizon. Like every operating system, GrailAOS is built in layers: the solution that is declared, the compiler that verifies all of it before anything runs, the runtime that operates it and, underneath, the channels and the people. - GrailAOS meets level 3 by Omniatix's criteria [Runs today] - Limit: Under other criteria, the result may change, and each piece has its limits: parallel branches run on a single server. **The publication** [Read the publication: The five levels of agent systems](https://grailaos.com/papers/five-levels). Five levels of agent systems, where each category stands today according to its sources, and why governing an entire system calls for an operating system. October 30, 2026 · 10 min read. ## An entire company, programmed A chief of staff distributes the work among the agents of each area, workflows wait for whoever approves, and the manager has an assistant of their own. Illustrative example: none of these companies is a customer or a published solution. Each piece carries the label of what runs today. **The org chart: My Store** - **Coordinator**: The chief of staff [Runs today] - **People who decide**: - The manager [Runs today] - **Alongside the person in charge**: The manager's assistant [Runs today] - The warehouse [Runs today] - **Agents by area**: - Sales and customer service [Runs today] - After-sales and complaints [Runs today] - Stock and replenishment [Runs today] - Billing and reconciliation [Runs today] **Its day** - 07:00 · On a schedule: Before opening, yesterday's payments are reconciled with sales. If something does not add up, a notice is left for the manager. [Runs today] - 09:15 · On a schedule: Two sales came in through Mercado Libre. The chief of staff passes them to the stock agent, which reserves the goods in the ERP. [Runs today] - 11:30 · Through a channel: A customer asks on WhatsApp for a $180,000 refund. Since it is over $100,000, it waits for the manager: a notification reaches their phone, they approve it and the money is returned. [Runs today] - 18:30 · By a person: 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 their chat. [Runs today] [The three companies, with their whole day](https://grailaos.com/examples) ## A language, a compiler and a runtime **The three pieces of GrailAOS** - **The language** [Runs today]: A solution is a set of versioned text documents that declare agents, workflows, tools, knowledge, data and their test cases, written inside each agent and each workflow. [The language in detail](https://grailaos.com/language). - **The compiler** [Runs today]: Before anything runs, it verifies the entire solution and returns the errors it finds in a single report, written for a model to read. Same input, same report. [The compiler in detail](https://grailaos.com/language#compiler). - **The runtime** [Runs today]: It operates the solution on every channel, scales by adding replicas, publishes versions without rebuilding the image and hands the conversation to a person when needed. [The runtime in detail](https://grailaos.com/runtime). ## Built to be operated for real A solution isn't finished when it compiles: someone operates it every day. That is why GrailAOS has high availability, extends without touching the runtime and can be observed turn by turn. **What supports it** - Standard [Kubernetes](https://grailaos.com/glossary#kubernetes), today on [k3s](https://grailaos.com/glossary#k3s): replicas, traffic only to ready [pods](https://grailaos.com/glossary#pod) and the new runtime rolled out pod by pod [Runs today] - Workflow runs that keep going even if the server driving them goes down [Runs today] - Your own tools and data at startup, HTTP integrations without a private network, and [MCP](https://grailaos.com/glossary#mcp) as a client [Runs today] - Limit: Several built-in tools depend on configuration or on the [deployment](https://grailaos.com/glossary#deployment)'s startup code. - A [trace](https://grailaos.com/glossary#trace) per turn with its cost, the operations console, and caps that cut off before the next turn [Runs today] - Limit: The turn in progress always finishes; usage notifications are off by default and, like the billed-amount cap, need billing turned on. [The runtime in detail](https://grailaos.com/runtime) ## Measured in the repositories, not estimated Every number carries its source and its date. - **v4.437** Specification version implemented by the runtime. Source: GrailAOS runtime repository, main branch. Measured on October 30, 2026. - **171** Compiler diagnostic codes. Source: Frozen compiler diagnostic registry, in the GrailAOS runtime. Measured on October 30, 2026. - **21,558** Tests declared in the runtime. Source: GrailAOS runtime repository, main branch. Measured on October 30, 2026. - **72.5%** Share of [commits](https://grailaos.com/glossary#commit) attributed to Claude. Source: GrailAOS specification and runtime repositories, main branch. Measured on October 30, 2026. ## Join the waitlist We write rarely, and only when there is something concrete. The developer program is private: there is no open sign-up today, and we'll let you know when it opens. [Join the waitlist](https://grailaos.com/#waitlist) - Looking for a ready-made assistant for your business? [omniatix.chat](https://omniatix.chat/) - Are you a company? [Enterprise](https://omniatix.com/enterprise) ## Frequently asked questions ### Is GrailAOS's source code open? No. GrailAOS is a proprietary engine. Core parts of the platform are the subject of provisional patent applications in the United States, which are pending. ### Which models does GrailAOS use? The agents' providers are the ones in this list, each with its label. Failover never kicks in silently. - **Other providers, through an OpenAI-compatible gateway** [Available on request]: Connecting agents to models from other providers through an OpenAI-compatible [gateway](https://grailaos.com/glossary#gateway): LiteLLM, OpenRouter, or any server that speaks that interface. - **Claude, with failover** [Runs today]: Today agents run on Anthropic's Claude, with a failover that can be turned on, through another Anthropic account or through OpenRouter, and an alert to the operator when the provider fails; [embeddings](https://grailaos.com/glossary#embeddings) are computed with OpenAI. - Limit: The failover is off by default and is turned on together with the operator alerts. ### How do I get access to GrailAOS? A company contracts it from Omniatix, with its own deployment. To evaluate it, also under [NDA](https://grailaos.com/glossary#nda), request more information on the Enterprise page. The developer program is private and in preparation: there is no open sign-up today, and the waitlist will let you know when it opens. [Request more information](https://grailaos.com/enterprise#more-info) ### Which channels does GrailAOS handle? WhatsApp, web chat with the reply shown live, a conversations API to integrate it into another system, and physical voice devices. Phone calls through Telnyx run in part, and Telegram is available on request. WhatsApp, web, API and devices [Runs today] · Phone voice calls [Partial] · Telegram [Available on request] ### Who makes GrailAOS? It is developed by Omniatix, the trade name of Grupo Omniatix Inteligencia Aplicada S.A.S., an Argentine software company.