Keylight vs iLok — licensing a plugin without a dongle

You are about to charge money for a plugin, and you have found iLok and Keylight. Most comparisons at this point would tell you the incumbent is bloated and the new thing is better. That is not the honest read. iLok and Keylight are aimed at two different developers, and picking correctly is mostly a question of who your buyer is.

What iLok gets right

iLok has been the licensing layer of professional audio for a long time, and it earned that position.

It covers every format that matters — VST, VST3, Audio Units, AAX. Activation is not dongle-only: PACE lets you allow an iLok USB dongle, iLok Cloud, or the customer’s own machine, and you choose which of those your plugin accepts. Customers manage everything from iLok License Manager, an application many of them already have open.

That last part is the real advantage, and it is not a technical one. A working studio already owns a dongle for Pro Tools or for half the plugins on their system. When your plugin shows up as another license in a manager they already use, you inherit infrastructure instead of asking them to adopt yours. For some buyers, seeing iLok on your product page is itself the trust signal that closes the sale.

If your customers are professional studios, that inheritance is worth more than any integration convenience.

Where Keylight is different

The split is what you have to do, and what you ask your customer to do.

iLok integration means bringing your binary into PACE’s toolchain — wrapping and signing your plugin so their system can protect it. It is a build-pipeline change, and it is a real project.

Keylight is a header. You drop keylight_single.hpp into your JUCE project, hold a Licensing member in your processor, and gate features on the audio thread with a lock-free read:

void MyPluginAudioProcessor::processBlock(
    juce::AudioBuffer<float>& buffer,
    juce::MidiBuffer& midiMessages)
{
    // One lock-free atomic read — safe under real-time constraints.
    if (!licensing.hasFeature("pro"))
    {
        applyFreeFeatures(buffer);
        return;
    }

    applyProFeatures(buffer);
}

No wrapper, no signing step, no change to how you build.

The customer side differs just as much. With Keylight, someone buys from your site, gets a key in their inbox, and pastes it into your plugin. That is the whole flow — no account to create, no manager application to install, nothing between the purchase and the plugin working. With iLok, the license lands in an iLok account, which means your customer needs one.

Neither is wrong. One asks your customer to join an ecosystem. The other asks them to paste a key.

Offline works in both, by different means. iLok uses the dongle or a machine activation. Keylight signs an Ed25519 lease that your plugin verifies against a public key compiled into your build, so an isolated studio machine never hits the network to prove it is licensed. Your feature flags are signed into that lease too, so gating a pro tier offline costs nothing extra.

And the money is yours directly. A Stripe payment mints the license and emails the key — Keylight catches the webhook, you write nothing. You are not adding a storefront, you are connecting the one you already have.

When iLok is the better pick

Be honest about this, because getting it wrong is expensive.

Your buyers are professional studios. If the people buying your plugin already run an iLok dongle and expect to see your license appear beside the rest of their collection, that expectation is the product decision. Fighting it to save integration time is a bad trade.

A distributor or partner requires it. Some channels in pro audio assume iLok. If yours does, the conversation is over.

You want the deepest anti-piracy track record in the category. PACE has been doing this specific job, against this specific threat, for decades. Keylight raises the cost of casual copying and makes buying the easy path. It does not claim to out-engineer a dedicated anti-piracy company with that history.

Where Keylight fits

You are a solo builder or a small team. The plugin is built, it works, and the only thing between you and selling it is licensing. You do not have studios asking for iLok, you have a landing page and a Stripe account.

That is the case Keylight is built for. A header in your JUCE project, activation from your plugin editor, offline verification in any DAW host, device limits so one key does not end up on twenty machines, and a key that appears in the customer’s inbox the second they pay. You can also set the trial length from the dashboard and change it later without shipping a new build.

The difference in one line: iLok is licensing infrastructure you join. Keylight is licensing infrastructure you install.

If your buyers already live in the first one, go there. If you are trying to ship a paid plugin this month, the second one is a shorter road.

Plans start at $19/month, with a free tier. Test the whole checkout-to-plugin flow before you pay for anything.