Yes. If you purchased a perpetual, single‑device license, you must first deactivate it from the old machine (via Settings → License → Deactivate). The key can then be re‑activated on the new device. For subscription or multi‑seat licenses, you can bind additional devices up to the allowed seat count without deactivating.
Absolutely. The Licensing API supports bulk key generation and CSV export. You can also integrate with your provisioning system via the POST /v1/bulk-keys endpoint. 10. TL;DR The System Mechanic License Key feature delivers a secure, frictionless, and flexible activation experience. It protects intellectual property with industry‑grade cryptography, supports offline use, enables multiple business models (perpetual, subscription, trial, feature bundles), and offers powerful admin tools for revocation, analytics, and bulk provisioning. The result is a win‑win: users enjoy instant, hassle‑free access while System Mechanic safeguards revenue and gains actionable insights. Prepared for product managers, engineering leads, and marketing teams to communicate the value and mechanics of the System Mechanic License Key.
All UI text is fully localizable; the activation flow adapts to right‑to‑left languages without breaking the layout. | Integration | API Endpoint | Data Flow | |-------------|--------------|-----------| | License Portal | POST /v1/licenses | Create, edit, revoke licenses. | | Activation Service | POST /v1/activate | Validate key, return JWT. | | Renewal Service | POST /v1/renew | Exchange expiring token for fresh token. | | Analytics | GET /v1/metrics | Pull activation counts, churn, geography. | | Third‑Party Resellers | POST /v1/bulk-keys | Bulk download of pre‑generated keys. | | Support Tool | GET /v1/license/key | Verify status for support agents. |
No. The activation token (JWT) is encrypted with OS‑level secure storage. The raw license key is never persisted after activation; only the signed token is kept.