Device licensing
Per-device access that manages itself.
Plans license a fixed number of devices. Binding happens automatically at first launch, expired activations free their slots on their own, and institutions manage seats instead of passwords on sticky notes.
How it works
Three steps, on a real console workflow.
01
First launch binds
A learner's first console launch registers the browser as a licensed device. There is nothing to configure.
02
Limits enforce fairly
Device limits follow the plan; hitting a limit says so clearly instead of failing mysteriously.
03
Expiry cleans up
When access expires, its device slots are released automatically. No support ticket needed.
How licensing behaves
| Event | System behavior | User experience |
|---|---|---|
| First launch | Device fingerprint bound | Invisible |
| Second device (1-device plan) | Blocked with reason | Clear message, not an error |
| Plan expiry | Bindings auto-released | Renew and relaunch |
| Upgrade | Trial superseded cleanly | No mixed access states |
In the classroom
How programs use it
- Lab machines and personal laptops coexist under seat-based institutional plans.
- No shared logins: progress records stay per-learner and gradable.
- Device resets are self-serve or admin-side. Nobody waits in a support queue.
Start today
Put your learners at the console today.
Free 45-minute trial. No installs. Runs in any browser.