Glossary
Open Core
The core is open source and free to run; the company sells what sits around it: enterprise features, managed hosting, support, packaged builds. Reading the licences tells you where the line is.
General definition
Open Core is the most common way an open-source product funds itself. The company publishes the core under an open-source licence, builds a community and a user base on it, and sells additions that organisations rather than individuals need: single sign-on and audit features, scale and high-availability options, a managed cloud, support with a service level agreement, or a packaged distribution with a commercial licence. GitLab, with a permissively licensed community edition and a proprietary enterprise edition, is the textbook case; many infrastructure and developer-tools companies follow the same pattern with different lines between the tiers.
- Open-source core: under an OSI-approved licence such as MIT, Apache 2.0, GPL or AGPL, usable and modifiable by anyone, including competitors
- Commercial layer: enterprise-only features, a hosted service, support contracts, or a distribution licence with terms the open licence does not have
- Source access: some vendors give enterprise customers the source of the commercial layer under contract, so the code is auditable even where it is not open
- Source-available: a different model, where code is published but under a licence that restricts commercial or competing use and is not open source
Reading an open core product means reading at least two documents. The licence on the repository tells you what you may do with the core: a permissive licence lets you embed it in a closed product, a copyleft licence such as AGPL requires you to share modifications, including when you offer the modified software over a network. The commercial terms tell you what the packaged distribution, the enterprise features and the hosted service cost and permit. The two are often different, and that difference is the business model, not a contradiction. Several well known projects have moved their core from open-source to source-available licences in recent years, which is why checking the current licence rather than the one you remember matters.
For buyers, open core offers an exit: if the vendor disappears or the relationship sours, the core keeps running and can be maintained by anyone. For vendors, the risk is a cloud provider offering the core as a service without contributing, which is the pressure behind both the AGPL and the source-available moves.
In the Ethora ecosystem
Ethora is open core. The platform’s source is published on GitHub as a monorepo under the AGPL, so anyone can read, run and modify it, and must share modifications if they run a modified version as a network service. The packaged Ethora Core distribution, the Docker images, Helm chart and marketplace images used for self-install, ships under the Ethora Core Software License: free to run, with per-server limits of 5 apps and 500 user accounts, raised to 10 apps and 5,000 accounts after free registration on the admin License page.
The commercial layer is the managed service and the enterprise relationship: a managed cloud with a free tier, a dedicated server run by Ethora TechOps in your own cloud account or on-premise with an enterprise SLA, a BAA and DPA where needed, and enterprise source access so a customer can audit what it runs. A team building a white-labelled app can therefore choose its own line: self-host the core under its licence, or buy the dedicated, supported version and keep the same code. The options are compared on the pricing page.