Cloud CRM for flexible sales workflows

Cloud-based CRM software is a customer-relationship system that the provider operates as a managed online service and that a team accesses through a browser. Customermates Cloud manages the application and database service while your team configures users, permissions, records, pipelines and connected providers.

What Customermates Cloud actually includes

The managed product brings contacts, organizations, deals, services and tasks into one workspace. Teams can define typed custom fields, work in table, card and kanban views, inspect activity history and configure deal stages with probabilities. Dashboards show current operational values, including total and weighted deal or pipeline values.

REST, webhooks and MCP are available for supported integrations and externally operated workflows. These interfaces do not imply that every accounting, marketing, data or automation provider is built into Customermates.

Managed cloud or self-hosting?

Customermates offers a managed service and a separately operated open-source core. They share the core CRM, but they are not feature-identical editions.

Choose the managed cloud when you want Customermates to operate the application and database and when your workflow needs cloud plan entitlements. Evaluate self-hosting when operating Docker, PostgreSQL, updates, backups and connected providers is an intentional requirement rather than a generic preference.

How a team starts with Customermates Cloud

1. Create a small workspace

   Start the Pro trial and invite only the teammates needed for the first evaluation.

2. Model one real pipeline

   Add a few synthetic or approved test contacts, organizations and deals, then configure the stages and fields your team actually uses.

3. Test the working views

   Compare table, card and kanban views and verify the relationships and permissions behind the workflow.

4. Connect only what is necessary

   Add an entitled messaging account, webhook, REST integration or MCP client only after its data and permission boundary is understood.

5. Review the operating choice

   Decide whether the managed service fits, or whether the Starter boundary and operating work of self-hosting are preferable.

Database region, security and provider boundaries

The primary production database is configured in AWS Frankfurt (eu-central-1). This is a selected product setting, not a contractual promise that every service or transfer remains in that region. Application hosting, monitoring, connected-account transport and any provider selected by a customer have their own locations and transfer paths.

The Data Processing Agreement documents measures including TLS in transit, encryption for the production database and backups at rest, role-based access, account-level segregation, monitoring and restoration procedures. It does not claim a security or compliance certification. The current subprocessor list records the providers, purposes, known locations and transfer bases used by the managed service.

AI and automation without false promises

Every managed-cloud plan includes a Mate entitlement and a plan-specific monthly hosted-AI credit allowance per active user. Whether Mate is live depends on the hosted environment's current configuration. When enabled, Mate works inside the CRM, uses the current user's permissions and applies separate confirmation controls to sensitive actions.

External AI clients can use the Customermates MCP server with a model provider and subscription selected by the customer. They use the customer's provider rather than Customermates hosted-AI credits. When Mate is enabled, the two paths share supported CRM tools and permission checks, but not their client, billing or confirmation path.

For automation, teams can call REST, receive webhooks, use MCP or connect a separately operated workflow tool such as n8n. Customermates does not include the n8n runtime, its third-party connectors or their provider contracts.

Migration and reporting boundaries

Customermates has no dedicated CSV or CRM-record import/export workflow. Moving data from another CRM requires a separately designed REST or MCP process with explicit source mapping, validation, deduplication, retries and an agreed rollback.

Dashboards, activity history, stage probabilities and weighted deal or pipeline values help a team inspect the current workspace. They are not predictive close or revenue forecasts, lead scores, conversion analytics or pipeline-velocity analysis.

Plans and connected-account allowances

The 7-day trial starts on Pro. LinkedIn, email, calendar, AI, automation and other external-provider subscriptions remain separate where required.

Who Customermates Cloud fits

Customermates Cloud fits teams that want a managed, browser-based CRM for flexible records and pipelines, prefer explicit interfaces over a closed integration promise, and value a separately self-hostable open-source core.

It is not a fit when the requirement is a complete ERP, accounting, inventory, invoicing, helpdesk, call-center, predictive-analytics or turnkey migration suite. Those workflows require different products or a deliberately designed integration.

Frequently asked questions