Self-hosted CRM
A self-hosted CRM your IT team can run and understand.
This page is for the people who will operate Sigma CRM. It explains the stack, what a server needs, how updates and backups work and what stays inside your network. For the business decision between on-premise and cloud, see deployment.
The stack
What runs on your server.
Sigma CRM self-hosted is one Docker Compose project. Only the application is exposed, through your reverse proxy.
| Service | Job |
|---|---|
| db | PostgreSQL with a persistent volume, reachable only inside the stack |
| db-init | One-shot step that sets the service role passwords |
| auth | Authentication service for sign-in |
| rest | Internal REST layer over the database |
| storage | File storage for attachments, with a persistent volume |
| gateway | Internal API gateway and auth mail templates |
| migrate | One-shot database migrations; the app waits until they succeed |
| app | The Sigma CRM application and its background worker |
| cron | Scheduled calls for recurring CRM jobs |
Requirements
What your server needs.
A Linux server with Docker and Docker Compose, a domain, and a reverse proxy with TLS in front of the application. Building the images needs about 3 GB of free memory. We size the server with you based on your team and data.
- Docker and Docker Compose
- A domain and a TLS reverse proxy for the app
- Enough memory to build and run the stack
- Outbound access only for what you enable, such as email or a model provider
Want us to look at your infrastructure?
Operations
Backups and updates.
A complete backup needs both the database dump and the storage volume, because the database rows point to the files. Updates run the migrations in their own step first; if a migration fails, the deployment stops and the new version does not start.
- Database dump plus the storage volume
- Migrations before the app starts
- Each image passes linting, type checks and tests before it can ship
- You decide when to update
Explore Sigma CRM
Features
Custom fields, a flexible data model, views, workflows and roles.
FeaturesAI & MCP
How AI works in Sigma CRM: agents, observers, Sammy and model choice.
AI & MCPMCP server
All use cases, setup in 3 steps and the tool list for Claude and other MCP clients.
MCP serverDeployment
Run it on your own servers or in our cloud.
DeploymentPricing
Cloud subscription or Enterprise perpetual license.
PricingGuides
MCP servers, Claude, AI sales agents, implementation, migration and cost.
GuidesFrequently asked questions
Is Sigma CRM open source?
No. Sigma CRM is commercial software. Self-hosting runs under the Enterprise license, which is a perpetual license.
Which database does Sigma CRM use?
PostgreSQL. In the self-hosted stack it runs as its own container with a persistent volume and no published port.
Can we run it without internet access?
The CRM itself runs inside your network. Features that call outside services, such as email sending, enrichment or a cloud model provider, need outbound access to those services.
How do we back it up?
Back up the PostgreSQL dump and the storage volume together. A restore needs both.
Who installs it?
Your IT team or ours. We plan the setup with you and support the first deployment.
Plan your self-hosted setup with us.
We go through your infrastructure, sizing, backups and updates in one call.