Self-hosted CRM: Run it on your server - Relaticle    

 Self-hosted

Your CRM, on your server. AGPL-3.0, Rela included.
==================================================

 Download the compose file, add two secrets, start it. Unlimited users, no per-seat cost, and an install below that is ready to paste.

 [ Read the guide ](https://relaticle.com/developers/self-hosting) [  View on GitHub    ](https://github.com/relaticle/relaticle) 

2 GB of RAM to start. Docker 20.10+ with Compose v2.

 Terminal       Copy  

  Your address  https://      

\# Download the compose file

 $ curl -o compose.yml https://raw.githubusercontent.com/relaticle/relaticle/main/compose.yml

\# Add the two secrets and your address

 $ cat > .env << EOF

 > APP\_KEY=base64:$(openssl rand -base64 32)

 > DB\_PASSWORD=$(openssl rand -hex 24)

 > APP\_URL=https://crm.example.com

 > EOF

\# Start Relaticle

 $ docker compose up -d

\# Create your admin account

 $ docker compose exec app php artisan make:filament-user

 The stack serves HTTP on port 80. For HTTPS, put a TLS reverse proxy in front. [Reverse proxy guide](https://relaticle.com/developers/self-hosting#reverse-proxy-and-ssl)

    https://crm.example.com/app 

 ![The opportunities board in Relaticle, served from your own address](https://relaticle.com/build/assets/app-pipeline-preview-1652w-B8jj_oNU.webp) 

  [ 1.9K+ GitHub stars](https://github.com/relaticle/relaticle) [ 68,000+ Docker pulls](https://hub.docker.com/r/manukminasyan/relaticle) [ 164 Discord members](https://relaticle.com/discord) 

 Open source

 Everything, under one license. Not a community edition. 
---------------------------------------------------------

 01

### Your data stays on your server

Every company, person, opportunity, task, and uploaded file lives on the PostgreSQL, Redis, and storage volumes compose.yml defines. Nothing is sent to Relaticle.

 02

### Source you can read and change

Everything a self-hosted install runs, including Rela and the MCP server, is on GitHub under AGPL-3.0. Audit it, modify it, and redistribute it under the same license.

 03

### One flat cost: your server

Unlimited users and unlimited records on every install. No per-seat price, no license fee, and no user-count paywall to hit.

 The stack

 Six containers from one command. Each one named in the published compose file. 
--------------------------------------------------------------------------------

### app

 ghcr.io/relaticle/relaticle 

Serves the app, the API and the MCP server, and runs migrations on startup.

### horizon

 ghcr.io/relaticle/relaticle 

The queue worker: imports, exports, email, and Rela's replies.

### scheduler

 ghcr.io/relaticle/relaticle 

Runs the recurring jobs: cleanup and notifications.

### reverb

 ghcr.io/relaticle/relaticle 

The websocket server that streams Rela's replies to the browser.

### postgres

 postgres:17-alpine 

PostgreSQL 17, on a volume you back up.

### redis

 redis:7-alpine 

Cache, sessions, and the queue, with append-only persistence.

 The guide also covers Dokploy, Coolify, Laravel Cloud, reverse proxies, backups, and a Docker-free manual install. [Read the full self-hosting guide](https://relaticle.com/developers/self-hosting)

 Rela, self-hosted

 Your keys, your models. Nothing answers until you configure a provider. 
-------------------------------------------------------------------------

 Providers

###  Rela ships in the image. You decide what it calls. 

- Relaticle does not meter AI credits on a self-hosted install.
- Claude or GPT with your own key, at your own usage rates
- Ollama, vLLM, or any OpenAI-compatible endpoint for a local model

 [ Choosing a model that calls tools    ](https://relaticle.com/developers/self-hosting#ai-assistant) 

 .env 

\# Cloud models, billed to your own account

ANTHROPIC\_API\_KEY=sk-ant-…

OPENAI\_API\_KEY=sk-…

\# A local model through Ollama

OLLAMA\_BASE\_URL=http://host.docker.internal:11434

OLLAMA\_MODEL=qwen3:14b

\# Or any OpenAI-compatible endpoint, such as vLLM

SELF\_HOSTED\_AI\_URL=http://host.docker.internal:8000/v1

SELF\_HOSTED\_AI\_MODELS=qwen3:14b,llama3.1:70b

 Self-hosted or Cloud

 Same CRM, two operators. Who runs the server, and who provisions the models. 
------------------------------------------------------------------------------

  Self-hosted Cloud 

Infrastructure

 Self-hosted: Your own server, under your own operational control.

 Cloud: Relaticle-managed infrastructure.

Updates and backups

 Self-hosted: You pull new images and back up PostgreSQL yourself. The guide has the pg\_dump commands.

 Cloud: Handled by Relaticle, with no maintenance window to schedule.

AI models

 Self-hosted: Bring your own provider key, or run a local model with Ollama.

 Cloud: Cloud-hosted models ready immediately, with no provider key required.

Getting help

 Self-hosted: Community support on Discord and GitHub issues.

 Cloud: Email support.

 FAQ

Self-hosting questions, answered
--------------------------------

 Something else on your mind? [Ask on Discord](https://relaticle.com/discord) or [open an issue](https://github.com/relaticle/relaticle/issues). [The contributing guide](https://relaticle.com/developers/contributing) covers local setup.

   What license is Relaticle released under?     AGPL-3.0. Everything a self-hosted install runs, including Rela, the built-in AI assistant, and the MCP server, is on GitHub under that license. Read it, audit it, modify it, and redistribute it under the same terms. 

   How do I update a self-hosted install?     Pull the new images and restart the stack: docker compose pull then docker compose up -d. Database migrations run automatically on startup, so check the release notes for breaking changes before you upgrade. 

   What does Rela need to work on a self-hosted install?     A provider it can call. Set an API key for Claude or GPT, or point it at Ollama or any OpenAI-compatible endpoint. With neither configured, the assistant has no model to answer with. 

   Where does my data live?     On the PostgreSQL, Redis, and storage volumes defined in compose.yml, all running on your own server. Nothing is sent to Relaticle-operated infrastructure unless you choose the hosted Cloud instead. 

   What server do I need?     The published minimum is 2 GB of RAM and 1 core, with 4 GB recommended for real workloads. Docker 20.10+ and Docker Compose v2 are required. 

   Can I move between self-hosted and Cloud later?     Yes. Both run the same CRM against the same schema, and every record type has a built-in CSV export, so moving between them is an export and re-import, not a proprietary migration. 

 Run it your way. Your server, or ours. 
----------------------------------------

 [  Deploy self-hosted    ](https://github.com/relaticle/relaticle) [ Try Relaticle Cloud ](https://relaticle.com/login) 

14-day trial, no card, unlimited users.
