Waitlist opens soon

The image comes before the form

We are building the base image, the boot chain, the SI runtime and the isolation every KyberCell stands on. When the sign-up form goes live it will ask for one thing, an email address, and use it for exactly one thing: telling you the repositories are public.

We are building

Base image, verified boot, atomic updates, KyberCells. That is where the week goes, not into this page.

Waitlist soon

One field, no sales calls, no drip campaign, no reselling your address.

Come back

The blog moves first. New posts mean the image is settling.

Why there is nothing to fill in

A waitlist that collects addresses months before there is anything to boot is a mailing list with extra steps. It would also be a strange first move for a system whose whole argument is that it should contain only what it needs, and report on nobody.

What happens when it opens

The form will take an email address and, optionally, the hardware you would run KyberLinux on, because the reference images will be chosen by what people actually have rather than by what is convenient to build. Nothing else.

If you build systems for a living

If you work on minimal images, verified boot, kernel isolation or supply-chain tooling, you are exactly the person we want reading the image definition when it is published. The same goes for anyone who has spent years tuning a keyboard-first desktop and has opinions about defaults. Claims about minimalism and verifiability are worth what they can be checked against.

Where the rest of the story lives

KyberLinux is chapter four of five. The hardware that boots it is on KyberDeck, the assistant that runs on it is KyberBot, the swarms that work in its cells are KyberAgent, and the cloud whose nodes run it is KyberFusion. None of them is taking sign-ups yet either.

In the meantime

The blog carries the reasoning: why a general-purpose distribution is the wrong base, how KyberLinux keeps a swarm in its cells, why a system for SI should be keyboard-first, and why the power budget is a design constraint rather than a benchmark.

No form, no tracking pixels lying in wait — just work in progress.