Bitflake logo
← Back to Twenty

Self-host Twenty with Docker Compose

Open-source CRM built as a modern alternative to Salesforce.

twenty-crm

postgres

postgres:18.3-alpine3.23

redis

redis:7

The steps below take a few minutes end to end.

  1. Docker compose setup and file
    save the generated compose and env files.
  2. Secret generation
    create the random passwords Twenty needs.
  3. Start Twenty with Docker Compose
    bring the stack up and check it's healthy.

Requirements

You'll need these installed on the machine you're deploying to:

Docker

Packages Twenty and everything it depends on into an isolated container, so it runs the same way on your machine as it does everywhere else.

Install guide

Docker Compose

Reads docker-compose.ymland starts everything in it together. Ships with Docker Desktop. On Linux servers it's usually a separate install.

Install guide

1. Docker compose setup and file

Create a folder for Twenty and save the file below into it as docker-compose.yml. It describes every container the stack needs — Twentyitself and any supporting services, such as its database — along with the ports, volumes and environment variables each one uses. You'll also need an empty .env file in the same folder; Docker Compose reads it automatically and uses it to fill in the ${VARIABLE}references you'll see in the file below.

docker-compose.yml

version: "3.9"
services:
  postgres:
    image: postgres:18.3-alpine3.23
    restart: unless-stopped
    network_mode: service:twenty-crm
    environment:
      POSTGRES_PASSWORD: ${RANDOM_PG_PASSWORD}
      POSTGRES_USER: app
  redis:
    image: redis:7
    restart: unless-stopped
    network_mode: service:twenty-crm
    environment:
      REDIS_PASSWORD: ${RANDOM_REDIS_PASSWORD}
    entrypoint:
      - sh
      - -c
    command:
      - redis-server --requirepass $$REDIS_PASSWORD
  twenty-crm:
    image: twentycrm/twenty
    restart: unless-stopped
    ports:
      - 3000:3000
    environment:
      APP_SECRET: ${RANDOM_APP_SECRET}
      ENCRYPTION_KEY: ${RANDOM_ENCRYPTION_KEY}
      PG_DATABASE_URL: postgresql://app:${RANDOM_PG_PASSWORD}@localhost:5432/app
      RANDOM_PG_PASSWORD: ${RANDOM_PG_PASSWORD}
      RANDOM_REDIS_PASSWORD: ${RANDOM_REDIS_PASSWORD}
      REDIS_URL: redis://:${RANDOM_REDIS_PASSWORD}@localhost:6379/0
      SERVER_URL: http://localhost
    volumes:
      - server-local-data:/app/packages/twenty-server/.local-storage
      - tmp:/tmp
    healthcheck:
      test:
        - CMD
        - curl
        - -f
        - http://localhost:3000/
      interval: 10s
      timeout: 5s
      retries: 5
volumes:
  server-local-data: null
  tmp: null

Volumes

Twenty stores its data in named Docker volumes, so it survives container restarts and updates:

  • server-local-data mounted at /app/packages/twenty-server/.local-storage
  • tmp mounted at /tmp: writable scratch for migration/yarn tooling at startup.

2. Secret generation

Twenty needs a few randomly generated secrets — for example, database passwords or an internal session key — before it can start. These are referenced from docker-compose.ymlabove but don't live in it, so they need to end up in your .env file. Pick one of the two options below.

Generating secrets…

3. Start Twenty with Docker Compose

From the folder with docker-compose.yml and .env, run:

Terminal

Start Twenty and all its supporting services in the background.

docker compose up -d

The -d flag runs the stack in the background so it keeps running after you close the terminal. Docker will pull the images the first time, which can take a minute or two.

To check on it afterwards: docker compose ps shows whether containers are healthy, and docker compose logs -f follows their logs if something looks wrong. Once it's running, open http://localhost:3000 in your browser.