Pre-launch · chapter 4/5 · the ground
kyber install --profile siKyberLinux is an ultralight, secure, open-source operating system for SI. Opinionated and keyboard-first, with defaults worth keeping and one command to install. The same system runs on a KyberDeck Card, inside a robot and on a KyberFusion cloud node, and it is what keeps every KyberAgent in its own KyberCell.
Three costs you inherit when the ground under your assistant is a distribution made to run everything.
A device running models does not need a print server, a display stack it never draws on or three scripting languages. Every one of them is something to patch, something to audit and something that can break.
General distributions hand you parts and a free weekend. Hardening, updates, the model runtime and isolation for agents are left as exercises, and no two installs end up the same.
On a card on a lanyard, a robot on battery or a node on a shelf, watts spent on background services are watts not spent on the model.
The image holds what the job needs and nothing else. The rest of the design follows from that.
One command and a profile give you a finished system, with defaults chosen by people who use them every day. No evening spent picking a bootloader, a launcher and a firewall. The command at the top of this page shows the shape; it does not exist yet.
Read-only root, verified boot, kernel lockdown and least privilege for every service. Not a checklist someone works through after installation, but the state the system starts in, every time.
The model runtime is part of the base system and every agent gets its own KyberCell, so memory, accelerators and permissions are handed out by something that knows what an agent is.
Two keys for the things you do all day, one command for each thing the system promises. This is how we intend KyberLinux to feel.
| keys or command | what it does |
|---|---|
| super + space | Opens the launcher: programs, files, settings and commands from one line, without reaching for the mouse. |
| super + a | Talks to KyberBot. Speak or type; the assistant answers in a panel and asks you before anything sensitive. |
| kyber update | Writes the next system image to a second slot and switches at reboot. Either the new image comes up or the old one does; there is no half-updated state. |
| kyber rollback | Returns to the previous image. A reboot, not a rescue procedure, and it happens by itself when a new image fails its health check. |
| kyber cell ls | Lists the running KyberCells: which agent, which files it can see, which network rules apply and what it is doing now. |
| kyber verify | Checks the running image against its published hash and signature, so the system you run is the system that was built. |
Planned defaults, not a release. The bindings and commands show the design; none of them can be installed or run today.
Boring where infrastructure should be boring, opinionated where you touch it.
A read-only root and a boot chain checked from firmware up, with every service running under least privilege. The system that starts is the system that was built, and drift between the two stops being possible.
Updates are whole images that apply at once and roll back if the machine does not come up. No half-updated system on a device nobody can visit.
Running models is first-class work, not a container fighting a scheduler designed for web servers and desktops. Memory, accelerators and thermal headroom are planned for it.
Kernel-level isolation for every agent: files and processes fixed when the cell is created, network closed by default, every step logged. A feature of the system, not something bolted on top.
One launcher, consistent key bindings, a terminal that is a first-class citizen and a look worth keeping. Decisions made once and written down, so you start working on day one instead of configuring.
The image definition is public and the build is meant to be reproducible, so anyone can check that what runs matches what was published.
KyberLinux is the ground the other layers stand on. The deck boots it, the assistant and the swarms run on it, and the cloud nodes run it too. Each layer has its own site.
kyber stack --from you
Your data stays yours at every step: on the device whenever it can be, encrypted and unlinked from you in the cloud when it has to go there. Tokens settle compute between members; this is not an offer.
KyberLinux is meant to arrive on a key you can write-protect and to start only what was signed. Each stage checks the next, from firmware up, so a machine left in a bag, a hallway or a rack cannot be made to boot something else without a key you hold.
KyberLinux is not tied to our hardware. The reference targets are the KyberDeck forms, robot controllers and cloud nodes, and the image definition is public, so a board on your desk is a question of drivers rather than permission.
An operating system that is not published yet earns trust by saying plainly where its edges are.
KyberLinux is pre-launch. An operating system that has not been published should say so plainly.
The minimal image, verified boot, atomic updates and the isolation KyberCells need, built and rebuilt against the hardware the rest of the family runs on.
One for carried devices, one for robots, one for cloud nodes: the same base in honest configurations, with the keyboard-first desktop on the ones that have a screen.
Image definitions, the build pipeline, signatures and the one-command install published together, so the claim that it is minimal and verified is something you can check.
KyberLinux is an ultralight, secure, open-source operating system for SI — immutable, verified at boot, updated atomically and keyboard-first — that runs the same on a KyberDeck Card, a robot and a KyberFusion cloud node, and keeps every agent in its own KyberCell.
Super Intelligence. Most of the industry still uses an older name for it, and the note at the foot of every page spells that out once. We say SI because of what is coming, and because of who we think it should belong to: the people who use it, not the companies that rent it out.
Because the alternative is taking one built for everything, trimming it and hardening it by hand on every machine, again and again. When the work is SI and the hardware is small, a declared minimal base is less work and far easier to verify. And because a system you use every day deserves opinions worth borrowing.
A KyberCell is the isolated sandbox every KyberAgent runs in: files and processes fixed when it is created, network closed by default with per-program rules, secrets injected only at the authorised endpoint, every step logged. Isolation that strong has to come from the kernel, which is why KyberLinux provides it rather than a program running on top.
Lighter, yes, by construction: a system with fewer components has fewer components. Power depends on the workload and the hardware, and a single number without both tells you very little. What we commit to is treating idle draw as a design constraint and publishing it per reference image once there are images to measure.
KyberLinux is the ground. KyberDeck is the hardware that boots it, KyberBot is the assistant that runs on it, KyberAgent swarms do the work inside its KyberCells, and KyberFusion — the sovereign cloud, and the name of the whole ecosystem — runs it on every node.
Yes. KYBERIOS, the branch of the Kyber stack for small businesses, runs on KyberLinux: the office server, the warehouse devices and the cells its agents work in.
Everything so far stands on something. A body you hold, an assistant you trust, hands that do the work: none of it is yours if the system underneath answers to someone else. An operating system decides what runs, what it may touch and who may change it, and most of the systems under today's intelligence were never meant to be read by the people who depend on them.
Our answer is a system small enough to read, checked every time it starts, and the same on a card, a robot and a server. It has opinions, so you are not left assembling it, and it has walls, so every agent works in its own cell and nowhere else. Open source, reproducibly built, and boring exactly where boring means safe.
Ground is still only ground. When the work outgrows the device in your hand, the same system runs on a node in a cloud owned by the people who use it, and that network is the last chapter.
Kyber is a Linux block I/O scheduler built for fast SSDs and NVMe. How its latency targets work, how to switch to it and when mq-deadline, BFQ or none is the better choice.
Agent loops with people at the decision points are coming to bookkeeping and purchasing. They will land on machines with no admin, so the system must supply the conditions.
NVIDIA's reference architecture for agent security names Canonical, SUSE, Red Hat and Windows, not Debian. What that says about choosing a base for agents.
The waitlist goes live soon. Until then, the blog is where the design decisions get argued.
No form yet, no data collected — just come back.
