When you build an audio plugin, licensing is unlikely to be the part of the project that gets you most excited. Your focus is more likely to be on the DSP, the user interface, presets, compatibility, performance and testing across different DAWs and operating systems. You are trying to create something that sounds great, works reliably and gives musicians a reason to buy it.
Licensing is important, but ideally it should simply work in the background. It should protect the product without becoming another major technical or operational challenge for the business.
The difficulty is that licensing has a habit of becoming more complicated as an audio business grows.
How licensing grows
What starts out as a relatively simple requirement to generate a license and allow a customer to activate a plugin can gradually become a much larger part of the underlying technology stack. Licensing can end up touching the plugin itself, customer accounts, activation and deactivation, online and offline use, subscriptions, upgrades, bundles, product versions and customer support. Each additional requirement can introduce another integration, database, API or piece of logic that needs to be maintained.
This is particularly relevant for smaller audio companies, where development resources are limited and the team is already responsible for building products, fixing bugs, supporting customers, managing releases and running the wider business. Licensing may not be the product they are trying to build, but it can still consume a surprising amount of development and operational attention.
From technical to operational
As the customer base grows, the problem can become even more apparent. A licensing system that works perfectly well for a relatively small number of customers may become much harder to manage when there are thousands of licenses across multiple products. The questions become more complicated:
- Who owns a particular license?
- Is it active?
- How many times has it been activated?
- Has it been transferred?
- Which version of the product is associated with it?
- Why is a particular customer unable to activate their plugin?
- What happens when a subscription ends or a customer changes device?
These are no longer purely technical questions. They quickly become operational questions that involve customer support, product teams, finance and management.
This is where licensing can quietly become an infrastructure problem.
The data licensing creates
There is another aspect that becomes increasingly important as the business grows: the data that licensing creates.
Every license represents a series of events and relationships. A license is issued, assigned to a customer, activated, potentially deactivated or transferred, and eventually renewed, upgraded or expired. Across thousands of customers and multiple products, this creates a potentially valuable source of information about how products are being acquired and used.
The challenge is that this information can become fragmented across different systems, creating data silos between the licensing platform, the plugin, customer databases and payment or subscription systems. Bringing that information together and turning it into something that a business can actually understand and use is not always straightforward.
This means that licensing can create two problems at the same time. There is the infrastructure required to reliably issue, activate and manage licenses, and there is the information generated by that infrastructure that can become increasingly valuable as the business grows.
We think this is an important distinction.
Licensing is infrastructure
Licensing should not simply be viewed as a mechanism for protecting an audio plugin. It is part of the infrastructure that sits underneath the relationship between an audio company and its customers.
That infrastructure should be reliable, straightforward for developers to integrate and capable of supporting a business as its products and customer base grow. It should also provide a clearer understanding of what is happening across the license base, without requiring developers to build and maintain an increasingly complex system themselves.
What we're doing about it
At Polaris, this is the problem we are trying to address.
We believe licensing infrastructure should reduce friction rather than create it. It should allow audio developers to concentrate on building great products while providing the underlying technology needed to manage licenses as their businesses grow.
Ultimately, the goal is simple: licensing should be something an audio developer can rely on, rather than another infrastructure problem they have to solve.
Building great audio products is hard enough. Licensing shouldn't make it harder.
Building audio software and want an early look? We'd like to hear what you are working on.