I’ll try to answer let me know if I misunderstood what you said.
When you upgrade to JUCE 5, you still have the right to use and distribute products under the JUCE 4 license terms, but products built with JUCE 5 will need to be released under the terms of the JUCE 5 license.
How does a person obtain the FREE Juce 5 license? Is it automatic?
Also, I wonder if you need a wee bit more explanation. The way it sounds, from the email I received, I can use Juce5 for free and release a closed source statically linked program as long as my revenues are below $50K per year. The GIT disclaimer (above) seems to negate that and simply says that a paid license is required. I hope this is wrong.
Once I am through the development phase and start to generate some revenue, a paid license is not a problem.
The GitHub disclaimer is meant to say that the code on Develop needs to be used according to the terms of the JUCE 5 licence. And as will be more clear on the website very soon, the Personal license allows to release commercial, closed-source products for free, as long as total revenue is less than $50k yearly, and that a “Made with JUCE” splash screen is added to the app.
The other free option is the GPL one, which continues from JUCE 4 and has no restrictions of funding or splash screen, but requires to distribute the source along with your application.
I’d just like to say I think the move to create a free tier is great, and I believe will help JUCE to be adopted by more developers, which will benefit everyone.
Yes, if you currently have a JUCE indie license but are not generating more than $50k a year, you can switch to JUCE 5 Personal and still release closed-source apps (note that a splash screen will be added to your app).
Contact us at sales@juce.com if you need us to cancel your Indie subscription.
At this point I’m just wondering… does the Personal License’s $50k limit applies just to revenues made with JUCE related products or to my general yearly income as well, even if from totally unrelated stuff?
I have a “real” job as a Graphic Designer, and I’m lucky enough to be able to sustain my family and myself with it, but I’ve always been in love with audio/MIDI programming and I use a big chunk of my free time to play with Max and M4L (and now JUCE) to develop small plugins.
I was going to release the first one made with JUCE when I received the email with the new licensing model highlights…
As my yearly income is already really close to 50k from my main job (and sometimes over, it varies slightly between years), will I be able to release it under the Personal License (I don’t mind the splash screen) or will I need to pay for an Indie License?
The funding or revenue limit is for the whole revenue of a company or an individual. We feel that it’s fair to account for the whole revenue and not the sole revenue of JUCE-based products because some companies may release free software to help make other sales (such as hardware), and therefore generate low volumes of direct sales from JUCE-based products ; these companies should account for the whole revenue of the company to choose their license tier.
That being said, I understand that you are in an edge case, but if you create a company that looks after the sales of your plug-ins and keep your day job pay separate from that company, then you’ll only have to consider for the revenue limit the income from the company that distribute the plug-ins, which will indeed start lower than $50k.
I thought so… and I understand that you cannot possibly make hundreds of license tiers to fit everyone’s needs.
Also, your point makes sense and it seems quite fair to me as well… considering the reduced price for the Indie license (nice move, btw), I think I’ll go for that, at least for one year, and see how it goes.
Your suggestion could help… I’ll think about that, but I’m afraid that (being in Italy, where bureaucracy reigns) going down that particular road could cost me way more than the reasonable Indie fee…
Maybe I could just license JUCE to my wife, it would be definitely easier!
to be clear @jb1 - the GPL does not require anyone to distribute source code with every binary - it only requires that source code be made available upon request - developers may even charge a reasonable fee for the service