The account portal is where a customer creates an account, chooses a plan, pays securely, manages devices, and gets the key needed to run Bitfield.
Somebody reads the docs, pressesGet My Key, lands on account.bitfield.so, chooses the trial or plan, completes checkout, then opens the account page to activate their first device.1
The account portal owns identity, returning login, and recovery.
→
2
The checkout surface shows trial, plan, runtime/device range, and cadence.
→
3
The payment provider receives only an accepted checkout request from the account portal.
→
4
The account page is the place to manage account state, key access, and devices.
What happens where
Key delivery rule
Treat the key as account-owned access. The docs should never tell a customer to invent a key, paste a random token into local state, or edit activation files by hand.Local activation state can exist on the device after authorization, but the customer-facing control point is still the account portal.Common failures
Verify
The flow is clear when a new customer can answer:- Where do I create the account?
- Where do I pick the trial or plan?
- Where do I pay?
- Where do I get the key?
- Where do I activate or replace a device?