Guide
Choose Your Integration
Pick the SoundSync integration path that matches your framework, amount of custom code, and customer journey.
SoundSync
Integration chooser
Each option has different responsibilities.
| Path | Use when | SoundSync handles | Developer handles |
|---|---|---|---|
| Generated HISE Package | You build with HISE and want the maintained SoundSync package/runtime. | Generated config, credential embedding, Test Connection payloads, activation runtime, validation, deactivation, branding, package Store/My Products where included. | Product setup, package placement, runtime include, release QA, support copy, product UI and audio behavior. |
| Generated JUCE Package | You build with JUCE and want the maintained package over the shared native licensing core. | Module wrapper, generated config, CMake project, client API, public state, ready-made components, examples, docs, and tests. | Product-specific UI placement, audio behavior, release QA, host/format coverage, and package regeneration when product or brand state changes. |
| Custom JUCE/C++ | You need full control or want to call the HTTP licensing API from your own native client instead of the JUCE package. | Server-side licensing API and product credential checks. | Activation UI, HTTP requests, response-state handling, secure persistence, startup validation, offline grace, deactivation, logging redaction, audio/access decisions. |
| Other Native C++ Client | You are not using JUCE networking but can make HTTPS JSON calls. | Same API contract as JUCE/custom HTTP. | Your networking, JSON parsing, secure storage, threading, and lifecycle handling. |
| Server-to-Server | A trusted platform needs SoundSync data or fulfillment behavior. | Only documented for verified credential classes. | Do not reuse plugin credentials as developer/server credentials unless the endpoint explicitly accepts them. |
| Embedded Storefront or Customer Library | You want web commerce or customer-owned product/library surfaces. | Storefront/embed/library APIs where documented. | Keep this separate from native plugin licensing and do not mix frame/library tokens with plugin credentials. |
JUCE package status
The JUCE package is complete and current in the repository package path. Use Custom JUCE/C++ only when a product needs a bespoke transport, UI, storage, or build architecture outside the maintained package.
SoundSync
Quickstarts
Start with the guide matching your choice.
Generated HISE Package
Use package setup, Test Connection, activation modes, validation, grace, and release checklist.
Custom JUCE/C++
Use the HTTP client examples and licensing quickstarts.
Raw HTTP and cURL
Use copyable HTTP requests for endpoint testing and server exploration.
Server-to-Server
Use only verified server credential surfaces.