This document is a draft. It is currently not in effect, so everything here is bogus now, but it may eventually become the guide for plugin licensing in the future.
VCV Rack is open-source software, but you should still familiarize yourself with the VCV Rack licenses before releasing your plugin, to avoid misuse of intellectual property. If in doubt, send any licensing questions to contact@vcvrack.com.
Since Rack is licensed under GPLv3, you may license your plugin under GPLv3 as well. You may do anything with your plugin that the GPLv3 allows, including selling it without a commercial license (below) as long as you release the source code under GPLv3.
This is the most common choice among plugin developers. Rack offers a VCV Rack Non-Commercial Plugin License Exception which allows you to license your plugin under any terms you want, as long as it is offered free of charge. You may choose:
Note that if you copy significant portions of Rack's code into your own plugin, you must license it under GPLv3.
If someone makes a fork of your non-GPLv3 open-source plugin that is not a Rack plugin (e.g. a port to VST or a digital hardware module), their source code becomes no longer linked to VCV Rack and is thus no longer a “derived work” of Rack, so Rack's license does not apply to their source code.
VCV offers commercial royalty licensing for Rack plugins by emailing contact@vcvrack.com. This license also includes permission to use the Component Library graphics by Grayscale, which are normally licensed for non-commercial use only.
It is recommended to contact VCV as early as possible in your development process to make sure the license agreement is ready well before you release your plugin. You can expedite the licensing processing by sending concepts and design mockups along with your license request.
You may also wish to sell your plugin on the VCV Store. Some benefits of distributing your plugin on the VCV Store:
You must follow the VCV Rack Plugin Ethics Guidelines in order to obtain a commercial plugin license: