KernelHub Three redemptions, ninety days
Share your referral code with people who would get something out of KernelHub. Once three of them have actually redeemed it, 90 days are added to your own access. That is the whole thing — there is nothing else to read.
3 successful redemptions = +90 days of access for you. Same account, same workspaces, same six permission tiers — the only thing that moves is your expiry date.
How it works
Three steps, and only the middle one is out of your hands.
You share your code
Your referral code and its link come from the CLI on your own machine. In any paired project folder, run icloser referral — it prints the code and the share link. Send it to whoever you like, as many times as you like; sharing costs you nothing and is not limited.
They redeem it
The person you sent it to installs KernelHub, opens the app on their own phone, and enters the code. Their account activates. That moment — the redemption succeeding — is the event that gets counted.
At three, you get 90 days
When the third redemption succeeds, 90 days are added to your access. Run icloser referral again to see the new expiry date, and the Access screen in the app will show it too — it is the same access, read from the same server.
What counts, and what does not
This is the part worth reading twice. Handing out the link is not the thing being counted — someone else redeeming a code is.
A redemption that succeeded
Someone entered your code in their own KernelHub app and their account activated. The server accepted it. Your number goes up by one at that moment, not before.
Everything that stops short of that
Posting the link. Someone clicking it. Someone landing on the download page. Someone installing the app and never entering a code. A conversation where they say they will get around to it. None of those move the number, however many of them there are.
Whether a redemption counted is decided in the same place your access itself is checked — on the server, not on your machine. Reinstalling, switching phones, or pairing another machine does not reset what you have already earned, and editing anything on your side does not add to it.
Where to check your progress
Run icloser referral in a paired project folder. It prints your code, how many redemptions have actually succeeded, and how many are still needed. The days you have left and your expiry date stay where they always were — on the Access screen in the app.
| Your referral code and link | icloser referral, on your own machine |
| How many redemptions have succeeded | icloser referral, on your own machine |
| How many are still needed | 3 minus the number that succeeded |
| The 90 days, once you reach three | Added to your access; the new expiry date shows in the app and in the CLI |
Those numbers come from the server, not from your machine — what you read there is what the server will act on.
What this is not
Written down so nobody has to guess. If it is not on this page, it is not part of the programme.
No leaderboard
There is no public ranking, no board, and no way for anyone else to see your number. Your count is yours and the server's.
No cash
The reward is access time and nothing else. There is no payout, no commission, no credit balance, and no way to turn the 90 days into money.
No multi-level
You are credited for the people who redeem your code. You are not credited for the people they later refer. The chain is one link long, on purpose.
No change to what you can do
A referral adds days. It does not add permission tiers, seats, workspaces, Runtimes, or anything else. Someone who never refers anyone has exactly the same product you do.
Getting started
You need an activated account before you have a code to share. If you already have one, run icloser referral in a paired project folder and your code is there.