Pre-launch · waitlist not open yet
The data model comes before the form
We are building the parts everything else depends on: one data model, the policy engine and a KyberBot that keeps company memory and private memory apart. 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 KYBERIOS is ready to run on a server that is not ours.
We are building
The data model, the policy engine, the employee KyberBot and the first process swarms. That is where the week goes, not into this page.
A waitlist, later
One field, no sales calls, no drip campaign, no reselling your address. Nothing is for sale and no payment is taken.
Come back
The blog moves first. New posts mean the design is settling.
Why there is nothing to fill in
A waitlist that collects addresses months before there is anything to install is a mailing list with extra steps. For a project whose argument is that a company’s data should stay with the company, starting by collecting yours would be an odd way to begin.
What happens when it opens
The form will take an email address and, optionally, what your business does and which programs it runs today, because the first pilots will be grouped by the shape of the work (a workshop, a wholesaler, a service company) rather than by size. Nothing else. No budget range, no phone number for a follow-up sequence, and no payment, because nothing is for sale.
The rest of the story
KYBERIOS is a branch of the Kyber story, not a chapter: the five layers put to work for a small business. The hardware on the floor is KyberDeck, the assistant every employee gets is KyberBot, the swarms that run the processes are KyberAgent, the system on the server and the devices is KyberLinux, and the network that lends compute when the office server 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: why a small business needs an operating system, not another app, a KyberBot for every employee and whose memory is whose, processes run as swarms, and company data on company ground.
No form, no tracking pixels lying in wait — just work in progress.