Skip to main content

Your key is how a device or runtime identity can trigger Bitfield for your account. The account portal owns the customer path: account, checkout, email, key access, runtime identities, recovery, and plan management.

You want to try Bitfield on the device in front of you. You need account access first, then device activation, then Runtime Kit can run against that account path.
1

Use the account portal and confirm the email you will keep.

2

Start a trial or plan with the runtime/device range you need.

3

Use the key path to connect this device to your account.

The account portal should show your account, plan or trial state, available runtime/device range, and the current way to activate this runtime identity.

1. Open the account portal

Go to account.bitfield.so.Use an email you control. Account recovery, checkout receipts, key access, and device messages depend on that email.

2. Choose the trial or plan

  1. Choose the plan or trial that fits the runtime/device range you need.
  2. Confirm the checkout terms and billing authorization.
  3. Confirm your email when it arrives.
  4. Open the account portal and activate the first device.
The runtime/device count is not the number of users in your imagination. It is the number of runtime identities that trigger Bitfield in the billing window.

3. Activate the first device

Use the account portal’s current activation path for the device you are using.If you are testing alone, this is usually your laptop first. If you are testing with a phone and laptop, each triggered runtime identity can matter. If you give access to a friend or teammate, treat it like real account access.

4. Keep the account path recoverable

The account portal is the customer control room. It is where you see your plan, billing cadence, keys, runtime/device range, replacement history, and cancellation options when they are available.Keep access to the email you used at checkout. License-key and account-recovery messages go there. If a device is lost or replaced, use the portal to revoke that device and free the spot for another one.

Common failures

SymptomLikely causeFix
You cannot find the key pathEmail or checkout step is incompleteConfirm email, then reopen the account portal
A new device will not activateActive-device count is fullRevoke or replace an old device in the portal
You used the wrong emailAccount ownership is tied to checkout/recovery emailUse the email you can keep and recover
You are unsure what counts as a deviceActive device means a triggered runtime identity in the billing windowRead Active devices
Billing or cancellation is unclearPlan management belongs in the account lifecycleRead Trials and billing and Plan changes and cancellation

Next

Last modified on May 11, 2026