CameoDB licensing
CameoDB uses a multi-license model inspired by the Sentry licensing policy. The codebase is deliberately split between a permissive core, MIT-licensed SDKs, and a protected product surface that converts to Apache-2.0 over time.
Permissive core
The cluster and storage crates are Apache 2.0, with patent protection, and stay that way.
MIT client tooling
SDKs and clients are MIT so they can be embedded anywhere, including GPL projects.
Time-limited protection
The server application is FSL-1.1-Apache-2.0 and becomes Apache-2.0 two years after each release.
What is covered by what
Licensing follows the directory, so the boundary is visible in the repository itself.
crates/cluster · crates/storageApache 2.0. Fully open-source core with patent protection.crates/clientMIT. Maximises compatibility, including with GPL projects.crates/serverFSL-1.1-Apache-2.0. Converts to Apache-2.0 two years after release.Full texts
Every license text is in the repository under licenses/.
What you can do
Self-hosted deployments
Run CameoDB freely for your own internal use and applications, under the licenses covering the components you deploy.
Competitive hosting
Offering the server components as a managed service is restricted by the Functional Source License. Exactly two years after a release, the FSL future grant converts that code to Apache-2.0 automatically.
SDKs and integration
Client tooling stays MIT, so it can be embedded in closed-source or GPL projects without restriction.
Contributing to CameoDB
Contributions are accepted under the same multi-license structure. By contributing you agree that your work may be distributed under Apache 2.0, MIT and FSL-1.1-Apache-2.0, as applicable to the components you modify.