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.
The licensing overview on GitHub →- Permissive core The cluster, storage and MCP 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.
Licensing follows
the directory
Each crate’s manifest names its license, so the boundary is visible in the repository itself.
Every license text is in licenses/: Apache-2.0, MIT and FSL-1.1-Apache-2.0, plus the Unicode notice for the data the Japanese and Korean fold tables are derived from.
$ grep -H '^license =' crates/*/Cargo.toml crates/bench/Cargo.toml:license = "MIT" crates/client/Cargo.toml:license = "MIT" crates/cluster/Cargo.toml:license = "Apache-2.0" crates/mcp/Cargo.toml:license = "Apache-2.0" crates/server/Cargo.toml:license = "FSL-1.1-ALv2" crates/storage/Cargo.toml:license = "Apache-2.0" # FSL-1.1-ALv2 is the SPDX id of FSL-1.1-Apache-2.0
What you can do
Run it for your own work, embed the clients anywhere, and every server release opens up to Apache-2.0 two years after it ships.
- Self-hosted deployments Run CameoDB freely for your own internal use and applications, under the licenses covering the components you deploy.
- SDKs and integration Client tooling stays MIT, so it can be embedded in closed-source or GPL projects without restriction.
- Competitive hosting Offering the server components to others as a commercial product or service that competes with CameoDB is reserved under the Functional Source License. Exactly two years after a release, the FSL future grant converts that code to Apache-2.0 automatically.
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.