SoundSyncDeveloper Platform

Licensing

Licensing that reaches the installed plugin.

SoundSync licensing is designed around serial validation, subscription access, activation, deactivation, restore activation, suspend/revoke states, machine identity, offline grace, HISE packages, and custom API/JUCE workflows.

OnlineRequired for initial activation
7 daysDefault offline grace
ImmediateLock on confirmed invalid state

Plugin flow

Plugin -> SoundSync API -> license check -> cache/token -> unlock.

Initial activation must be online. Offline grace applies only after a valid activation/cache exists, and only for network failure or temporary unavailability. A confirmed invalid backend response should lock the plugin immediately.

1 Plugin
2 SoundSync API
3 License / customer / product check
4 Activation cache / token
5 Plugin unlocks

Serial validation

Validate a serial against customer, product, machine, and entitlement state before unlocking.

Subscription access

For subscription products, validate active, trialing, past-due, canceled, refunded, and expired states before allowing recurring access.

Activation

Bind a valid serial/customer/product to a machine identity and store a validation token locally.

Deactivation

Release a machine and clear local license state so customers can move devices.

Restore activation

Use claim and claim-status flows when customer identity or verification is required.

Suspend/revoke

Respect suspended, revoked, deactivated, expired, not-found, and product-mismatch states immediately.

Offline grace

Default offline grace is 7 days unless configured otherwise, and only after valid activation/cache.

Reseller/manual serials

External redemptions, imported serials, manual grants, and promo/offline serials can feed the same access model.

Credential rotation/revocation

Rotate or revoke product/plugin credentials when a secret is exposed or an integration changes.

Refresh/check status

Use validate as the refresh/status check and respect backend polling guidance.

Lock states

Confirmed invalid states should not fall back to grace.

If the backend returns invalid, revoked, suspended, deactivated, expired, not-found, or product-mismatch, the plugin should lock immediately. Offline grace is not a way around confirmed license failure.

  • invalid
  • revoked
  • suspended
  • deactivated
  • expired
  • not-found
  • product-mismatch
Validate before unlock
POST /api/license/v1/validate
Authorization: Bearer PLUGIN_SECRET

{
  "license_key": "CUSTOMER_SERIAL",
  "machine_id": "DEVICE_ID",
  "validation_token": "TOKEN_FROM_ACTIVATION"
}

License support context

Resolve access questions without guessing at license state.

Customer, serial, activation, subscription, and download-access context should point support toward the right next step without revoking, suspending, restoring, refunding, or unlocking licenses outside controlled workflows.

  • Activation context
  • Serial state
  • Subscription access
  • Controlled changes

Launch Center ready

Wire licensing before launch.

Create product credentials, test activation/validation/deactivation, and confirm your plugin locks correctly on failed validation states.

Launch Your First Product Read the Docs