Account and licensing

Licenses and your account

A bound key follows your account; an unbound one stays on the machines you install it on.

On this page

Binding a license to your account

A license key and an Alithon account used to be two separate things. The key knew machine ids; the account knew your devices, orders and cloud traffic. Nothing connected them, so every new machine meant finding the delivery email again.

Binding connects them. Once a key belongs to your account, signing in to Serial Port Utility activates whatever computer you are on, and signing out releases it again. There is nothing to copy and nothing to type.

  • At checkout: tick Bind the license to my Alithon account. It is on by default for Personal keys and off for Enterprise ones. The key is recorded against the email you enter on the order form — not necessarily the account you are signed in to, because that is where the key is delivered.
  • If you have no account yet: the key waits for one. Register with that same address and it becomes yours automatically.
  • If you already have a key: bind it from Dashboard > Licenses, or accept the prompt Serial Port Utility shows the first time you sign in on a machine that already has one installed.
The desktop License Management dialog: a table of product, version, status, license key, type, activation and expiry dates, CID and an Account row reading Not bound, beside an Input License field, a My licenses button, a ticked Also bind to my account box explaining that a bound license activates every computer you sign in on and can be bound to one account only, and Activate, Offline Activate and Remove License buttons
Help > Licence Management on the desktop. The Account row says whether this key has settled on an account; the tick binds it as it activates.
Dashboard > Licenses: a My licenses panel listing one personal 1-year key marked Active with its expiry and bind date, the two computers it is live on each with a Remove button, and below it a Bind a license key panel with a field for a key from the delivery email
Dashboard > Licenses: the key, the machines it is live on, and the field that binds a key you already own.

A key binds to one account, once

A binding cannot be moved to a second account afterwards. That is deliberate: if a key could drift between accounts, "sign out and lose your activation" would become a way to take somebody's license. Every place that offers binding says so first and asks you to confirm.

If a key ended up on the wrong account — a refund, an address typed wrong at checkout, an engineer who has left — contact support with the order number and the key, and we can release it.

How many computers

A bound key has no device limit. It is live only where its owner is signed in, which is a better control than counting machines: use it on your desktop, your laptop and the bench PC, and sign out where you are finished.

An unbound key runs on up to three machines at once. This replaced the old "one activation plus three transfers" rule, which was spent forever — reinstall Windows four times and the license was finished. A concurrency limit gives the slot straight back: deactivate a machine from Dashboard > Licenses and the next one can take its place.

Enterprise keys are different again: they carry a seat count from the order, and that count is what limits them whether they are bound or not.

What signing out does

Signing out of Serial Port Utility on a machine releases a bound license there: the activation is removed locally and the machine is taken off the license. Signing back in puts it straight back.

An unbound key is untouched by signing out — it stays installed on that computer exactly as before.

A session that simply expires is not the same as signing out. If the app cannot renew your session, the license stays active and it asks you to sign in again.

Was this document helpful?