Your account

Signed in as

—

Account

—

Sign-in methods

—

Connecting a provider adds another way into this account. It does not create a second one — that only happens if you use a provider while signed out and it has never been connected here.

Devices

Loading your devices…

You can release any of these from here, including a machine you no longer have. A device signed in on its own can only release itself — that is deliberate, so a stolen machine cannot cut off the others.

Release frees the slot and the machine can take it back by activating again. Revoke records a revocation so it cannot — use that for a machine you have lost. Revoking is not instant: it takes hold at the next activation, the next entitlement refresh, or the next run or serve session, and serve seats within about three minutes. A machine mid-render finishes that render.

Browser-free activation

For machines that cannot open a browser — a server you reach over SSH, a build agent, a fleet. You prepare an enrolment key here and the machine presents it instead of approving in a browser.

The command line in the build this site offers accepts these now. Create and manage keys here, then enrol a machine with veizik activate --key KEY --password-stdin (or --no-password for a key issued without one). Approving in a browser still works and is the default; the key is for machines that cannot open one.

A key enrols whatever machine presents it. Unlike approving at /activate, nothing proves the machine using it is the one you meant — so give each machine its own single-use key, keep a password on it, and revoke the key once the machine is enrolled. A revoked or expired key does not disturb machines already enrolled with it; release those under Devices.

—

CLI password

A second secret, separate from how you sign in here. A key on its own is one thing to lose; a key plus this is two.

—

Sign out