Hosting and deployment
Self-hosted CMP Core development versus proprietary managed CMP Cloud.
CMP Server can be run locally as a development-only Core repository backend. It is not currently production-certified, and the implementation refuses production mode and non-loopback binding.
The public server owns SQLite-backed context records, commits, branches, diffs and merges, plus an optional repository-only MCP adapter. It contains no managed organization identity, provider OAuth, CMP Connect, WebSocket agent streams, coordination service, or session archive storage.
CMP Cloud is the proprietary managed service with a separate backend and authorization model. Its operational environment, multi-tenant access policies and Cloud-only services are not bundled with the public server.
Do not forward an unreviewed local development server to the internet. A production self-hosted edition would require independent auth controls, access isolation, logging, backup/recovery, deployment and security audits.
See run a local server and Core versus Cloud.