4 ms·
Developers often ask on HN: "How can I make a full-time living from my open source product?" Consider this scenario: You have created an open source library or
by open-source-ux 5y ago
Developers often ask on HN: "How can I make a full-time living from my open source product?"
Consider this scenario: You have created an open source library or programme and now want to sell it to customers. You would love to work on the product full-time. And it's important to you that the product remains open source. What are your options?
- Offer the product for free, but sell support. (No developer finds this option appealing.)
- Offer the product for free, but charge for documentation. (This is inherently user-hostile and encourages purposely complicated products to goad users to pay for the documentation.)
- Offer the product for free, but offer a paid hosting option if it is a server-based web app. (Users who do not want to pay for hosting will self-install the product.)
- Offer the product for free, but charge for a closed-source add-on with more features ('open core').
Notice a missing option in the list above? To sell you product with source code (with a open source licence attached) is simply not possible. And yet, this missing option probably appeals the most to creators.
The examples of commercial success of open source products are few and far between. You can make a list of a few dozen successful examples e.g. GitLab ('open core'), Red Hat (enterprise support) - but these examples are the exceptions, not the norm.
Sponsorship, donations or patreon campaigns are not steady or sustainable long-term options.
The alternative? Well, one option is to offer a source-only option for your product. You charge for your product and offer the source code at the same time. The customer is free to amend the code to suit their needs. This isn't open source though - the customer cannot re-distribute the code. This is the 'source-only' model.
Recently, some companies have created a hybrid model: free open-source code for non-commercial use and a paid license for commercial use. There is debate about whether this meets the spirit of open source development or not. Everyone has a opinion. You can make you up your own mind.
Finally, and quite ironically, there is a recent development in software (related to open source code) that has been wildy successful: SaaS (Software as a Service).
Why ironic? Because open source software has been critical to the success of the SaaS model. And yet, the source code for these services (built on open source) is not visible.
It's a model that takes away the hassle of installation and maintainence of software, but gives users less control of their data than the desktop software model that preceded it. Where you essentially "rent" an app until you stop payment.
You could argue SaaS is the true success of the 'open source business model'. Just not in the way open source advocates ever expected it to be.
- john_cogs 5y agoThis page in the GitLab handbook explains our approach in great detail: https://about.gitlab.com/company/stewardship/ https://about.gitlab.com/company/stewardship/ You may also want to check out this video of our founder/CEO Sid discussing commercial open source strategies: https://www.heavybit.com/library/video/commercial-open-source-business-strategies/ https://www.heavybit.com/library/video/commercial-open-sourc...
- fsflover 5y ago> To sell you product with source code (with a open source licence attached) is simply not possible. It's possible and it's called double licensing. Should work best with AGPLv3. https://en.wikipedia.org/wiki/Multi-licensing https://en.wikipedia.org/wiki/Multi-licensing
- webmobdev 5y agoOffer the product for free, but sell support. (No developer finds this option appealing.) This is new to me - do developers really not like providing paid support for their product? It's one of the easiest way to make money! The whole of India's IT industry makes money this way - the annual maintenance contract is a tried and tested business model. Even I've made easy money by doing light sys-admin tasks on VPS for clients. And I also feel you are missing a major point - not all developers are natural entreprenuers who know how to make money from their product. There is a big learning curve to figure out all the business stuff and often many developers don't have the time or inclination to do so. And yeah, SaaS provided a great way for companies previously averse to GPL licenses to really make money from it without adhering to the open source spirit behind it. And that is why all GPL software needs to be relicense under AGPL.
- jimmyvalmer 5y agoTime was software makers could make a living just selling CD-ROMs in shrink-wrapped boxes. They'd of course augment their income by selling support, but few devs enjoyed "is your computer plugged in?" hand-holding. With everything now open-source, selling support is now all their income. Same thing happened to music industry. Artists could live off record sales alone, but ever since napster, going on tour is no longer optional if they want to maintain a proper rockstar standard of living.