License Management for Vendors
Lyrinox Market's licensing tools support product licenses, activation limits, expiration, subscriptions and license-status management. Contributors can manage no-charge products without vendor approval. Charging requires an approved vendor application and explicit acceptance of the current publishing agreement, except for official first-party Lyrinox profiles; separate API-access checks still apply.
Describe what the customer receives
A product should explain its license scope, supported versions, activation limits, updates and support. Those customer-facing terms need to match the product and its publishing arrangement. Application approval alone does not grant distribution rights or settle licensing terms.
Activations and account access
The existing license API supports domain activation and optional IP locking. Account-based authorization provides a separate approval flow tied to a customer's entitlement. Do not describe these mechanisms as a general device-management system without confirming the integration's behavior.
Issuance and changes
Use manual issuance only where you have authority to grant access, and retain a clear reason for changes. Revocation and suspension affect customer access and must follow the applicable terms; a change in vendor onboarding is not itself a reason to revoke a customer's purchase.
Subscription license status follows the existing payment integration. A publishing agreement does not replace the application's payment and entitlement checks.
How Software Licensing Works for Developers provides general licensing context. For a new product, begin with publishing with Lyrinox.