Rignos has two halves. The desktop app goes on the laptop that visits the truck; the workspace is a website, so there is nothing to install for that.
Issuing the code creates a machine row in your workspace; activating binds that laptop to it. You can rename the machine, attach the customer’s email and engine serial to it, see when it last uploaded, or revoke it — all from Machines & tokens.
Codes expire after 15 days by default (set 0 days when issuing for a shop laptop that should never expire). An expired code is refused with a clear message in the app, and recordings already queued on that laptop still upload for a week after expiry so nothing recorded in the field is lost. Your plan caps how many machines can be active at once; the cap is enforced at activation, not just in the web form.
Issue a new code and activate on the same computer name: Rignos re-issues into the existing machine row instead of creating a second one, and the old code dies at that moment. Without this, every rebuild would burn one of your machine slots until somebody noticed. The app also has a Revoke this machine button for when you want to hand a laptop on.