使用中的实例
到期
登录过的机器
这个密钥上的套餐
你的许可证 Main
主导航
FollowBot · 2 个套餐已合并 · 创建于 2026年3月4日 · 从未吊销
使用中的实例
4 / 10
到期 24 天 2026年9月14日 · 两个套餐
登录过的机器 4 不锁定任何一台
这个密钥上的套餐 2 每个 5 个实例，合并为 10 个
你的许可证密钥
应用用什么登录
•••••-•••••-•••••-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.
结尾是 —用下面的“显示密钥”查看
点“显示密钥”随时可以看到完整密钥。如果密钥给过别人或泄露了，请在下面重新签发：新密钥会替换它，旧的立即失效。
新密钥已签发——现在就复制。
需要时，“显示密钥”随时能把它再显示出来。每个正在运行的实例都必须换成这个密钥——旧密钥现在就失效了。
4KQF9-M2TXW-7DH3N-C7Q2A← 你的许可证密钥
← 留空
☑ Remember passwordSign in
这就是应用平常的登录框。每台机器输入一次密钥，Password 留空，并勾选 Remember。
把密钥分享给了别人，想收回来？重新签发会立即生成新密钥，旧密钥随即失效。现在运行着的 4 个实例会被断开，直到每个都保存了新密钥为止——你的套餐和到期时间都不受影响。
reissue_licence_key这个许可证上的套餐
已合并 · 10 个实例你买的每个套餐都是单独的一行，有自己的日期。默认合并成一个总额度。可以单独续费某一行，也可以把它拆分到单独的密钥上。
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 个实例
购买于 · 通过 PayPal 付款 · 单号 · 到期
这是这里最后一个有效套餐。你的用户名会让 FollowApp 登录到这个许可证；把这个套餐拆分出去后，用户名将找不到任何套餐。届时请改用新许可证的密钥来运行它。
split_grant 续费
这个许可证上还没有套餐。购买、试用，或从别的许可证拆分出来的套餐都会显示在这里。
拆分不是购买，也不会中断任何东西。套餐保留它的到期时间和收据；变的只是它归哪个密钥。
从这个许可证拆分出去的你的其他许可证
套餐来自 Main 的许可证只要双方都有效，任何一个都可以合并进这个许可证Guild — Ryn Expires in 6 days
Split out on 2 Jul 2026 · 5 instances · its own key ····3B1E · 2 machines signed in
merge_licence
Open
合并会把那些实例并入这个密钥，并停用单独的那个。双方都必须有效，合并后也可以再拆分出去。
用这个密钥登录过的机器
4 台机器| 机器 | 硬件 ID | 首次在线 | 最后在线 | 状态 |
|---|---|---|---|---|
| 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 |
| 机器 1 | 4F2C…D0E3 | 在线 | ||
| 还没有机器用这个密钥登录过——第一次登录就会自动列出一台。 | ||||
用这个密钥登录过的每台机器都列在这里，附带首次和最后在线的时间。不锁定任何机器，也没有会用完的名额：要用新电脑，在那里把密钥填进应用并登录就行。如果这里有一台你不认识的机器，就在上面重新签发密钥——每个正在运行的实例都会被断开，直到拿到新密钥为止。
只有真人能做的事
吊销这个许可证。密钥立即失效，所有用它的实例都会断开；剩余时间不退款，也不转移。因为你自己无法撤销，所以这是向工作人员提出的请求，而不是一个按钮。
仅限工作人员退款、补偿和延长时间都由人来决定——从来不由助手决定，也不由这个页面决定。她可以把请求连同证据一起交给工作人员。
仅限工作人员本页是英文页面的译文；价格、退款和条款以英文页面为准。
All 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.)