4 ms·
I've built two open source startups, totaling a decade of my life. Take it from me: the only way to do this sustainably is open core. That means you make the c
by benwerd 2y ago
I've built two open source startups, totaling a decade of my life. Take it from me: the only way to do this sustainably is open core.
That means you make the core software open, but you sell the features that businesses will pay for or that allow other people to make money. Think of it as two distinct products for two distinct userbases.
In effect, the open source software becomes lead gen; the closed software is your actual business. They're both integral, and obviously feed into each other, but most of your open source users will never, ever be customers.
- gigamick 2y agoCan you point me to your startups? I'm not entirely sure I understand how to implement this.
- solardev 2y agoNot the OP and not the maintainer, but an open core example product that I love (and pay for at some companies) is MUI: https://mui.com/pricing/ https://mui.com/pricing/ They're a React UI framework with many free and some paid components.
- lysecret 2y agoAlso an example of open core is https://www.quantconnect.com/ https://www.quantconnect.com/
- Onavo 2y agoTheir monetisation strategy is from cloud hosting and being a data provider, very different from open core.
- edg5000 2y agoOdoo is ERP/CRM software that comes to mind when open core is mentioned. PS Also look into Cesium, they approached it in a smart way as well, by offering a web services tightly coupled wity, but optional from their open source product.
- handfuloflight 2y agoCan you switch the licenses? I'm assuming since no consideration is exchanged, there's no contract, so you can change to a less permissive license.
- GTP 2y agoDepends on the license: e.g. the GPL can't be revoked, so once something gets GPL'd it remains so forever.
- shiroiushi 2y agoNo it doesn't. If you're the sole copyright holder of the code (e.g. it's a project you did by yourself), you can do what you want with it, including switching to a proprietary license. You can't retroactively un-GPL any copies that other people already have, of course, and it probably would look bad to take away older GPL versions from your GitHub page or wherever they're hosted, but you absolutely can make all new versions proprietary if you want.
- GTP 2y ago> You can't retroactively un-GPL any copies that other people already have That's what I meant when I said that you can't revoke the GPL. Of course with new versions you have more freedom, but what was relased under the GPL remains available under the GPL.
- Someone 2y ago> but what was relased under the GPL remains available under the GPL. Not necessarily. The copyright holder only has to provide source to those who got it from them under a GPL license. Others may not be able to get a copy, as those who can ask you for it aren’t obliged to give it to them on request (https://www.gnu.org/licenses/gpl-faq.html#CanIDemandACopy https://www.gnu.org/licenses/gpl-faq.html#CanIDemandACopy) There also is the issue as to what happens when a license holder dies or is dissolved. I think that’s a gray area. Let’s say company Foo releases a product with a GPL license and later goes bankrupt. If Bar buys the source code from the bankrupt company, I don’t see how they would have to release it under the GPL, or should legally be obliged have to give the source code to those who got a license from Foo, and Foo can’t provide it anymore, as it doesn’t exist. Similarly, if you only give (or sell) your GPL-licensed software to an individual who later dies, does their estate inherit the right to ask you for the source code?
- byefruit 2y agoHow do you handle contributions to the open core? Do you require a CLA? I've been wondering about this for a project of mine. If one goes for an AGPL license but offers a commercial license for those that can't comply then a CLA is necessary from any contributors.
- benwerd 2y agoYou absolutely do need a CLA.