This website uses cookies to better the user experience of its visitors. Where applicable, this website uses a cookie control system, allowing users to allow or disallow the use of cookies on their computer/device on their first visit to the website. This complies with recent legislative requirements for websites to obtain explicit consent from users before leaving behind or reading files such as cookies on a user’s computer/device. To learn more click Cookie Policy.

Privacy preference center

Cookies are small files saved to a user’s computer/device hard drive that track, save, and store information about the user’s interactions and website use. They allow a website, through its server, to provide users with a tailored experience within the site. Users are advised to take necessary steps within their web browser security settings to block all cookies from this website and its external serving vendors if they wish to deny the use and saving of cookies from this website to their computer’s/device’s hard drive. To learn more click Cookie Policy.

Manage consent preferences

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookies list
Name _rg_session
Provider rubygarage.org
Retention period 2 days
Type First party
Category Necessary
Description The website session cookie is set by the server to maintain the user's session state across different pages of the website. This cookie is essential for functionalities such as login persistence, ensuring a seamless and consistent user experience. The session cookie does not store personal data and is typically deleted when the browser is closed, enhancing privacy and security.
Name m
Provider m.stripe.com
Retention period 1 year 1 month
Type Third party
Category Necessary
Description The m cookie is set by Stripe and is used to help assess the risk associated with attempted transactions on the website. This cookie plays a critical role in fraud detection by identifying and analyzing patterns of behavior to distinguish between legitimate users and potentially fraudulent activity. It enhances the security of online transactions, ensuring that only authorized payments are processed while minimizing the risk of fraud.
Name __cf_bm
Provider .pipedrive.com
Retention period 1 hour
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to support Cloudflare Bot Management. This cookie helps to identify and filter requests from bots, enhancing the security and performance of the website. By distinguishing between legitimate users and automated traffic, it ensures that the site remains protected from malicious bots and potential attacks. This functionality is crucial for maintaining the integrity and reliability of the site's operations.
Name _GRECAPTCHA
Provider .recaptcha.net
Retention period 6 months
Type Third party
Category Necessary
Description The _GRECAPTCHA cookie is set by Google reCAPTCHA to ensure that interactions with the website are from legitimate human users and not automated bots. This cookie helps protect forms, login pages, and other interactive elements from spam and abuse by analyzing user behavior. It is essential for the proper functioning of reCAPTCHA, providing a critical layer of security to maintain the integrity and reliability of the site's interactive features.
Name __cf_bm
Provider .calendly.com
Retention period 30 minutes
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to distinguish between humans and bots. This cookie is beneficial for the website as it helps in making valid reports on the use of the website. By identifying and managing automated traffic, it ensures that analytics and performance metrics accurately reflect human user interactions, thereby enhancing site security and performance.
Name __cfruid
Provider .calendly.com
Retention period During session
Type Third party
Category Necessary
Description The __cfruid cookie is associated with websites using Cloudflare services. This cookie is used to identify trusted web traffic and enhance security. It helps Cloudflare manage and filter legitimate traffic from potentially harmful requests, thereby protecting the website from malicious activities such as DDoS attacks and ensuring reliable performance for genuine users.
Name OptanonConsent
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonConsent cookie determines whether the visitor has accepted the cookie consent box, ensuring that the consent box will not be presented again upon re-entry to the site. This cookie helps maintain the user's consent preferences and compliance with privacy regulations by storing information about the categories of cookies the user has consented to and preventing unnecessary repetition of consent requests.
Name OptanonAlertBoxClosed
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonAlertBoxClosed cookie is set after visitors have seen a cookie information notice and, in some cases, only when they actively close the notice. It ensures that the cookie consent message is not shown again to the user, enhancing the user experience by preventing repetitive notifications. This cookie helps manage user preferences and ensures compliance with privacy regulations by recording when the notice has been acknowledged.
Name referrer_user_id
Provider .calendly.com
Retention period 14 days
Type Third party
Category Necessary
Description The referrer_user_id cookie is set by Calendly to support the booking functionality on the website. This cookie helps track the source of referrals to the booking page, enabling Calendly to attribute bookings accurately and enhance the user experience by streamlining the scheduling process. It assists in managing user sessions and preferences during the booking workflow, ensuring efficient and reliable operation.
Name _calendly_session
Provider .calendly.com
Retention period 21 days
Type Third party
Category Necessary
Description The _calendly_session cookie is set by Calendly, a meeting scheduling tool, to enable the meeting scheduler to function within the website. This cookie facilitates the scheduling process by maintaining session information, allowing visitors to book meetings and add events to their calendars seamlessly. It ensures that the scheduling workflow operates smoothly, providing a consistent and reliable user experience.
Name _gat_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _gat_UA-* cookie is a pattern type cookie set by Google Analytics, where the pattern element in the name contains the unique identity number of the Google Analytics account or website it relates to. This cookie is a variation of the _gat cookie and is used to throttle the request rate, limiting the amount of data collected by Google Analytics on high traffic websites. It helps manage the volume of data recorded, ensuring efficient performance and accurate analytics reporting.
Name _ga
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga cookie is set by Google Analytics to calculate visitor, session, and campaign data for the site's analytics reports. It helps track how users interact with the website, providing insights into site usage and performance.
Name _ga_*
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga_* cookie is set by Google Analytics to store and count page views on the website. This cookie helps track the number of visits and interactions with the website, providing valuable data for performance and user behavior analysis. It belongs to the analytics category and plays a crucial role in generating detailed usage reports for site optimization.
Name _gid
Provider rubygarage.org
Retention period 1 day
Type First party
Category Analytics
Description The _gid cookie is set by Google Analytics to store information about how visitors use a website and to create an analytics report on the website's performance. This cookie collects data on visitor behavior, including pages visited, duration of the visit, and interactions with the website, helping site owners understand and improve user experience. It is part of the analytics category and typically expires after 24 hours.
Name _dc_gtm_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _dc_gtm_UA-* cookie is set by Google Analytics to help load the Google Analytics script tag via Google Tag Manager. This cookie facilitates the efficient loading of analytics tools, ensuring that data on user behavior and website performance is accurately collected and reported. It is categorized under analytics and assists in the seamless integration and functioning of Google Analytics on the website.

