Why Super Intelligence has to belong to people
The more capable an assistant becomes, the more it matters whom it works for. Rented intelligence answers to its landlord. Here is what owning it takes.
- SI
- ownership
- data
Pre-launch · chapter 5/5 · the network
kyber fusion --joinYour SI needs a cloud you co-own
KyberFusion is the network under the whole system: a sovereign cloud with hardware for SI, for rent. Members contribute hardware and energy and earn tokens for what the network uses; users rent compute and pay in tokens. It is governed as a DAO, built to be anonymous, and it sells no data.
- Contribute capacity, earn tokens
- Rent compute, pay in tokens
- Governed by its members as a DAO
- No data sold, no ads
The problem
The cloud SI runs on today belongs to someone else
Three reasons the current cloud is the wrong home for an intelligence that is supposed to be yours.
err 01
Intelligence is rented from a few landlords
A handful of companies own the models, the machines and the buildings they sit in. You pay the rent twice: once in money, and once in the data and attention their business runs on.
err 02
Idle hardware, rented hardware
Machines sit idle for most of their life, including the one on your shelf, while the same people pay by the hour for capacity somewhere else. Nothing connects the two, so both costs are paid.
err 03
Energy decides more than price lists do
Where and when work runs changes what it costs and what it emits. Almost no scheduling decision takes that into account, because almost no system is given the information.
How it works
Contribute, earn, rent
One loop. Capacity is the currency, and the token is how the network keeps score.
- 01
Contribute
Hardware you own, from a KyberDeck Node on a shelf to a rack in a room, or energy you can supply at particular hours. The network places work on it under rules you set, and only when you say so.
- 02
Earn
Tokens accrue for what the network actually used: measured, recorded and settled on a blockchain ledger that every member can audit.
- 03
Rent
Spend tokens on compute elsewhere in the network when your own is not enough. Your KyberBot can do it for you, inside limits you set.
What it does
A cloud, documented like a terminal
Each line is a promise about how the network behaves, written the way we intend to document it.
| command | what it does |
|---|---|
| kyber fusion rent | Rents compute for a job described by what it needs: capability, deadline, jurisdiction. Paid in tokens, placed by the network, and not tied to your name. |
| kyber fusion contribute --node | Offers your KyberDeck Node's spare capacity to the network, at the hours and for the classes of work you choose. Off by default, and one command turns it off again. |
| kyber fusion vote | Casts your vote on a DAO proposal: pricing rules, admission, what the shared income pays for. Proposals and tallies are public. |
| kyber fusion ledger | Shows what was used, at what rate, and what was settled, under pseudonyms rather than names. Every member can check the same record. |
| kyber fusion schedule --deferrable | Lets work that can wait run where and when energy is cheapest and cleanest, and still finish before its deadline. |
| kyber fusion leave | Takes your node and your work out of the network. No exit fee and no lock-in: the ability to leave is what keeps the network honest. |
Illustrative: the commands describe behaviour. They are not a released CLI, and nothing here moves a token.
What it is
Six parts of a network you co-own
Infrastructure, not a financial product.
01
Bring your own hardware
A Node on a shelf, a rack, a room or one machine. The network does not care who owns the metal, only whether it meets the requirements of the work being placed on it.
02
Multicloud by default
Work is described by what it needs rather than where it runs, so the same job can land on a member's node, a provider in your jurisdiction or a large cloud region.
03
Energy-aware scheduling
Price, availability and carbon intensity vary by place and hour. Work that can wait should run when and where it is cheapest and cleanest, and the scheduler should know that.
04
Built to be anonymous
Jobs are meant to arrive encrypted and unlinked from the person who sent them, so a node sees work rather than a name. That is the goal the design serves, not a claim about today.
05
Governed as a DAO
Pricing, admission, dispute handling and what the shared income pays for are decided by members, in the open, rather than by an operator with its own position in the market.
06
Settlement you can audit
What was used, at what rate, and what was owed, recorded in tokens on a shared ledger so any member can verify it instead of trusting an invoice.
The system
KyberFusion is the last chapter, and the name of the whole
Every layer has its own site. KyberFusion is the one furthest from your hand, and the name for all five together: the four colours fused into one.
kyber stack --from you
01KyberDeck · bodyHardware around you, to buy or to build
02KyberBot · trustThe assistant that knows you and runs the rest
03KyberAgent · handsSwarms of agents doing the work, each in its own cell
04KyberLinux · groundAn ultralight, secure, open system for SI
05KyberFusion · network← you are hereA sovereign cloud owned by the people who use it
↳KYBERIOS · businessThe Kyber stack as one operating system for a small business — built on all five layers, for one job
↳KYBERTIS · servicesThe company that deploys, hardens and supports Kyber, with an SLA — built on all five layers, for one job
One request, end to end
- you speak
- KyberDeck hears
- KyberBot decides, and asks when it matters
- KyberAgent swarms do the work
- KyberLinux keeps each agent in its cell
- KyberFusion lends power, paid in tokens
- the answer comes back to 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.
Contribute
A node on your shelf, a node in the network
A KyberDeck Node spends most of the day waiting. If you want it to, it can lend that spare capacity to the network and earn tokens for what is used. You decide the hours, the classes of work and how much energy it may draw. The network decides nothing for you.
- Off by default. Lending capacity is something you switch on, never something you discover.
- Your memory stays out of it. Work from the network runs in its own KyberCell, sealed off from what your assistant keeps.
- Metered, not estimated. Tokens settle what was actually used, and the meter shows what it drew.
Settlement
The network is the product. The token is the accounting.
Plenty of projects in this space started with a token and looked for a use. This one starts from an operational problem, capacity that cannot move to where it is needed, and the token is how the network keeps score between members who have no reason to trust a bookkeeper.
- A token is a unit of settlement for compute, measured by the network rather than by a market narrative.
- A shared ledger, because every member needs to verify settlement without trusting an operator.
- Income keeps the lights on. Hardware sales, compute rent and whatever else the DAO decides on pay for the infrastructure and fund the five projects. None of it is paid out as a return.
- This is not an offer. Tokens are planned, and we are analysing them under EU law before anything goes live.
Limits
What KyberFusion does not do
A network that asks to be trusted with compute and settlement has to say plainly where its edges are.
- It is not open yet. There is no network to join, no token has been issued, and no payment is taken anywhere on this site.
- It is not an investment. A token is a unit of settlement for compute. It promises no return, profit or price, and we do not invite anyone to buy one. This is not an offer.
- It does not sell your data. No advertising, no data brokerage, no profile of you to rent out. The ecosystem earns from hardware and compute, not from you.
- It is not anonymous yet. Anonymity is what the network is designed for. Until it is built and tested, we will not claim it.
- It does not take your node without asking. A KyberDeck Node lends capacity only when its owner switches that on, and stops the moment its owner says so.
Where we are
No network to join yet, so here is the honest state of it
KyberFusion is the layer where overclaiming would be easiest, because it involves money. So: design, not deployment.
- Now
Scheduler, settlement and governance design
Working out how capacity is measured, how work is placed, how settlement stays verifiable without a trusted operator, and how members make decisions.
- Next
A closed network with pilot members
A small number of members running real work across shared capacity, with settlement observed rather than enforced, while tokens stay in planning and we analyse them under EU law.
- Later
Open membership and the DAO
Public specifications, open admission, and the governance mechanism actually holding the rules rather than being described on a page.
FAQ
Frequently asked questions
What is KyberFusion in one sentence?
KyberFusion is a sovereign cloud with hardware for SI, for rent, settled in tokens and governed as a DAO by members who contribute hardware and energy, and it is also the name of the whole Kyber ecosystem.
What does SI mean here?
Super Intelligence. Most of the industry still uses an older two-letter name for it, as the footer of every page notes. 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.
What is the token? Is this a crypto project?
A token is a unit of settlement for compute: earned by contributing capacity, spent on renting it, recorded on a blockchain ledger members can audit. It promises no return, profit or price, there is no sale, and nothing on this site is a financial promotion or investment advice. Tokens are planned, and we are analysing them under EU law. This is not an offer.
Who governs it, and who pays for it?
Members do, as a DAO: pricing, admission, dispute handling and what the shared income pays for. The ecosystem earns in several ways together, from hardware sales, compute rent and other streams the DAO decides on, and that income keeps the infrastructure running and funds the five projects. The governance design will be published before anyone is asked to rely on it. This is not an offer.
Is it really anonymous?
That is what it is built for: jobs that arrive encrypted and unlinked from the person who sent them, nodes that see work rather than names, settlement that does not need an account in your name. It is a design goal, not a claim. When there is something to test, the method will be published with the result.
Why is it also the name of the whole system?
Because it is where the five meet. KyberDeck is the body, KyberBot the assistant you trust, KyberAgent the swarms that do the work, KyberLinux the ground they stand on, and KyberFusion the network that lends power when a device is not enough. Its colour is the other four at once.
Where does KYBERIOS fit?
KYBERIOS is a branch of the ecosystem: the five layers put together as one operating system for a small business. When the office server is not enough, it borrows power from KyberFusion and settles in tokens, like any member. This is not an offer.
Chapter 5/5 · Network
Chapter five: the network
A body, an assistant you trust, hands that do the work, ground they stand on: none of it is enough on its own. Some jobs will always be bigger than anything you carry, and today the only place to take them is a cloud owned by a few companies whose business is your data and your attention.
So the last layer has to be shared the way the first one is owned. KyberFusion is a network its members hold together: they bring hardware and energy, rent what they need, settle in tokens on a ledger anyone can read, and set the rules as a DAO. It sells no data and shows no ads. What the ecosystem earns keeps the machines running and pays for the work on all five layers.
Which brings the story back to where it started: to you, holding a card on a lanyard. The network is worth building only if every request that leaves your hand comes back to it, and nothing about you stays behind. That is the whole of it, and it is all in the manifesto.
Blog
All articlesNotes from the network
From a node on your shelf to a node in the network
A home node idles most of the day. Lending that capacity is a question of consent, isolation and energy, not of technology. Here is how a Node is meant to join.
- home node
- capacity
- energy
What a cloud node knows about you
When your work runs on someone else's machine, the content is only part of what leaks. Account, payment, metadata and logs say more. Here is what a node should see.
- privacy
- anonymity
- cloud
Be there when the network opens
The waitlist goes live soon. Until then, the manifesto says what we are building and the blog argues how.
No form yet, no data collected, no tokens on offer — just come back.