Pre-launch · chapter 1/5 · the body
kyber deck --whoamiKyberDeck is the hardware around you that your personal assistant lives in: a card on a lanyard, a unit on your wrist, a pocket deck, a node at home, a robot. Buy one ready-made or build your own. Every one runs KyberBot on KyberLinux, and none of them works for anyone but you.
Three reasons a phone is the wrong body for an assistant you are supposed to trust.
Its business model is attention and distribution. Every design decision serves that, and an assistant working quietly on your behalf is not what the platform is optimising for.
Ask it anything and the question leaves the building. On a device you carry everywhere, that is a running record of your day held by somebody else.
Locked bootloaders, a vendor operating system, and a permission model designed for apps rather than for something acting on your behalf.
Each form exists because the hands are doing something different. Same KyberLinux, same KyberBot, same identity: the body changes, the system does not.
in designIdentity, presence and a glance. A card-sized computer on a lanyard that hears you, shows one line, and knows who you are to the building.
in designFor work where the hands are busy. Voice and a glance on the wrist, with a slider that makes it deaf.
prototype boardsThe cyberdeck. A screen and a real keyboard for when the task deserves them, and a terminal into your own systems.
in designThe one that stays home. It bridges your devices, keeps the long memory local, and lends spare capacity to KyberFusion only when you say so.
in designA compute module for robots. The same assistant with wheels and hands, inside the limits KyberBot enforces in the physical world.
Every form will have an open reference design, and the same system runs on boards you already own.
Make your own ↓Pre-launch: nothing here is for sale, and the specifications are design targets rather than measured results. The waitlist is not open yet, so joining it collects nothing for now.
If you would rather solder than wait, the same system will run on hardware you already have. Two paths, both open.
For small things: a button, a microphone, a screen and a radio. The board listens and shows; KyberBot runs on a Node or a Pocket nearby.
For anything that runs Linux: install KyberLinux and KyberBot runs on the device itself, small models included.
Not released yet. These commands show the shape the SDKs will take; today they do nothing. When they ship, bricked boards and voided warranties are yours, and so is everything you build.
A plan, not a compatibility claim. Nothing on this list has been tested or certified, and no maker listed here is a partner.
Each line is a promise about how the hardware behaves, written the way we intend to document it.
| command | what it does |
|---|---|
| kyber listen | Captures and transcribes on the device. Nothing leaves it unless a policy you can read says it may. |
| kyber mute --hard | A physical switch cuts the microphones and the camera. Not a setting: a circuit. |
| kyber offline | Keeps working out of coverage: capture, context, the day's notes. Sync waits until there is something to sync to. |
| kyber whoami | One identity, the same one your KyberBot acts under, across every form you own. |
| kyber ask bot | Hands anything bigger than the device to KyberBot, which decides whether it runs here, on your Node, or in KyberFusion. |
| kyber repair | Documented parts and published schematics, so a broken part means a repair rather than a replacement. |
Illustrative: the commands describe behaviour. They are not a released CLI.
The deck is where you touch the system. Every other layer sits one step further from your hand, and each one 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.
Carried devices are small on purpose, so something has to remember. The Node sits on a shelf, holds the long memory your assistant works from, and runs the jobs that are too big for a pocket but too personal for anyone else's server.
KyberDeck Core slides into a robot, and the assistant that knows you gets a body that moves. With mass come rules: where the machine may go, how fast, what it may touch. KyberBot enforces them on board and writes every motion down.
Pre-launch hardware earns trust by saying plainly where its edges are.
Hardware timelines are the ones most often exaggerated. Ours are on this page instead.
Getting small models running usefully within a carried device's power and thermal budget, which is the constraint everything else has to fit around.
A small number of devices with people running real work on them, in the form that fits their hands rather than the one that demos best.
Schematics, both SDKs and the OS image published together, because a device you carry all day should be one you can inspect.
KyberDeck is the hardware your personal SI lives in — a card, a wrist unit, a pocket deck, a home node or a robot module — running KyberBot on KyberLinux, ready-made or built by you.
Super Intelligence, the name we use for the field as a whole. We use the word 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.
That is the plan. A microcontroller SDK for small listening devices and a Linux SDK for anything that runs Linux. Neither is released yet; when they are, they will be open.
For some people, eventually. Today it replaces the assistant-shaped part of what a phone does: capture, context, decisions and identity. It is designed as a tool you own rather than as a platform that sells to you.
Yes, by design. A carried device spends real time out of coverage, so capture, transcription and the day's context work without a link, and synchronisation happens when there is something to synchronise to.
KyberDeck is the body. KyberBot is the assistant that lives in it, KyberAgent is the swarm of agents it sends to do the work, KyberLinux is the system underneath all of them, and KyberFusion is the sovereign cloud that lends power when a device is not enough — owned by the people who use it. KYBERIOS, a branch of the same stack, puts these devices to work in a small business: a Band in the warehouse, a Card at the door, a Node as the office server.
Every intelligence so far has lived somewhere you do not: in a data centre, behind an account, inside a business model that needs your attention more than your trust. Super Intelligence will be the most capable tool people have ever had, and the question that matters is not whether it arrives, but whom it belongs to.
Our answer starts with something you can hold. A card, a band, a deck, a box on a shelf, a robot in the hallway: hardware you own outright, that you can open, repair, and switch off with a real switch. If the body is not yours, nothing that runs inside it is.
The body is only the beginning. Inside it lives the one that knows you best, and that is the next chapter.
A weekend plan for a cyberdeck that is yours down to the microphone. The SDKs are not released yet, so the commands are illustrative; the habits are not.
A card, a band, a pocket deck, a home node and a robot module: why one assistant needs five bodies, what each one is for, and which ones you can build yourself.
Most connected devices report on their owners by design: telemetry, accounts, cloud processing. This is what hardware looks like when there is nothing to report.
The waitlist goes live soon. Until then, the blog is where the hardware decisions get argued.
No form yet, no data collected — just come back.
