Pre-launch · kernel and policy engine in build
One operating system for the whole company
KYBERIOS is a sovereign, AI-native OS — a system of action that replaces the ERP, CRM and WMS stack with one data model, one login and one place where decisions are made and carried out.
- One system, one login
- Runs on your own infrastructure
- Agents, robots and devices on one kernel
Eleven systems, and none of them in charge
The cost of a fragmented stack is never in the licences.
Eleven systems, eleven truths
The ERP, the CRM and the warehouse each hold a fragment of the same order, in a different shape, updated at a different time.
Integration is a permanent project
Connectors break, schemas drift, and the map of what talks to what lives in one person's head. The work never finishes because it cannot.
People are the integration layer
The joins between systems happen in someone's head, at human speed, and the company only moves as fast as those handovers.
Run it, point it, delegate to it
An operating system, not a subscription. It arrives as software you install and control.
- 01
Run it where you want
Your hardware, your colocation, your European provider. Models included. Nothing has to leave the building for the system to think.
- 02
Point it at the business
Read-only connectors into what you already run. KYBERIOS earns write access one process at a time, after it has been right about that process for a while.
- 03
Delegate with policy
You define what agents may decide and what they may execute. The OS enforces it, logs it, and can explain any decision after the fact.
An operating system, in the original sense
Not a suite with a copilot bolted on. A layer that owns the resources and schedules the work.
One data model
Orders, stock, cash, people and projects live in one model instead of being reconciled across eleven. There is nothing to integrate because nothing was split.
Agents as first-class citizens
Agents are not a feature in a menu. They are processes the OS schedules, bounds and supervises, the same way it does everything else.
One kernel for software, robots and devices
The agent on the server, the robot on the floor and the deck in your pocket run the same policies, the same identities and the same audit trail.
Sovereign by construction
Local models on infrastructure you control. No document, order or customer name has to leave your network for the system to do its job.
A policy engine, not a prompt
What may be suggested, what may be executed, by whom and within which limits — declared explicitly, enforced by the system, recorded for the auditor.
Open and composable
Built on an open, composable platform. If a layer does not fit your business, replace that layer instead of leaving the system.
A system of action, not another system of record
Business software mastered two categories. Systems of record store what happened. Systems of engagement collect it. The part nobody automated is a human reading both, deciding, and typing the result back in. That gap is the product.
- It reads across the whole business, not one domain — so the join happens in the system, not in a person.
- It runs unprompted. State changes trigger work; nobody has to open a report first.
- It decides with a rationale — the recommendation arrives with the evidence and the confidence attached.
- It executes within policy. The line between suggesting and doing is configuration, and it is always logged.
Agent, bot and deck — one kernel
KYBERIOS is the layer the rest of the Kyber system stands on. The same identities, the same policies and the same audit trail, whether the work is done by software, by a machine on the floor or by the device in someone's pocket.
- KyberAgent — the autonomous agent: ontologies, graphs, a homeostat and the safety policies that bound it.
- KyberBot — the same OS for physical robots, with the harness and limits that physical work demands.
- KyberDeck — the hardware people actually carry: a card, a wrist device, a deck in a pocket, holding a personal or business agent.
- One kernel underneath all three, so a policy written once applies everywhere it should.
No release to download yet — so here is the honest state of the build
KYBERIOS is pre-launch. The roadmap is public because a case study would have to be invented.
- Now
Kernel, data model and policy engine
The three pieces everything else depends on, built against real operational data rather than a demo dataset.
- Next
Closed pilots with agent and deck
A small number of companies running KYBERIOS beside their existing stack, in read-only mode first.
- Later
Open platform release
General availability with published deployment guides, the policy specification and an audit package.
Frequently asked questions
What is KYBERIOS in one sentence?
KYBERIOS is a sovereign, AI-native operating system for a company: one data model and one policy engine that replace the ERP, CRM and WMS stack, and on which agents, robots and devices all run.
What does system of action mean?
A system of record stores what happened and a system of engagement collects it. A system of action closes the loop: it reads across the whole business, notices when reality drifts from plan, decides what should change and carries it out within the limits you set.
Does it replace our ERP?
Eventually, in the sense that the reason to have separate ERP, CRM and WMS products disappears when one model holds the data and one system acts on it. In practice it starts above what you already run, read-only, and takes over processes one at a time.
How do KyberAgent, KyberBot and KyberDeck fit in?
They are the same system in three bodies. KyberAgent is the autonomous agent, KyberBot runs physical robots, KyberDeck is the hardware people carry. KYBERIOS is the kernel underneath, so identities, policies and audit trails are shared rather than reimplemented.
Is it open source?
The platform is built to be open and composable, so a layer that does not suit your business can be replaced without leaving the system. Licensing details will be published with the first release rather than promised now.
When can we use it and what will it cost?
Closed pilots come first, then an open release. Pricing is not set, and we would rather say so than publish a number we will change. The waitlist opens shortly.
Be in the first cohort
The waitlist form goes live soon. Until then, the blog is where the design decisions get argued.
No form yet, no data collected — just come back.