Skip to content
SoundSyncAudio software platform

Secure Licensing for HISE, JUCE, and Custom Audio Software

Licensing for Audio Software

SoundSync provides product-scoped credentials, serial activation, customer-login activation, email verification, startup validation, offline grace, device limits, deactivation, subscription enforcement, and customer-library access.

Product access, from ownership to device use

SoundSync connects product credentials, customer ownership, serial claims, activation limits, validation, and deactivation. Activation registers authorized device use; validation refreshes it. Test Connection checks credentials, not the customer's right to use the product.

SoundSync

Choose your integration

PackageFit
HISEScriptFast script-level integration without rebuilding HISE
HISE C++Native authority requiring HISE source and exported-plugin builds
JUCE 0.7.3Processor-owned runtime and editor UI for Windows/Apple source packages
Custom HTTPYour own activation UI and runtime using product-scoped endpoints

State that survives real customer workflows

Device limits, ownership proof, recurring entitlements, and revocation must remain distinct from a temporary network failure. Offline rules depend on the integration, not one universal checkbox.

JUCE 0.7.3 supports signed offline access for the grace period selected in product Access settings, through 90 days. A prior successful activation or validation and the matching package verification keys are required. Startup uses a verified unexpired grant or online authorization. Zero, disabled, missing or expired grace requires online authorization; confirmed denial or deactivation locks access. Regenerate and rebuild older plugins to use this release.

Credentials and enforcement shipped in client software can be extracted or modified. Native enforcement raises the integration barrier; it is not a piracy-proof guarantee. Keep developer account tokens and partner secrets out of distributed plugins.

SoundSync

Implementation guides

Choose an integration

Package and API responsibilities.

Licensing API

Activation, validation, deactivation, and errors.

SoundSync

HISE customers can activate from inside the plugin

The HISE login screen shows the customer-facing activation surface with product identity, support context, account login, and serial activation paths.

SoundSync

JUCE serial validation is package-ready

The JUCE serial validation screen shows the native package path for serial entry, customer identity, validation, and activation state.

SoundSync

Owned products stay visible after activation

The JUCE My Products screen shows the logged-in customer state with owned product access, serial state, and device actions in the plugin UI.

Signed offline access follows your product settings

Choose the grace period in product creation > Access. Successful activation or validation returns a signed grant bound to the product, activation and device. The period starts at that successful online check, not the first failed connection. The package bundles only public verification keys. Reopening the plugin or losing connectivity does not extend its signed expiry. An earlier entitlement or subscription access deadline shortens the grant.

The processor enforces access with the editor closed, including float, double and bypass processing. Confirmed revoked, refunded or deactivated access must lock the product rather than renew grace. A disconnected device learns about later server changes on reconnect or when its existing grant expires.

Regenerate the Windows or Apple source package, check manifest offlineAccess, rebuild and test your product. Existing compiled plugins are not upgraded automatically. Windows VST3 and Ableton Live 10.1.43 fixture tests cover offline playback, expiry, saved-project restart and WAV export; Apple Keychain/AU and your own product binaries require target-host testing.

offlineAccess: true describes bundled verification capability, not an active customer license or an enabled product policy. An older unsigned cache needs successful online activation or validation before offline use. After rebuilding, distribute the updated binary; replacing a ZIP in the dashboard cannot update customer installations.

Changing Access settings applies on the next successful online validation without a rebuild when the installed package already has the required public keys. A future signer change must be coordinated with replacement public keys in rebuilt clients; never add private signing material to a plugin.

SoundSync

Update an existing JUCE product

Regenerate and update JUCE

Package readiness, saved activations, offline tests, and customer distribution.