Pre-launch · waitlist not open yet
The boards come before the form
We are getting small models to run usefully inside a carried device's power and thermal budget, in five forms. When a sign-up form goes live it will ask for one thing, an email address, and use it for exactly one thing: telling you there are units.
We are building
Prototype boards, the model runtime and five forms: Card, Band, Pocket, Node and Core. That is where the week goes.
A waitlist, later
One field, no sales calls, no drip campaign, no reselling your address. Nothing is for sale and no payment is taken.
Or build your own
A microcontroller SDK and a Linux SDK are planned. Neither is released yet; the blog will say when they are.
Why there is nothing to fill in
A waitlist that collects addresses months before there is anything to ship is a mailing list with extra steps. For a project whose whole point is that your device should not quietly collect things about you, starting that way would be a poor look.
What happens when it opens
The form will take an email address and, optionally, which of the five forms you would actually carry or build — because the first pilot units will be built in the shape people say they want rather than the one that demos best. Nothing else. It will not ask for payment, because nothing is for sale.
Hardware timelines are the ones people exaggerate
So here is the honest version: prototype boards and the model runtime now, pilot units in all five forms next, then open hardware, both SDKs and the KyberLinux image published together. If any of that starts slipping, the blog will say so rather than going quiet.
The rest of the story
KyberDeck is chapter one of five: the body. The assistant that lives in it is KyberBot, the swarms of agents it hands work to are KyberAgent, the system underneath all of them is KyberLinux, and the sovereign cloud that lends power when a device is not enough is KyberFusion. Each has its own site and its own honest state of the work.
In the meantime
The blog carries the argument: the five forms and why there are five, building your own once the SDKs ship, the home node that keeps your assistant’s memory, and hardware that does not report on you.
No form, no tracking pixels lying in wait — just work in progress.