Plugin Authentication (Online vs Serial Key)

Audio Plugins
1

Hey there, I’ve been researching methods for plugin authentication (anything but iLok really) and I’ve narrowed down my decision to two main options.

Online authentication

  • Send request to an auth server i control
  • return back some form of verification
  • plugin is unlocked, save to some file and kaboom

or

Serial Key / Offline authentication

  • Generate a database of keys
  • Give user key on purchace (manage using itch.io for my case)
  • user uses the serial key inside the plugin
  • plugin is installed, save to file, kaboom

I do have a concept in which the user inputs a serial, the key gets checked against an existing database and counts uses, then above a certain number a key can stop functioning, although this is just online auth again with extra steps.

Could someone with some experience in this (or even insight) help me come to a good, affordable solution that wont diminish user experience by asking for a serial key every time they run the plugin (or just too frequently in general)

1 Like
2

Yes, we’ve implemented both forms of authentication you’ve mentioned here.

You can implement a system that tracks machine codes over successful login authorizations. That’s probably the easiest way to go about things.

Set up a server that hosts a database of users, implement an authentication flow, and manage the user’s needs to access the internet accordingly.

There’s nothing inherently wrong with iLok, and they do provide a no-dongle experience via iLok cloud.

Alternatively, you can check out MuseHub, which is actively looking for partnerships.

If you want a custom, affordable solution, I’m happy to help.