Instances in use
Expires
Machines signed in
Plans on this key
Your licence key
What the app signs in withPlans on this licence
Machines that have signed in with this key
Your licences Licence
This licence could not be loaded.
The server answered, but not with this licence. Nothing on your account was changed.
Your licences Main
Main
FollowBot · 2 plans pooled · created 4 March 2026 · never revoked
Instances in use
4 of 10
Expires
24 days
14 September 2026 · both plans
Machines signed in
4
nothing is locked to them
Plans on this key
2
5 instances each, pooled to 10
Your licence key
What the app signs in with
•••••-•••••-•••••-C7Q2A
128 bits of randomness. It cannot be guessed, which is why there is no account lockout here and no stranger can lock you out of your own software.
Ending in —Use Show key below
Show key reveals the full key whenever you need it. If it was shared or leaked, re-issue it below: a new key replaces it and the old one stops working.
New key issued — copy it now.
Show key brings it back whenever you need it. Every running instance must be updated to it — the old key stops working now.
4KQF9-M2TXW-7DH3N-C7Q2A← your licence key
← leave it empty
☑ Remember passwordSign in
This is the app’s normal sign-in box. Put the key in once per machine, leave Password empty, and tick Remember.
Shared this key with someone and want it back? Re-issuing generates a new key immediately and stops the old one working. The 4 instances running now will be cut off until each has the new key saved — your plans and expiry are untouched.
reissue_licence_keyPlans on this licence
Pooled · 10 instancesEach plan you buy is its own line with its own dates. They pool into one allowance by default. Renew a line on its own, or split it out onto its own key.
FollowBot — 5 instances
Bought 4 Mar 2026 · renewed 5 times · paid in USDT · expires 14 Sep 2026 · receipt
split_grant
Renew — $30
FollowBot — 5 instances
Bought 11 Jun 2026 · renewed twice · paid with PayPal · expires 14 Sep 2026 · receipt
split_grant
Renew — $30
FollowBot — 5 instances
Bought · paid via PayPal · ref · expires
Last live plan here. Your username signs FollowApp in to this licence; split this plan out and the username finds no plan. Use the new licence’s key for it instead.
split_grant
Renew
No plan on this licence yet. A purchase, a trial or a plan split out of another licence will appear here.
Splitting is not a purchase and interrupts nothing. The plan keeps its expiry and its receipt; only which key it feeds changes.
Split from this licenceYour other licences
Licences whose plans came from MainAny of them can be merged into this one while both are activeGuild — Ryn Expires in 6 days
Split out on 2 Jul 2026 · 5 instances · its own key ····3B1E · 2 machines signed in
merge_licence
Open
Merging brings those instances into this key and retires the separate one. Both must be active, and it can be split out again afterwards.
Machines that have signed in with this key
4 machines| Machine | Hardware id | First seen | Last seen | State |
|---|---|---|---|---|
| DESKTOP-RIG | 4F2C…D0E3 | 4 Mar 2026 | 2 seconds ago | Live |
| LOFT-B450 | 91AE…227F | 19 Apr 2026 | 1 minute ago | Live |
| LAPTOP-XPS | C70D…4516 | 2 Jun 2026 | 9 days ago | Idle |
| OLD-TOWER | 2B55…C8D3 | 4 Mar 2026 | 4 months ago | Idle |
| Machine 1 | 4F2C…D0E3 | Live | ||
| No machine has signed in with this key yet — the first sign-in lists one by itself. | ||||
Every machine that signs in with this key is listed here with when it was first and last seen. Nothing is locked to a machine and there is no count to run out of: to use a new PC, put the key in the app there and sign in. If there is a machine here you do not recognise, re-issue the key above — every running instance is cut off until it has the new one.
Things only a person can do
Revoke this licence. The key stops working immediately and every instance using it is disconnected; remaining time is not refunded or transferred. Because it cannot be undone by you, it is a request to staff, not a button.
staff onlyRefunds, credit, and extending your time are decided by a person — never by the assistant and never by this page. She can put the request in front of staff with the evidence attached.
staff onlyAll Knowing
Main is active: two FollowBot plans pooled to 10 instances, 4 running right now, 4 machines have signed in with its key. Both plans expire together on 14 September 2026 at 21:04 UTC — 24 days from now. Nothing renews on its own; renewing either line adds time to the end of its term.
Read on your account:
licence Main → 2 grants, both active, both expires 2026-09-14; 4 sessions live; 4 machines signed in; authState ok.Everything she would say here is on the page above: the state chip, the instances in use, the expiry and the machines that have signed in are read from your account the moment the page opens. Nothing renews on its own; renewing adds time to the end of the current term.
All Knowing
I can split the June plan out of Main onto a brand-new licence with its own key. That leaves Main with 5 instances instead of 10, and nothing running is interrupted.
Read:
licence Main → 2 grants, both active; 4 sessions live. A split needs spare instances on the source — you have 6 free, so this is safe right now.I can move that plan onto a brand-new licence with its own key. This licence keeps its other plans; nothing running is interrupted. Give the new licence a name first.
Proposed action
split_grantoffer expires in 4:41Move the 11 June plan onto a new licence with its own key.
Move this plan onto a new licence with its own key.
- Main becomes
- 5 instances · 4 in use · expiry unchanged
- New licence
- 5 instances · 0 in use · expires 14 Sep
- Running now
- Nothing is interrupted or restarted
- Reversible
- Yes — merge it back while both are active
- Cost
- $0.00 — splitting is not a purchase
- This licence
- keeps its other plans · expiry unchanged
- New licence
- this plan · its own key, shown on the page
- Running now
- Nothing is interrupted or restarted
- Reversible
- Yes — merge it back while both are active
- Cost
- $0.00 — splitting is not a purchase
1–40 letters, numbers, spaces, dots, dashes. You can rename it later.
Only this click commits it. She proposed the action; the server checks independently that this licence is yours, and the result is written to your account history where you can undo it.
All Knowing
Merging Guild — Ryn back brings its 5 instances into Main (10 → 15) and retires Ryn’s key. His two running instances will stop at their next heartbeat — tell him first. Reversible: you can split it out again afterwards.
Read:
licence Guild — Ryn → 1 grant active, expires 2026-08-27; 2 sessions live; 2 machines signed in.Merging brings every plan on that licence into this one, pooling the instances, and retires its key. Anything running on it stops at its next heartbeat — warn whoever uses it first. Reversible: you can split a plan out again afterwards.
Proposed action
merge_licenceoffer expires in 4:58- Main becomes
- 15 instances · expiry per plan
- Guild — Ryn
- retired · key stops working
- Running now
- 2 instances will stop
- Reversible
- Yes — split the plan out again
- This licence
- gains every plan from the other · instances pooled
- The other
- retired · its key stops working
- Running now
- Its instances will stop
- Reversible
- Yes — split a plan out again
Only this click commits it. The server checks both licences are yours before anything changes.
All Knowing
A name is only a name — the key, the plans and the machines stay exactly as they are. Type the new one and confirm.
Proposed action
relabel_licence1–40 letters, numbers, spaces, dots, dashes.
- Reversible
- Yes — rename it again
Only this click commits it.
All Knowing
Before you do: 4 instances are running on Main right now and every one of them will be refused on its next heartbeat until it has the new key saved. If you are at your PC that is two minutes of work; if Ryn’s machines are on this key, they stop until he updates them. Plans and expiry are untouched.
If the goal is to cut Ryn off specifically, he is on his own licence (Guild — Ryn) — re-issuing Main does not affect him.
Read:
licence Main → 4 sessions live on DESKTOP-RIG ×3, LOFT-B450 ×1; Ryn’s machines signed in with Guild — Ryn, not Main.Before you do: every instance running on this licence right now will be refused on its next heartbeat until it has the new key saved. The count is on the page above. Plans and expiry are untouched, and the new key is shown on the page once — never in this conversation.
Proposed action
reissue_licence_keyoffer expires in 4:30- Affects
- Main · 4 running instances will stopThis licence · running instances will stop
- After
- New key shown on this page · old key dead
- Reversible
- Staff can restore the previous key
- Limit
- 1 per licence per day
Only this click commits it. The new key is shown on the page, never in this conversation.
All Knowing
Then someone else has this key. Of the four, OLD-TOWER is the one to look at first — first seen in March, last seen four months ago, nothing running on it. DESKTOP-RIG and LOFT-B450 are running right now and LAPTOP-XPS was seen nine days ago.
Then someone else has this key. The Last seen column above says whether the machine is still being used; a machine seen in the last few minutes is running instances right now.
The fix is the Re-issue this key button in the Your licence key section: the old key stops working the moment the new one is issued, every running instance on this licence is cut off until it has the new key saved — yours included, so have the new key ready for your own PCs — and the plans and expiry are untouched.
The entry stays in the list afterwards; it is a record of a sign-in, not something that gives the machine access. Staff can remove it if you want it gone.
Read:
4 machines signed in · OLD-TOWER lastSeen 2026-04-19 · 0 live sessions on it · 2 machines with live sessions.All Knowing
Revoking cannot be undone by you, so it is not something I can do — it goes to a person. Before that: if the aim is to stop a shared key, re-issuing it does that and keeps your plans; if the aim is to stop paying, simply do not renew and the licence lapses on 14 September with everything preserved.
Goes to a human
revoke_licence · staff onlyAsk staff to revoke Main, with the licence state and your last four payments attached. You get the answer in this same place.
Ask staff to revoke this licence, with its state and your recent payments attached. You get the answer in this same place.
All Knowing
I am not allowed to touch time, money or what you are entitled to — that is a person’s decision, deliberately. I can put it in front of one right now with everything attached.
Goes to a human
propose_refund · staff decidesRequest a review of Main’s billing, with your payment history and both plans’ dates attached.
Request a review of this licence’s billing, with your payment history and its plans’ dates attached.
All Knowing
(Design mock — in the live portal she answers here from your account and the support knowledge base, and proposes any action as a button you click.)