On this page
- What counts as open source, and what does not?
- Which business models do open-source companies use?
- How does a hosted cloud version make money from free code?
- What is open core, and what lives in the "ee" folder?
- What do support subscriptions and SLAs actually buy?
- How does dual licensing work with AGPL?
- What are source-available and fair-code licenses, and what do they allow?
- What is an open source maintenance fee?
- Can sponsorships and donations fund a project?
- Where do marketplaces, paid editions, training and consulting fit?
- What happens when an open-source company changes its license?
- What should you check before you depend on an open-source vendor?
- Which model fits a new open-source product?
- Sources
Open-source companies make money by selling what the license leaves out. The code is free to read, run and change, so revenue comes from something next to it: a hosted version someone else operates, enterprise features kept outside the open core, support with guaranteed response times, a commercial license for buyers who cannot accept copyleft, or a license that keeps competing commercial uses for the vendor. Smaller projects add sponsorships, maintenance fees, marketplaces, paid editions, training and consulting. Most companies combine two or three.
For buyers, the model decides which features stay free, what the cloud costs and what happens if the vendor changes course. License terms and prices below were checked against official license files, announcements and pricing pages in November 2026. This is an explainer, not legal advice.
What counts as open source, and what does not?
The reference is the Open Source Definition maintained by the Open Source Initiative (OSI). Of its ten criteria, two settle most arguments in this article: a license may not discriminate against any person or group (criterion 5), and it may not restrict use in any field of endeavor, commercial hosting included (criterion 6).
A license that forbids offering the software as a competing cloud service fails criterion 6, which is why the OSI board stated in January 2021 that the Server Side Public License (SSPL) is not open source (OSI). Code under terms like these is called source-available: you can read it, often run and modify it, but some uses are reserved.
Two labels describe that space. Fair-code, used by n8n, means software that is generally free to use and distribute with its source available, while its authors restrict commercial use; its site calls it a model, not a license (faircode.io). Fair Source, started by Sentry in 2024, adds a schedule: code is released under a restrictive license first and published under an OSI-approved one later (Fair Source).
Which business models do open-source companies use?
| Model | How revenue comes in | What users get free | Examples | Watch-outs |
|---|---|---|---|---|
| Hosted cloud | Managed service billed by usage or seats | The self-hostable code | Supabase, Carbon, n8n | Prices change; check export |
| Open core | Licenses for features in "ee" folders | The core, under an OSI license | GitLab, PostHog, Langfuse | SSO, SCIM and audit logs often paid |
| Support and SLAs | Contracts with response times and compliance reports | Software and community help | Langfuse, Carbon | Quality hard to judge in advance |
| Dual licensing | Commercial license instead of AGPL | The full AGPL version | Ever Gauzy, Mattermost, MR Office | Vendor must control the copyright |
| Source-available and fair-code | Paid rights for reserved uses, plus a cloud | Internal use, readable code | n8n, Sentry, AutoGPT, JobOps | Not OSI open source |
| Maintenance fee | Fee for official binaries above a revenue threshold | Source and self-built binaries | WiX Toolset | Builds may require a EULA |
| Sponsorships and donations | GitHub Sponsors, Open Collective, contributions | Everything | Sure, WiX Toolset | Unpredictable; no SLA |
| Marketplace | Commission on third-party add-ons | The platform | Odoo | Each add-on has its own terms |
| Paid editions and apps | License keys for a Pro edition | The community edition | Cloudreve | Lapsed keys can limit an install |
| Training and consulting | Courses, certification, implementation | Docs, self-paced courses | GitLab, Carbon | Scales with people, not software |
How does a hosted cloud version make money from free code?
Running software is work: provisioning, backups, upgrades, scaling, patches and someone on call. A managed cloud sells that work, and for many open-source companies it is the main revenue line.
Supabase publishes its code under Apache 2.0 and sells hosted projects on a Free plan, Pro from $25 per month and Team from $599 per month (Supabase pricing, November 2026). Carbon, a manufacturing ERP, lets anyone self-host its core under AGPL-3.0 and charges $40 per user per month for its Starter cloud and $100 for Business, with a five-user minimum (Carbon pricing, November 2026).
The license often protects this revenue. AGPL makes anyone who offers a modified version over a network share its source, and the source-available licenses below forbid competing hosted offerings outright. When you compare a cloud with self-hosting, count the operating time you would take on, not only the subscription.
What is open core, and what lives in the "ee" folder?
Open core splits one codebase. Most of it is under an OSI license; a marked part, usually a folder named ee for "enterprise edition", needs a paid license. The root license file shows where the line runs.
- GitLab is MIT outside
ee/and under its own enterprise license inside it (GitLab LICENSE); Premium costs $29 per user per month, billed annually (GitLab pricing, November 2026). PostHog uses the same split (PostHog LICENSE). - Langfuse is MIT except for a few
eedirectories. Its free self-hosted edition includes enterprise SSO; SCIM provisioning, audit logs, project-level roles and data retention controls need an Enterprise license (Langfuse self-hosting pricing). - Carbon applies the split to AGPL code:
packages/eeand any file with.ee.in its name fall under the Carbon Commercial License (Carbon LICENSE).
Large organizations pay for administration features that small teams rarely need, which is why the model works. The risk for buyers is that the line moves. Cal.com, a scheduling platform that had been AGPL with a commercial enterprise folder, announced on April 14, 2026 that its commercial product would go closed source, and released the open code as Cal.diy under MIT (Cal.com). The Cal.diy README lists what is missing: teams, organizations, insights, workflows and SSO/SAML (Cal.diy on GitHub).
What do support subscriptions and SLAs actually buy?
The software stays the same; you pay for a commitment. Langfuse's self-hosted Enterprise tier includes a support SLA, a named lead support engineer, a private Slack channel and SOC 2 Type II and ISO 27001 reports (Langfuse). Carbon's Enterprise plan, run in the customer's cloud account, adds a forward-deployed engineer and support for CMMC Level 2 and NIST 800-171 deployments.
Nothing is withheld from the free version, which makes support the cleanest model for buyers. Before signing, ask which severity levels, hours and versions the SLA covers, and whether it applies to self-hosted installs.
How does dual licensing work with AGPL?
The same code is offered under two licenses. The public one is usually the GNU Affero General Public License v3 (AGPL), which requires anyone who lets users interact with a modified version over a network to offer them its source. Companies that want to ship or host modified versions privately buy a commercial license instead.
- Ever Gauzy publishes a Community Edition under AGPL-3.0 and sells Small Business and Enterprise licenses that let your changes stay proprietary, with free Enterprise licenses for qualifying non-profit and open-source projects (Ever Gauzy LICENSES.md).
- Mattermost offers its source under AGPL v3 or a commercial license, while the binaries Mattermost compiles come under MIT (Mattermost LICENSE.txt).
- MR Office, browser-based office editors, uses AGPL-3.0 with two extra terms allowed by its section 7, an attribution link and no trademark rights, and sells a commercial license on request (MR Office NOTICE.md).
This only works if the vendor controls the rights to every line; Ever Gauzy's license file states that its company holds the copyright or sufficient licenses to all components. Such projects usually ask contributors to sign a contributor license agreement (CLA). The same rights that let a vendor sell a commercial license also let it change the public one later.
What are source-available and fair-code licenses, and what do they allow?
These licenses publish the code but reserve some uses, most often running it as a competing service. None meets the Open Source Definition while its restriction applies.
| License | Use inside your company? | Sell hosting or a competing product? | Becomes open source later? |
|---|---|---|---|
| Business Source License 1.1 (BSL or BUSL) | Non-production always; production per the Additional Use Grant | Not where the grant excludes it | Yes, within four years of each release |
| Functional Source License (FSL) | Yes | No competing use | Yes, Apache 2.0 or MIT after two years |
| Server Side Public License (SSPL) | Yes | Only if you publish your whole service stack | No |
| Elastic License 2.0 (ELv2) | Yes | No hosted or managed service | No |
| PolyForm Shield | Yes | No competing product | No |
| PolyForm Noncommercial | Noncommercial purposes only | No | No |
| Commons Clause (added to another license) | Yes | No selling, paid hosting or support | No |
| Sustainable Use License (n8n) | Yes, for internal business purposes | No | No |
BSL 1.1. Published by MariaDB, it allows non-production use, lets the licensor grant production rights, and converts each version to a GPL-compatible license on its change date or fourth anniversary, whichever comes first (BSL 1.1). HashiCorp moved from the Mozilla Public License 2.0 to BSL on August 10, 2023 (HashiCorp). Terraform allows production use except offerings that compete with the vendor's paid versions, and each release becomes MPL 2.0 after four years (Terraform LICENSE).
FSL. Sentry replaced BSL with its Functional Source License on November 17, 2023: one fixed rule, any purpose except a competing use, and Apache 2.0 or MIT after two years (Sentry). Sentry ships under FSL-1.1-Apache-2.0.
SSPL and ELv2. The SSPL, written by MongoDB, requires anyone offering the software as a service to release the source of everything used to run it (SSPL). The Elastic License 2.0 forbids providing the software as a hosted or managed service, circumventing license keys and removing notices (Elastic License 2.0).
PolyForm. Shield allows any purpose except a product that competes with the software or the licensor's products, free products included (PolyForm Shield). AutoGPT uses it for its autogpt_platform folder and MIT for the rest (AutoGPT LICENSE). Noncommercial allows personal, research, charity, education and government use only.
Commons Clause. A condition added to another license that removes the right to sell the software, including paid hosting, consulting or support whose value comes substantially from it. JobOps pairs it with AGPL-3.0 (JobOps LICENSE): you may self-host and modify it, but not run a paid JobOps hosting service, while the vendor sells hosted plans at £30 per month, or £20 if you bring your own API keys (JobOps, November 2026).
Sustainable Use License. n8n allows use and modification for internal business, non-commercial or personal purposes, and distribution only free of charge for non-commercial purposes; files marked .ee. need an n8n Enterprise License (n8n LICENSE.md). Cloud plans start at €20 per month billed annually, and the self-hosted Business plan, at €667 per month billed annually, adds SSO and queue mode (n8n pricing, November 2026). Our n8n guide covers hosting options.
Open core vs fair code: what is the difference for buyers?
Open core gives you real open source plus a marked folder you can leave out, so the free part can be forked in full. Fair-code restricts the whole codebase, but narrowly: internal use is fine, while hosting for others and competing products are not, and no one can fork it into a commercial rival except from versions whose BSL or FSL change date has passed.
What is an open source maintenance fee?
The Open Source Maintenance Fee (OSMF) keeps the license open and charges for official binaries. WiX Toolset, which builds Windows Installer packages, is under the OSI-approved Microsoft Reciprocal License (WiX LICENSE). Since WiX v6, organizations that use its binaries in revenue-generating work and have annual gross revenue of US$10,000 or more pay by sponsoring the project on GitHub Sponsors (FireGiant docs).
The agreement states that the fee is not a license fee, exempts users who already pay the maintainers for support, and leaves everyone free to compile the source and redistribute their own binaries (OSMF EULA). From WiX v7, builds must accept the EULA, for example with wix eula accept. Put the fee through procurement before a build server stops on it.
Can sponsorships and donations fund a project?
They fund maintainers more often than companies. GitHub Sponsors takes nothing from personal-account sponsorships and up to 6% from organization sponsorships (GitHub Docs). On Open Collective, a fiscal host holds the money and handles invoices, tax and accounting for projects without a legal entity; Open Source Collective charges 10%, and listed hosts range from 3% to 10% (Open Collective docs).
Sure, a community fork of the abandoned Maybe Finance app, runs at that scale: AGPLv3, free to self-host, voluntary contributions on its demo, and hosted installs through PikaPods or Railway billed by those providers (Sure). Donation-funded software can be excellent, but no one is obliged to fix your bug. If it becomes critical, sponsoring it costs less than a migration.
Where do marketplaces, paid editions, training and consulting fit?
These rarely carry a company alone, but they add revenue around a large user base.
Marketplaces. Odoo takes a 30% commission on app sales in its store and 25% on in-app purchases, and accepts modules under licenses from GPL-3 and LGPL-3 to its proprietary OPL-1 (Odoo Apps). Check each module's license, not only the platform's.
Paid editions. Cloudreve, a self-hosted cloud drive, is GPL-3.0 and sells a Pro edition licensed per root domain. If its offline license key expires and cannot be refreshed, the site turns read-only; the same key carries any iOS app volume licenses (Cloudreve docs). Test that behavior before relying on a paid edition.
Training and consulting. GitLab sells instructor-led courses and a professional certification, while its self-paced GitLab University is free (GitLab Education Services). Implementation work is often bundled into enterprise plans, like Carbon's forward-deployed engineer. It pays well but grows with headcount.
What happens when an open-source company changes its license?
Relicensing is the largest risk for buyers who chose a product partly because it was open. Three cases followed a similar path: the vendor restricted cloud competitors, others forked the last open version under a foundation, and the vendor later reopened in part or was acquired. A fourth, in 2026, went further.
| Project | License change | Fork and its home | State in November 2026 |
|---|---|---|---|
| Terraform | MPL 2.0 to BSL 1.1, August 10, 2023 | OpenTofu, Linux Foundation from September 20, 2023; CNCF sandbox since April 23, 2025, under MPL 2.0 | Still BSL; IBM, which completed its HashiCorp acquisition on February 27, 2025, is the named licensor |
| Elasticsearch and Kibana | Apache 2.0 to SSPL and Elastic License, January 2021 | OpenSearch, created by AWS in 2021; OpenSearch Software Foundation (Linux Foundation) since September 16, 2024 | AGPL announced as an added option on August 29, 2024, alongside SSPL and ELv2 |
| Redis | BSD 3-clause to RSALv2 and SSPLv1, March 2024 | Valkey, Linux Foundation, March 28, 2024, from Redis 7.2.4 under BSD 3-clause | Redis 8 added AGPLv3 on May 1, 2025; 7.2 and earlier stay BSD |
| Cal.com | AGPL open core to closed source, April 14, 2026 | Cal.diy, published by Cal.com under MIT | Commercial product closed |
Sources: HashiCorp, Linux Foundation on OpenTofu, CNCF, IBM, Elastic, Linux Foundation on OpenSearch, Linux Foundation on Valkey, Redis.
Released versions keep the license they shipped with, so a relicense affects your upgrades, not the copy you run today. Forks that last have a neutral home and funded maintainers: OpenTofu launched with pledges of at least 18 full-time developers for five years, and Valkey with AWS, Google Cloud, Oracle, Ericsson and Snap behind it. And a vendor can only relicense what it controls: Redis's license file puts contributions from Redis 8 onward under an updated contributor license agreement (Redis LICENSE.txt).
Acquisitions carry a quieter version of the risk. Terraform's license now names IBM. Langfuse, bought by ClickHouse in January 2026, said no licensing changes were planned (Langfuse), and its license file now carries a ClickHouse copyright line. Promises are worth noting; the license file is what binds.
What should you check before you depend on an open-source vendor?
- License type, folder by folder. Read the root license, any
ee/license and NOTICE file. GitHub's badge is a poor guide: its API reports "NOASSERTION" for mixed-license repositories such as Langfuse and JobOps. Check whether each license is OSI-approved. - Contributor agreement. A CLA that assigns or broadly licenses contributions to the company makes dual licensing and relicensing possible. A Developer Certificate of Origin (DCO) only certifies that contributors may submit their code.
- Governance. Foundation projects such as OpenTofu, Valkey and OpenSearch are far harder to relicense, because no single company holds all the rights.
- Who holds the copyright. Read the copyright line and named licensor; acquisitions move both.
- Cloud pricing. Per seat, per usage unit or per workspace? Annual billing? Minimums, like Carbon's five users on Business?
- The paid feature line. List what you need (SSO, SCIM, audit logs, roles, data retention) and find which edition has each.
- Export and self-host path. Can you export data in a documented format and run the same version yourself, or is the self-hosted edition reduced, like Cal.diy?
- Binary and key terms. Do official binaries carry separate terms, like WiX's fee? What does a paid edition do when its key lapses?
- Change dates. Under BSL or FSL, note when your version becomes open source. A converted version is a fallback no one can withdraw.
Which model fits a new open-source product?
For software makers, start from what customers would still pay for if the code were free.
- A service people would rather not run: hosted cloud on a permissive or AGPL core, as at Supabase and Carbon.
- Large customers needing administration features: open core with a bounded
eefolder, as at GitLab and Langfuse. - Cloud resellers as the main threat: FSL or BSL, which keeps a path to open source but gives up the label meanwhile.
- Buyers who cannot accept copyleft: AGPL plus a commercial license, with a CLA from the first outside contribution.
- A library or build tool with no service to sell: sponsorships or a maintenance fee.
Our launch checklist for SaaS and open-source software covers the LICENSE file and contribution policy to prepare before release.
Sources
- The Open Source Definition, Open Source Initiativeopensource.org
- The SSPL is not an open source license, Open Source Initiative, January 19, 2021opensource.org
- Business Source License 1.1, MariaDBmariadb.com
- Introducing the Functional Source License, Sentry, November 17, 2023blog.sentry.io
- About Fair Source, Fair Sourcefair.io
- Fair-code, faircode.iofaircode.io
- Elastic License 2.0, Elasticelastic.co
- n8n license (Sustainable Use License), n8n on GitHubgithub.com
- Open Source Maintenance Fee, WiX Toolset documentation by FireGiantdocs.firegiant.com
- HashiCorp adopts the Business Source License, HashiCorp, August 10, 2023hashicorp.com
- Linux Foundation launches OpenTofu, Linux Foundation, September 20, 2023linuxfoundation.org
- Linux Foundation launches open source Valkey community, Linux Foundation, March 28, 2024linuxfoundation.org
- Redis is now available under the AGPLv3 open source license, Redis, May 1, 2025redis.io
- Elasticsearch is open source, again, Elastic, August 29, 2024elastic.co
- Why Cal.com is going closed source, Cal.com, April 14, 2026cal.com
Frequently asked questions
Does open source mean free of charge?
No. Open source describes the rights you receive, not the price. The Open Source Definition lets anyone, the original author included, sell copies or services, and the GPL family of licenses says outright that you may charge for distributing copies. What it rules out is restricting who may use the software or for what purpose. A vendor can charge for binaries, a cloud or support, but it cannot forbid uses of code it published under an open source license.
Can a company take back an open-source license?
Not for versions it has already released. Apache 2.0 and GPLv3 describe their grants as irrevocable, and the forks of Terraform and Redis were built on the last versions released under open terms. What a company can change is the license of future releases, and only for code whose copyright it controls.
Can I use AGPL software inside my company without publishing my changes?
Usually, with one nuance. Running an unmodified AGPL application triggers no source obligation. If you modify it, everyone who interacts with the modified version over a network must be offered its source code. For an internal tool those users are your own staff, so the obligation rarely exposes anything; it matters when customers or the public use the modified version. Ask counsel to confirm how this applies to your setup.
Is n8n free for commercial use?
For internal use, yes. The Sustainable Use License lets a company use and modify n8n for its own internal business purposes, so automating your own processes on a self-hosted instance is allowed. It does not let you sell n8n itself, for example by hosting it for paying customers, and features in files marked .ee. need an n8n Enterprise License.
Why do so many open-source companies choose AGPL?
AGPL closes the gap that ordinary GPL leaves for hosted software: a provider that modifies the program and offers it over a network must share its changes with the users. That makes it less attractive to run a competing hosted version without contributing, while the license stays OSI-approved. When the vendor also controls the copyright, AGPL creates demand for a commercial license. Redis and Elastic both picked AGPL when they returned to an OSI license.
Is self-hosting an open-source tool cheaper than paying for its cloud?
Not automatically. Self-hosting removes the subscription but adds servers, storage, backups, monitoring, upgrades and the time of whoever looks after them, and some features may still need a paid self-hosted license. It tends to pay off when you have operations skills in-house, heavy usage that the cloud bills per unit, or data that must stay on your own infrastructure. Compare both over a year, staff time included.
What happens to my data if an open-source vendor shuts down?
The code outlives the company: you can keep running the last release you have, and the community may fork it, as happened when the Maybe Finance codebase was continued as Sure. Your data is safest when it already sits in your own database or exports cleanly in a documented format. For a hosted service, read the contract's shutdown and export terms and keep regular exports.
Tools in this article
SupabasePostgres platform with auth, APIs, realtime and storage
CarbonOpen-core manufacturing ERP, MRP, MES and QMS on one Postgres schema, with REST API and MCP server
GitLabDevSecOps platform with Git repositories, merge requests, CI/CD, security scanning and planning
PostHogOpen-source product platform: analytics, session replay, feature flags, experiments and error tracking
LangfuseOpen-source LLM engineering platform for tracing, prompt management, evaluations and datasets
Cal.diySelf-hosted, MIT-licensed booking pages and calendar scheduling, the community edition of Cal.com
Ever GauzySelf-hostable ERP, CRM, HRM and ATS platform with time tracking, invoicing and desktop timer apps
MattermostSelf-hosted team chat with channels, playbooks, boards and calls on Go and PostgreSQL, free Entry mode or paid plans
Facts link to their official sources. Product details can change after publication: report an error or read the editorial methodology.




