Pre-launch · a Kyber branch · business
kyber ios --company initKYBERIOS is the intelligent operating system for a small or medium business, built from all five Kyber layers. One data model and one system of action replace the patchwork of ERP, CRM, warehouse software and spreadsheets. Every employee gets a KyberBot, swarms of agents run the processes under rules you can read, and the company's data stays on the company's ground.
The cost of a fragmented stack is never in the licences. It is in the people who carry the joins.
The invoicing program, the customer list, the stock spreadsheet and the shop each hold a fragment of the same order, in a different shape, updated at a different time. None of them can say whether it will ship on Thursday.
The joins happen in someone's head and inbox: retyping an order, checking stock by phone, chasing a payment. The company moves only as fast as those handovers, and slows down when that person is on holiday.
Rented SI tools want the company's documents, customers and prices on their servers, one account per employee, under someone else's terms. What staff paste into them stops being only the company's.
An operating system, not another subscription. It arrives as software the company installs and controls.
KYBERIOS runs on KyberLinux on a server the company owns, in the office or the back room. Models included. Nothing has to leave the building for the system to think, and when it needs more power, KyberFusion lends it only where a rule allows.
It starts beside what you already run, reading, not writing. KYBERIOS earns write access one process at a time, after it has been right about that process for long enough to show it.
You write down what agents may decide, what they may do, up to which limits, and what waits for a person. The system enforces it below the agents, logs it, and can explain any action after the fact.
Each line is a promise about how the system behaves, written the way we intend to document it.
| command | what it does |
|---|---|
| kyber ios order | Takes an order from wherever it arrived, checks stock, credit and price, reserves the goods and drafts the confirmation. Anything outside policy waits for the person who owns it. |
| kyber ios stock | One stock figure for the shop, the warehouse and the van. A pick confirmed on a Band changes the record once, and every program that needs it reads the same number. |
| kyber ios invoice | Drafts invoices from what was actually delivered, matches incoming payments and lists what is overdue. Sending one is a step a person or a written policy approves. |
| kyber ios close-month | Gathers the month in one model: sales, costs, stock movements and open items, with a list of what still needs a human decision. Your accountant reviews it; the system does not sign anything. |
| kyber ios policy | Opens the company's rules: who and what may order, pay, discount, release or delete, and up to which limits. Plain text, versioned, enforced below the agents. |
| kyber ios why | Answers why any record looks the way it does: which person or agent acted, under which rule, with what evidence, in order. Readable without us. |
Illustrative: the commands describe behaviour. They are not a released CLI.
Not a suite with a chat box bolted on. A layer that owns the resources, schedules the work and enforces the rules.
Orders, stock, cash, people and projects live in one model instead of being reconciled across five programs and three spreadsheets. There is nothing to integrate because nothing was split.
Each person gets their own assistant at work, with two memories kept apart: the company's, which belongs to the company, and their own, which belongs to them.
Orders, invoices, stock and reporting run as KyberAgent swarms: a planner and sub-agents with one job each, every agent in its own KyberCell, scheduled and supervised like any other process.
What may be suggested, what may be done, by whom and within which limits: declared in plain text, enforced by the system, recorded for the owner, the accountant and the auditor.
A few set points the system watches without being asked: cash, lead time, stock, and the error rate of its own agents. When one drifts, it narrows its own autonomy and hands more back to people.
KyberLinux on hardware the company owns, local models, open source as the intent. No document, order or customer name has to leave your network for the system to do its job.
Not a sixth layer. KYBERIOS takes all five, the hardware, the assistant, the swarms, the system and the network, and puts them to one job: running a small business.
kyber stack --from you
The company's data stays on the company's ground at every step. When the office server is not enough, KyberFusion lends compute, paid in tokens. Tokens settle compute between members; this is not an offer.
Most of a small business does not happen at a desk. It happens at the counter, in the warehouse, on the shop floor and at a customer's site. KYBERIOS meets people there in KyberDeck forms, running the same KyberLinux and the same company policies as the office server, and working on when the signal drops.
A KyberDeck Node or any server the company owns, running KyberLinux, sits in the back office and holds the company memory, the ledger and the cells the agents work in. When month end or a large report needs more than the box has, KyberFusion lends the power: the job leaves encrypted, under a rule you wrote, to a network built to keep it unlinked from the company.
Software that wants to run a company earns trust by saying plainly where it stops.
KYBERIOS is pre-launch. The roadmap is public because a case study would have to be invented.
The pieces everything else depends on: one model for orders, stock, cash and people, the rules agents work under, and a KyberBot that keeps company memory and private memory apart.
A small number of companies running KYBERIOS next to what they already use, reading first, then taking over one process at a time.
Source, the data model, the policy specification and a guide to running the office server, published together, so a company can read what runs it.
KYBERIOS is the intelligent operating system for a small or medium business: one data model and one system of action instead of the ERP, CRM and spreadsheet patchwork, with a KyberBot for every employee, agent swarms running the processes under the company's own policies, and the data on the company's own ground.
Super Intelligence, the name we use for the whole field. Most of the industry still calls it by an older name, which the footer of every page spells out. We say SI because of what is coming, the most capable tool people have ever had, and because of whom it should belong to: for a business, the business that uses it, not the vendor that rents it out.
Eventually, in the sense that the reason to keep separate programs for invoicing, customers and stock disappears when one model holds the data and one system acts on it. In practice it starts beside what you already run, reading only, and takes over processes one at a time, in the order of how much pain they cause today.
The company owns the company memory: orders, customers, prices, documents. The employee owns their private memory: their notes, reminders and what they told their assistant about themselves. The two are kept apart by design, and when someone leaves, the company keeps its records and the person keeps theirs.
Closed pilots come first, then an open release, and neither has a date we would stand behind yet. Pricing is not set, and we would rather say so than publish a number we will change. Nothing is for sale.
KYBERIOS is a branch, not a chapter. It uses all five: KyberDeck forms on the floor, a KyberBot for every employee, KyberAgent swarms for the processes, KyberLinux on the server and the devices, and KyberFusion for extra power, the sovereign cloud owned by the people who use it.
You can run it yourself: the systems underneath are open. If you want someone accountable, KYBERTIS, the second Kyber branch, deploys it on your own server, hardens it and supports it with an SLA and an exit clause in the contract.
The Kyber story is about whom intelligence belongs to. For a person the answer is: to them, on hardware they hold. A company faces the same question with more at stake. Its orders, prices, customers and margins are what the company is, and most tools on offer today want all of them on someone else's servers, read by a model that answers to someone else.
The same principles hold one size up. Data belongs to whoever it is about: the company's records to the company, an employee's private memory to the employee. Systems should be open, so a company can read what runs it and replace a part without leaving the whole. And the rules agents work under should be written down, in plain text, where an owner, an accountant or an auditor can read them.
KYBERIOS is not a chapter of that story but a branch of it: the five layers put to work for one business. The story itself starts with something you can hold in your hand, and that is chapter one.
Company ground has borders: the external accountant, the bank, the tax authority, the marketplace. How a sovereign system hands data across them without moving itself.
An order of operations for an owner: one trusted data source, one assistant for one person, policies before agents, devices last. And what to leave disconnected in week one.
Android XR brings glasses, Gemini and multi-step tasks to the workplace. For a small company the question is whose account, assistant and cloud hold its work.
The waitlist goes live soon. Until then, the blog is where the design gets argued: the data model, the policies, the floor and the server room.
No form yet, no data collected — just come back.
