@Christoph-Hart cool! I've scheduled some time with our JUCE freelancer to make it JUCE6 compatible, using the APIs available there for machine IDs. We'll also implement an option to pass your own function for fingerprinting, so it's easy to plug in whatever else you may create, if you don't patch JUCE itself. Is there anything else we can do in the same go to make it more HISE-friendly? Let me know!

Good idea, thanks!

Our JUCE module contains most of the stuff you need to handle licensing & delivery:

• License activations (more on this later)
• Time-limited trials
• Offline activations
• Subscription-ready (including our Rent-to-Own features)
• Update notifications on new releases
• Analytics back to Moonbase (optional, stuff like host/daw/etc meta)

Our licensing flow is a bit different than most, we want the smoothest process we can, and so what it does is just open a browser on your website, where our web SDKs take over the process and activate plugins on the website. Since customers are usually already logged in to your website, since they made a purchase, downloaded your plugin, or whatever else, we can immediately activate the plugin.
We have a video of this flow, including the default UI of the JUCE module in our BSA customer story: https://moonbase.sh/stories/blacksaltaudio/

Having customer authentication on your website is a really good way to also provide a fully personalized storefront experience, where we can showcase segmented pricing, enabling loyalty discounts and a bunch of other cool things.

The biggest hurdle to adopting our JUCE module in HISE projects is the fact that it depends on JUCE version 7. I'm not the original author, but I know there's probably two things that would need to change for a downgrade to JUCE version 5 (which I think HISE is still using?):

1. The device fingerprinting needs to change. We had issues with the older JUCE (< v7) fingerprinting in cases where we crossed ~100k devices, where we saw collisions and unstable fingerprints.
2. I believe we're also using some utilities from the newer URL/HTTP classes, but I'm not 100% certain of this.

Generally, it's not a super complex module, but it is very battle-tested, powering hundreds of thousands of plugin installs.

@d-healey said in SoundSync: Reseller, Security & Serial Management Platform:

@trillbilly said in SoundSync: Reseller, Security & Serial Management Platform:

Im working towards a complete audio plugin/product backbone that allows developers (new and old) to quickly and reliably manage the entire backend of the business (and some development tools).

Sounds similar to Moonbase

Thanks for the shout-out! I'm Tobias, the founder of Moonbase.
Won't hijack this thread, welcome any competition in this space - it needs more modern options!

I believe we have 3-4 HISE users already onboarding onto Moonbase, integrating the JUCE module, but I'm not sure about the current status. It will need some changes here and there, but nothing too major I hope. I tried reaching out to @Christoph-Hart a while ago after we met in Berlin, but didn't hear back. Maybe it's time to re-visit a collab here? :)

Interfacing with resellers better sounds like a really cool approach, and something we have on the roadmap too. It gets tricky fast to get a grasp on actual cashflow and revenue sources when you have sales scattered across several channels, including your own. Happy to share any experience we have doing software sales @trillbilly !

@d-healey said in Moonbase:

@tobbentm Is it compatible with GPL plugins?

Since our JUCE module is closed-source, no.
You'd have to dual-license it, with a separate version that has DRM in it.
Alternatively, you could integrate on your own, or use other libraries to integrate with.
Syl is currently working on a pure C++ (no JUCE dep) open-source thing here, but it's very early days: https://github.com/SLM-Audio/moonbasepp
We're getting more and more requests for a simple C++ library, so we may try to build an alternate open-source solution ourselves next year.