How Developers Can Make money with Open Source Projects

  • 157524 views
  • 7 minutes
Maryna Z.

Maryna Z.

Copywriter

Oleksandra I.

Oleksandra I.

Head of Product Management Office

Tags:

Share

Most people, when they think of open source software, imagine enthusiastic and generous developers who spend their days and nights creating software for free. Indeed, for a few decades “open source software” was synonymous with “free software.” Developing software with open code through group effort excluded the opportunity for profit. But today there are ways to profit from building open source software (OSS).

Lately, developers have started thinking about how to monetize their OSS. We're going to highlight a few common ways to make profits from open source software.

Software as a Service (OpenSaaS)

One way to monetize your open source project is by using the SaaS business model. This option makes sense if you have a fully-fledged application capable of generating demand. The SaaS model is a popular way to license software because it’s flexible and offers rapid deployment and decreased costs. What makes SaaS attractive is that the software is stored in the cloud; users only need a web browser to access an application. SaaS is a popular business model for vendors that build tools for HR, collaboration, content management, and project management.

SaaS solutions with a free codebase reduce development costs and eliminate the need to build redundant functionality. Additionally, the vibrant OSS community will gladly promote quality open source products. With an OpenSaaS model, software is purchased via subscriptions, which can offer varying levels of service. For example, you might offer technical support, software customization, and trainings as package options. WordPress and Sharetribe are two bright examples of OpenSaaS products. Let’s see how they function.

WordPress as OpenSaaS

WordPress effectively functions as a free SaaS product: it’s an open platform, and it offers subscription plans with extra features like unlimited storage, automatic backups, customizable themes, and custom domain names. We say “effectively,” however, because WordPress technically comes in the form of a software product you can install on your own web server and maintain independently. The SaaS version of WordPress can be found at wordpress.com. If you choose this service, then WordPress hosts your application for you. However, since there’s no vendor lock-in, a customer can easily switch to a self-hosted WordPress version any time.

Sharetribe as OpenSaaS

Sharetribe, a marketplace builder, is another great example of an OpenSaaS product. It comes in two versions: a self-hosted free version which can be found on GitHub, and a cloud-based hosted version at sharetribe.com. With the SaaS version of Sharetribe, customers receive software hosted on Sharetribe’s servers along with full-cycle support and maintenance, from installation to backups. With the SaaS version, customers don’t have to worry about updating their software, as this is done by Sharetribe. But while the SaaS version receives great support and additional offerings like custom domain and removal of Sharetribe branding, this version of Sharetribe is less customizable, only allowing you to personalize marketplace filters and change colors, images, and block position in the user interface.

With the open source version of Sharetribe, on the other hand, the customer has to deploy Sharetribe on their own server and run updates and backups themselves. The GitHub community offers decent support, but ultimately you’re on your own.

