The Caveman 3.0.0 release relicenses the whole repository under Apache-2.0, replacing a split arrangement in which the skill, CLI, SDKs, middleware and contracts were MIT while the engine-linked runtime (engine, proxy, rewriter, browse, MCP server, shrink, the cavemem Go core and shared platform) shipped under the Business Source License 1.1 with an Additional Use Grant. The project’s LICENSING.md says there is no longer a hosted-service restriction, Change Date or commercial license requirement for anything in the repository, that Caveman Cloud remains separate commercial software, and that releases before 3.0.0 keep their original terms, with outside contributors’ MIT code staying available under MIT. The same release also switched the CLI and its agent hooks to send usage statistics with a random install ID and the user’s IP address by default, opt-out through ‘caveman telemetry off’ or DO_NOT_TRACK, and moved the SDK from MIT to Apache-2.0.
Caveman relicenses from a split MIT and Business Source license to Apache-2.0
The Caveman 3.0.0 release relicenses the whole repository under Apache-2.0, replacing a split arrangement in which the skill, CLI, SDKs, middleware and contracts were MIT while the engine-linked runtime (engine, proxy, rewriter, browse, MCP server, shrink, the cavemem Go core and shared platform) shipped under the Business Source License 1.1 with an Additional Use Grant. The project's LICENSING.md says there is no longer a hosted-service restriction, Change Date or commercial license requirement for anything in the repository, that Caveman Cloud remains separate commercial software, and that releases before 3.0.0 keep their original terms, with outside contributors' MIT code staying available under MIT. The same release also switched the CLI and its agent hooks to send usage statistics with a random install ID and the user's IP address by default, opt-out through 'caveman telemetry off' or DO_NOT_TRACK, and moved the SDK from MIT to Apache-2.0.
Source: Github