Audio is the one consumer-adjacent industry where hardware licensing is completely normal — iLok made sure of that. It also made sure every musician has an opinion about it. If you are choosing protection for a plugin line today, the question is not whether a dongle can work in a studio; it is how to get the protection without the parts your customers resent.
What the studio actually wants
Studio machines are offline by choice: tuned, frozen mid-production, and not interested in reaching an activation server at the downbeat of a session. Hardware licensing fits that world — account-based licensing fights it. With KeyNub there is no account for your customer to create, no license-manager application to install and keep updated, and no activation count to argue about in support tickets. Your plugin ships with one library; the customer plugs in one standard HID device; and the license is wherever the key is — the studio today, the laptop on tour tomorrow.
Keep USB out of the audio thread
The engineering rule that matters more in audio than anywhere else: the dongle is instantiation-time hardware, not render-time hardware. Verify the key once when the host loads your plugin, decrypt what you need, cache the result — and by the time the first audio callback fires, the dongle’s job is over. Nothing in the render path should ever perform USB round-trips, allocate, or take a lock that a license check holds. Every KeyNub sample follows that shape, and the C++ binding keeps the check-once pattern to a handful of lines.
Protection that survives a cracked binary
Plugins get cracked by patching the license check, and obfuscation only raises the hourly rate. The durable answer is to make the check not worth patching: ship your preset banks, impulse responses, wavetables or filter coefficients encrypted, and decrypt them through the dongle when the plugin loads. A crack that removes the check removes the content — the copy loads, and sounds like nothing.
One dongle, your whole catalogue
Each product is a record on the key, so a customer’s entire collection travels on one dongle. A bundle sale or an upsell is your shop writing one more record with vendor authorisation — no new installer, no re-download, and the upgrade works even if the studio machine has never seen the internet.
C++, mostly — and Rust, increasingly
Plugin code means C++ (JUCE or otherwise), with Rust gaining ground in DSP land — both bindings are published with runnable samples. Installer and shop-side tooling tends to be Python, where the binding comes with a command-line tool you can script directly.
All industries · All supported languages · Buy a KeyNub · Ask us something
