How iFeature went from no licensing to a proper activation system with Moonbase

Jan is a music producer, DJ, and software developer who runs iFeature. He develops plugins in VST3 and AUv2 formats, focusing on sound design and production workflow tools. His customers are primarily electronic music producers ranging from hobbyists to professional artists who want deeper control over their sound and faster workflows inside their DAWs.

The previous setup

For the first years of iFeature, there was no licensing system in place at all. The distribution model was simple: customers purchased a plugin and downloaded it directly. There was no activation process, no license keys, no structured system for managing who had access to what.

Jan also previously used Patreon as a distribution channel, though updating plugin versions there was harder to manage in a structured way. "When I previously uploaded plugins on Patreon it was harder to update versions in a structured way. With Moonbase the files are hosted directly, which makes it much easier to update plugin versions and manage downloads for customers."

This approach worked in the early days when the customer base was small. "That approach worked early on, but it wasn't sustainable as the project grew and more customers started using the plugins."

The decision

Jan knew he needed a proper licensing and activation system. He looked into several options. "Before choosing Moonbase I looked into a few other options such as Gumroad licensing solutions and larger licensing systems like PACE/iLok. Many of them were either too heavy for an independent developer workflow or required significantly more setup and overhead."

Moonbase stood out because it was straightforward to integrate and specifically built for independent developers building creative software. "Moonbase felt like a much better fit for a small but growing plugin project."

The migration

Jan migrated his existing customers manually. Since there was no previous licensing system, the process was relatively straightforward. "Existing customers were migrated manually. Since there was no licensing system before, customers simply received their new license through the Moonbase system and could activate their plugin from that point onward. The transition was relatively straightforward and most users adapted quickly."

Implementation

Integration took roughly a couple of days from start to live. "The core setup itself was fairly quick, but testing the activation flow inside the plugins and making sure everything worked correctly across systems took a bit of additional time."

Once live, the customer flow is simple: purchase the plugin, download it, activate using their online license, start using it in their DAW. "From the customer's perspective the process is simple: purchase the plugin, download it, activate and start using it in their DAW."

What changed

The shift to Moonbase licensing had several concrete effects. Manual work decreased significantly. Files are now hosted directly by Moonbase, making version updates much easier to manage compared to the Patreon era.

The licensing system also enabled product bundling. "Another useful feature is the ability to create product bundles, which makes organizing and offering multiple plugins much more flexible."

It also created a much more professional experience for customers. There's no ambiguity about what they own. There's a clear activation process. License management is handled in one place. "Adding proper licensing through Moonbase significantly improved how we manage plugin distribution. It reduced manual work and created a much more professional experience for customers."

Where they are now

iFeature is actively developing new plugins focused on advanced sound design and production workflow tools. The Moonbase licensing infrastructure is now the foundation for managing the plugin ecosystem as it continues to grow. Jan can focus on building better tools for music producers instead of managing distribution logistics manually.