What’s the difference between open source, open core and source-available?
Read this page as JSON or Markdown.
Check code, features and commercial terms separately
A public repository, a free plan and an open-source license are different things. An open-core product can have an open-source foundation while SSO, audit logging or another module has separate terms. A paid support contract does not, by itself, change the license of the underlying code.
Record the edition you will actually deploy
Keep the license name and source link with the version, image or release artifact. Review optional components, bundled dependencies, connectors and model weights separately when they have their own terms. Check intended use, modification, redistribution and embedding against those terms.
The directory’s licensing facet is a way to find candidates, not a substitute for that review. The Open Source Definition provides a reference for distinguishing open source from source-available restrictions. Use the exact license text and applicable commercial agreement when making a procurement decision.
Sources and further guidance
Answer reviewed 2026-11-21. Check the exact edition, configuration and current vendor terms before deciding.