Self-Hosted vs Cloud

Which deployment model is right for you?

Customermates is an Open-Source CRM, which means you can either use the managed cloud offering or run the product yourself in your own infrastructure.

The right choice depends less on feature checklists and more on operational priorities. Some teams want the fastest path to production with managed infrastructure and built-in AI agent provisioning. Others want maximum hosting control, internal deployment rules, and full ownership of the runtime environment.

Quick comparison

Category	Cloud	Self-Hosted
Setup time	Minutes	Depends on your infrastructure and deployment flow
Infrastructure management	Managed by Customermates	Managed by your team
Updates and operations	Handled for you	Handled by your team
Data hosting responsibility	Customermates cloud environment	Your own hosting environment
Open-Source flexibility
Full infrastructure control
Fastest onboarding
API and integrations
MCP and agent workflows
n8n and automation workflows
Sandboxed OpenClaw container on Pro plan		Self-managed setup

When cloud is the better choice

Cloud is the best fit when your team wants to get started quickly and avoid infrastructure work. It is especially strong when you want:

• the fastest route from signup to productive CRM usage
• managed updates and less operational maintenance
• built-in hosted operation instead of running your own stack
• the Pro-plan setup with a preconfigured sandboxed OpenClaw container for each user

For many teams, this is the most practical option because it keeps the system focused on CRM workflows instead of deployment work.

When self-hosted is the better choice

Self-hosted is the better fit when your organization wants to run Customermates inside its own infrastructure and keep the deployment model fully under its control.

That is especially relevant when you want:

• full control over hosting, networking, and runtime boundaries
• internal control over update timing and rollout strategy
• deployment inside your own cloud account or private infrastructure
• a setup that can be adapted to stricter internal operational requirements

The trade-off is simple: you gain more control, but you also take on more responsibility for deployment, updates, and runtime operations.

AI agents in both models

Both deployment models can support API integrations, MCP usage, and AI-driven workflows. The difference is mainly operational.

In cloud, Customermates manages the hosted runtime experience for you. In self-hosted environments, your team is responsible for how supporting services and agent runtimes are deployed and operated.

For the security model behind those runtime boundaries, continue with Architecture & Security. For the managed cloud AI-agent experience, continue with OpenClaw & AI Agents.