Written for the people who make the tools: what a plugin is technically, how to protect one, and how to get it into musicians’ hands — on MuseHub and elsewhere.
The four routes for getting a plugin to customers — MuseHub, your own store, plugin marketplaces and bundles — with the trade-offs of each, what to prepare before you publish, and how to market a plugin without a marketing team.
A map of plugin development from idea to release: what a plugin is, the formats hosts load (VST3, AU, AAX), the languages and frameworks that do the heavy lifting, and how to protect and distribute the result.
Why a plugin needs licensing beyond revenue, the options from no-code DRM to an integrated SDK, what PACE and Cryptlex offer and cost, why building your own is usually a mistake, and how to choose for your size.
Twelve teams, 24 hours, one brief: build an app or plugin from scratch. What came out of the first MuseHub hackathon at Queen Mary University of London — the winners, the honourable mentions and the app that shipped.