Concept page
Licenses, Activations, and Devices
Distinguish ownership proof, licensing identity, and active machine use.
Serial and login paths prove different things
A serial flow may require email verification or proof of the existing owner. Customer login establishes account identity before entitlement/activation checks. Product credentials authenticate the integration itself, not the person requesting access.
Activation records authorized device use
The product's machine policy and limits govern whether another device can activate. Validation checks current access; deactivation releases the selected activation. Neither operation is automatically a purchase refund.
Use the package's stable device identity and supported reset/deactivation controls. Inventing a new machine ID for every launch can consume device allowance and make support harder.
Access policy is package-specific
JUCE 0.7.0 requires online renewal at startup. Valid saved credentials are reused without repeated sign-in, but offline audio access is unavailable in this release. HISEScript offline grace is a different package policy.
HISEScript grace starts from prior valid access. A network failure, expired subscription, revoked entitlement, and a customer-identity mismatch must remain distinguishable.