YOUR DATA.
YOUR CALL.
Managed by us in the EU, or run it yourself on your Postgres and object store. Same binary, same models, same MCP tool surface.
THE CONTEXT LAYER HOLDS YOUR MOST SENSITIVE DATA.
A context graph is valuable precisely because it holds what matters: client relationships, meeting records, proposals, the frameworks your team keeps re-explaining. That is what makes an agent useful — and exactly what many firms cannot hand to a vendor lightly, whether because of client contracts, regulation or simple prudence.
CMP42 gives you the choice. Let us run it for you in the EU, or run it inside your own environment on infrastructure you already operate. The product does not change between the two: same binary, same models, same MCP tool surface.
Self-hostability is also a guarantee you benefit from even if you never use it. A CRM you could run yourself is a CRM you are not locked into.
TWO WAYS TO RUN. ONE PRODUCT.
| Aspect | Managed · EU | Self-hosted |
|---|---|---|
| Who operates it | protagx | You |
| Where it runs | EU-hosted | In your environment, on your Postgres and object store |
| Binary and models | Same binary, same models | Same binary, same models |
| MCP, REST, GraphQL | Identical tool surface, same auth and audit trail | Identical tool surface, same auth and audit trail |
| Data leaving your control | None, except what you explicitly send to an agent you connect | Nothing leaves your environment |
| Training on your data | CMP42 does not train on your data | Not applicable — the data never reaches us |
| Analytics and tracking | No third-party analytics, no fingerprinting, no session replay | Your environment, your rules |
| Availability | Alpha with Design Partners from October 2026 | Design Partners: Alpha access. Image published in Beta, Q1 2027 |
CMP42 is released under the Functional Source License 1.1 — you may read, use, modify and redistribute the source; the only reserved right is standing up a competing commercial CMP42-as-a-service. Every release automatically becomes Apache 2.0 two years after publication, so the long-term open-source guarantee is written into the licence itself.
Self-hosted plans price at a 20% discount against the equivalent managed tier when paid annually — the discount reflects that you carry the operational responsibility. Support is business-hours email plus the community forum. The managed tier and the self-hosted image share one codebase and one export format, so migration works both ways with cmp42-export and cmp42-import; Design Partners test-migrate at no cost during the Alpha.
WHAT DATA LEAVES?
The short answer, in both setups:
- Managed EU tier: none, except what you explicitly send to an agent you connect. CMP42 does not train on your data. There are no third-party analytics, no fingerprinting, no session replay. An AVV / DPA is available on request.
- Self-hosted: nothing leaves your environment at all.
One distinction is worth spelling out, because it is easy to blur. CMP42 ships no proprietary AI layer — you choose the agent and the model. When you connect an agent, whatever it reads from your graph goes wherever that agent runs, under your agreement with its provider. Self-hosting CMP42 keeps the CRM inside your environment; which model sees what remains your decision, and the run history of a Process shows what each agent read.
More on the managed tier: EU data residency · GDPR-native by construction.
WHAT YOU NEED TO RUN IT.
CMP42 self-hosted runs the same binary as the managed service, on two pieces of infrastructure most engineering teams already operate:
- A Postgres database
- An object store
The container runs on Docker (docker-compose is the reference setup) or Kubernetes (a Helm chart ships with each release). CMP42 requires PostgreSQL 16 or later with the pgvector extension, and any S3-compatible object store for artefacts (tested against AWS S3, Cloudflare R2 and MinIO). For a small team (10 users, 100k records) plan on 2 vCPU / 4 GB RAM and about 20 GB of Postgres storage; a mid-sized team (50 users, 1M records) grows to 4 vCPU / 16 GB RAM and 100 GB Postgres with a read replica. Updates ship as container images with semantic version tags in GHCR; roll them out with compose or Helm, and the Postgres schema migrations bundled with the image apply on first start.
Your models are git-versioned files, so the ontology you shape during a managed Alpha is the same artefact you would deploy on your own infrastructure.
THE PATH TO THE SELF-HOSTED IMAGE.
The path to GA
- Now
- Design Partner Program opens. Twelve slots, applications close December 2026.
- Oct 2026
- Alpha begins. Weekly release cadence. Design Partners get access to the hosted platform, the self-hosted image and every model / process API surface.
- Q4 2026
- MCP tool surface stabilises. First case studies published.
- Q1 2027
- Beta opens to a broader waitlist. Self-hosted image published.
- H1 2027
- General availability. Pricing published. Design Partners keep their lifetime rate.
If running on your own infrastructure is a hard requirement, the Design Partner Program is the earliest way to evaluate the self-hosted image with a real workload. See the program →