One key, one PC — multi-PC is not supported

Nimbus keys are bound to a single Windows PC fingerprint at a time. You cannot have one key authenticated on two PCs simultaneously — the loader rejects the second sign-in with HWID mismatch and refuses to inject. This is intentional, technical, and not negotiable: pricing assumes one paying customer per key, and the HWID bind is what enforces that.

What works on one key:

• One PC at a time, any PC. Move the key between as many machines as you want using the HWID reset flow (change-bound-pc) — subject to the 24-hour cooldown.
• Multiple keys on one account. You can buy a Day + a Week + a Lifetime and have all three listed in your dashboard. Each one binds independently to whichever HWID you sign in from first.
• Reinstalling Windows on the same PC. A clean Windows install changes the HWID fingerprint enough to look like a different PC; one reset and you're back.

What does NOT work on one key:

• Desktop + laptop simultaneously. You can move the key back and forth using HWID reset, but only one authenticates at a time.
• Living-room PC + bedroom PC. Same answer — alternate via reset, but not concurrent.
• Sharing the key with a friend, sibling, partner, or guildmate. Every share attempt locks both of you out on alternating sessions.
• A virtual machine (VM) running on the same host as your bare-metal install. The VM has a different HWID than the host; binding to one breaks the other.

If you genuinely need two-machine concurrent use (desktop + travel laptop, two-PC streaming setup, etc.), you have two options:

1. Buy a second key. Day pass is $5 if it's only occasional travel; Month is $30 if both PCs see regular use. The second key is a fresh purchase from /products and binds independently to the second PC's HWID.

2. Lifetime add-on: concurrent slot. Lifetime customers can request a second concurrent slot for a one-time $40 add-on. DM #support on Discord after you have Lifetime — this isn't advertised on the pricing page but it exists. The add-on grants exactly one extra concurrent HWID binding; not unlimited.

Why we don't allow multi-PC by default. Without HWID binding, a single $5 Day pass would be shared across a Discord server of 200 within an hour, and we'd be out of business by Friday. Even a 2-PC default would get gamed — "I share with my brother" stretches to "I share with my whole friend group" instantly. The 1-PC default with self-serve switching is the policy that holds the math together at our price point.

Why we don't auto-detect "same person, two PCs". Any signal we could use to claim "these two HWIDs are the same person" (IP address, browser fingerprint, account behavior) is trivially spoofable. We'd be writing the multi-PC bypass for free. The honest answer is one HWID at a time; the workaround is the reset flow, which we keep fast (under 5 seconds) and forgiving (24h cooldown with manual waivers for emergencies).