Though there aren’t many examples of OpenSaaS products on the market today, we feel that this business model is just beginning. The term ‘OpenSaaS’ was only coined in 2011 by Dris Buytaert, creator of Drupal. OpenSaaS is an exciting new trend that combines the best of both worlds, allowing people to build web experiences more easily than ever.

How developers can make money with open source projects

Paid support

Many OSS companies succeed by providing extra services.

Such as technical support, certifications, and trainings. In fact, most professional open source companies – including Red Hat, JBoss, and MySQl – have built their entire business by providing free solutions. They generate profits only from additional services.

The most common way to get revenue from OSS is to provide paid support. Red Hat sets the bar for this model, boasting substantial revenue. In 2016, the company – widely known for its enterprise operating system, Red Hat Enterprise Linux – announced a profit of 2.05 billion dollars.

Red Hat does admirably by selling yearly subscriptions for user and technical support. Customers can choose a subscription plan based on number of requests, severity of requests, support channels and hours of coverage. MySQL, the leading open source database, derives revenue from selling support subscriptions for their product.

Paid support is an effective tool for making profit from open source for a few reasons. First, enterprise owners can save money on their payroll. Instead of hiring in-house specialists, enterprises can have access to certified support specialists on a less expensive basis. Second, enterprises can have peace of mind knowing that they can call in the pros whenever a problem arises.

Dual licensing

Dual licensing allows companies to release commercial software (with a commercial license) that’s derived from free OSS commonly distributed under the GNU General Public (GPL) license. Dual licensing can be implemented in a few ways. In the first scenario, a company releases identical products under a commercial license and under a free license like GPL. In the second scenario, the company releases different versions under different licenses.

So what’s the point of dual licensing? The GPL license allows end users to run OSS, redistribute that software, and modify it. However, you can’t embed OSS solutions into your proprietary (commercial) software and make profit under a GPL license. This is precisely where you’ll need a commercial version of an open source product to have the right to sell your commercial software.

The most well-known example of successful dual licensing is MySQL. The company releases MySQL Enterprise Edition, MySQL Cluster CGE, and MySQL Standard Edition under commercial licenses while still offering two other products – MySQL Classic Edition and MySQL Community Edition – under the GPL license. The commercial versions receive enhanced security features, backups, 24/7 support and more.

How open source developers make money

Paid extra features or functionalities

Some companies make money with open source in this way: they distribute their software for free, but charge money for additional features, functionalities, or updates. We can't call such approach selling open source software.

As we mentioned previously, customers feel most comfortable paying for only the services they utilize. Which is why, charging money for extra functionality is attractive for a number of reasons. First, it’s quite clear what additional functionality customers are paying for. Second, customers can save money on deployment and troubleshooting when these services are included in paid packages. For instance, GitLab distributes their developer tools in three editions. Their version for enterprises includes premium support, file locking and advanced solutions for remote teams, and is billed per user.

Charging money for additional functionality works well for software designed for blogging, HR, collaboration, customer management, and other similar needs. WordPress provides their Premium and Enterprise customers, for instance, with additional websites and an additional workforce to maintain their WordPress sites. While the fee per developer is quite high – $5k USD per month – customers receive certified professionals assigned to specific technologies and businesses.

Paid certification

If software is popular enough, companies can offer certification opportunities for specialists who want to validate their knowledge and skills. Getting certified, as a developer, is quite useful for a number of reasons. First, it’s a great opportunity to differentiate yourself among other specialists with the same skills. Second, developers realize the importance of networking with mentors and groupmates. Finally, a developer’s certification leads lends them additional professional credibility and even promotions, and can boost a company’s image.

Open source giants including Magento and Red Hat offer a variety of certification options. In fact, Red Hat offers around 30 different kinds of certifications in Red Hat’s products as well as PaaS, business processes, deployment and system management. Magento issue certificates for skills related to Magento development and solutions.

Conclusion

Open source software is highly regarded thanks to its security, reliability, and vibrant communities that support it. Moreover, OSS helps companies avoid reinventing the wheel, and can even be used within proprietary software. Altogether, these factors have made OSS quite popular. Today, people are willing to pay for open source software to ensure legal protection, technical support, and professional services. With paid open source technologies, companies can offer the best of both worlds: transparent technology with the support and features of commercial software.

CONTENTS

Tags:

Authors:

Maryna Z.

Maryna Z.

Copywriter

Oleksandra I.

Oleksandra I.

Head of Product Management Office

Rate this article!

Nay
So-so
Not bad
Good
Wow
64 rating, average 4.67 out of 5

Share article with

Comments (1)
Christopher Dunsford
Christopher Dunsford over 4 years ago
Great read. Thank you
Reply

Subscribe via email and know it all first!