Custom Domains and SSL for SoundSync Storefronts
Use your main domain or a storefront subdomain.
Connect root and apex domains or storefront subdomains with guided DNS records, provider detection, verification checks, SoundSync-provided SSL certificates, and storefront publishing. Developers only need the domain and DNS access; SoundSync handles the rest of the hosted-domain setup.
SoundSync
Domain setup from Brand Manager
Brand Manager keeps domain status, storefront preview, colors, logo, support identity, and email-domain readiness in one dashboard surface.
SoundSync
Domain choices
Developers are no longer limited to store. or shop. subdomains.
| Domain option | Use it when | DNS record |
|---|---|---|
| Main/root domain | You want the SoundSync storefront to live at the primary brand domain, such as example.com. | Use the guided apex/root record provided by SoundSync. |
| Storefront subdomain | You want to keep an existing website and put commerce at store.example.com, shop.example.com, or another chosen subdomain. | Use the guided CNAME record provided by SoundSync. |
| Email sending domain | You want marketing and system email to use branded sender/authentication records. | Use SPF, DKIM, DMARC, verification, and tracking records from the email-domain workflow. |
SoundSync
Custom-domain setup
Developers only need the domain and DNS access. SoundSync handles the hosted storefront connection, verification workflow, and SSL certificate provisioning.
-
Enter domain
Choose a root domain or subdomain from Brand Manager or the domain setup flow.
-
Detect provider
SoundSync detects common DNS providers from nameservers where possible and falls back to generic DNS instructions.
-
Copy records
Copy the exact A, CNAME, TXT, SPF, DKIM, DMARC, verification, and tracking records that apply to the selected flow.
-
Verify steps
Use one-record-at-a-time checks, full workflow checks, status messages, and troubleshooting until records resolve.
-
SSL certificate
SoundSync provides SSL certificates for connected domains after the domain is verified and routed correctly.
-
Publish with brand
Hosted storefront, Website Builder, checkout, customer accounts, package links, and customer support surfaces use the approved brand/domain values.
Propagation and package boundary
DNS propagation timing depends on the developer DNS provider. Dynamic storefront and account surfaces can read updated Brand Manager values, while generated HISE/JUCE packages should be regenerated when embedded logos, colors, support URLs, domains, or static config values change.
Set brand once, then reuse it everywhere.
Start with Brand Manager docs, then connect the domain and regenerate package artifacts when the brand is ready.
SoundSync
Product proof
Screenshots and diagrams are placed near the workflows they explain, so visitors see the actual SoundSync surfaces instead of abstract feature claims.
Questions developers ask
Is SoundSync only for plugins?
No. SoundSync supports plugins, instruments, sample libraries, digital downloads, subscriptions, and custom audio tools.
Can I use my own site?
Yes. You can use hosted storefronts, embedded storefronts, standalone embeds, and custom domains depending on the surface you choose.
Does marketplace attribution add another fee?
No. SoundSync uses one 10% fee on SoundSync-processed sales, including marketplace-attributed sales.
Use your main domain or a storefront subdomain. belongs in one connected launch system.
Move from setup to customer access, growth, trust, and operations without rebuilding the business around disconnected services.