Twenty v2 CRM Sales Workspace

Deploys Twenty v2, an open-source CRM for companies, people and opportunities, with a separate background worker. For teams that want a sales workspace in their own Railway project instead of a per-seat SaaS CRM.

What you get

  • Twenty server (web app and API) and a separate Twenty Worker for sync, workflow, import and webhook jobs, both pinned to image v2.45.8
  • Postgres 18 and Redis 8.2, each on a volume
  • A Railway Bucket for attachments, so the server keeps no local state
  • Database migrations run in the pre-deploy step; all secrets are generated at deploy time
  • Optional SMTP, Google and Microsoft mail/calendar variables, also settable later in the Admin Panel

Good for

  • Running a sales pipeline of companies, contacts and opportunities
  • Syncing Gmail or Microsoft 365 mail and calendars into a shared customer timeline
  • Automating follow-ups with Twenty workflows and webhooks
  • Building internal tools on Twenty's GraphQL and REST APIs

Services in this template

  • Twenty · image twentycrm/twenty:v2.45.8
  • Twenty Worker · image twentycrm/twenty:v2.45.8
  • Postgres · image ghcr.io/railwayapp-templates/postgres-ssl:18
  • Redis · image redis:8.2

Questions people ask

How do I log in the first time?

Open the public URL and create your workspace. The first account created becomes the workspace admin. Without SMTP configured, invitation e-mails are written to the Twenty logs.

What drives the cost?

Five services run continuously: the Twenty server, the worker, Postgres, Redis and the bucket. The server and worker are the main memory users. Usage is billed per resource, so busy mail sync or workflow volume raises the worker's share.

Is my data kept across redeploys?

Yes. Postgres and Redis use volumes, and attachments are stored in the Railway Bucket.

How do I upgrade Twenty?

Change the image tag on both the Twenty and Twenty Worker services to the same version, back up Postgres first, then redeploy. Migrations run once in the pre-deploy step.

What licence does Twenty use?

The Twenty core is AGPL-3.0, and some enterprise files carry a separate commercial licence (see the upstream repository). Redis 8 is offered under RSALv2, SSPLv1 or AGPLv3. Review these terms if you plan to modify or resell the software.

Full template README

Deploy and Host Twenty with Railway

Twenty is an open-source CRM for managing companies, people, opportunities and workflows, with a fast spreadsheet-style interface and a full API. This community template runs Twenty v2 on Railway with a dedicated background worker, Postgres, Redis and a Railway Bucket for files, so your customer data stays in your own project.

About Hosting Twenty

Twenty is a NestJS server that also serves the web app, plus a worker process that handles background jobs: e-mail and calendar synchronisation, workflow runs, imports and webhooks. It needs Postgres for data, Redis for cache and job queues, and file storage for attachments. This template wires those pieces together on Railway's private network, keeps attachments in a Railway Bucket so the server stays stateless, runs database migrations as a pre-deploy step, and generates every secret at deploy time. SMTP and Google or Microsoft mail/calendar sync are prepared as optional variables and can also be set later in Twenty's Admin Panel.

Common Use Cases

  • Running a sales pipeline (companies, contacts, opportunities) for a team without per-seat licence fees
  • Syncing Gmail or Microsoft 365 mail and calendars into a shared customer timeline
  • Automating follow-ups and data updates with Twenty workflows and webhooks
  • Building internal tools on top of Twenty's GraphQL and REST APIs

Dependencies for Twenty Hosting

  • Twenty server and Twenty worker (twentycrm/twenty, pinned)
  • PostgreSQL 15 or newer (Railway Postgres 18)
  • Redis (cache and BullMQ queues)
  • S3-compatible object storage (Railway Bucket)

Deployment Dependencies

Implementation Details

Service Image Role
Twenty twentycrm/twenty:v2.45.8 API and web app on the public domain; runs migrations in its pre-deploy step
Twenty Worker twentycrm/twenty:v2.45.8 Background jobs (yarn worker:prod)
Postgres ghcr.io/railwayapp-templates/postgres-ssl:18 Database (volume)
Redis redis:8.2 Cache and job queues (volume, noeviction)
Bucket Railway Bucket Attachments and uploaded files

First login: open the public URL and create your workspace; the first account becomes the workspace admin. Without SMTP, invitation e-mails are written to the Twenty logs. To enable e-mail or Gmail/Outlook sync, fill the EMAIL_SMTP_*, AUTH_GOOGLE_* or AUTH_MICROSOFT_* variables on the Twenty service (the worker reads them by reference) and redeploy, or set them in Settings → Admin Panel.

Scaling: the server keeps no local state, so you can add replicas to Twenty; add replicas to Twenty Worker for heavy sync or workflow volume.

Versions: both Twenty services use the same pinned tag. To upgrade, change the tag on both, back up Postgres, and redeploy; migrations run once in the pre-deploy step.

Why Deploy Twenty on Railway?

Railway runs the server, worker, database, cache and bucket as one project with private networking, managed volumes and usage-based billing. You get a production-shaped Twenty install without maintaining servers, and you can scale each part independently as your team grows.

Guides for this template

View Twenty v2 CRM Sales Workspace on railway.com

Similar templates

TemplateCategoryDeploymentsDeploys
Chatwoot
A customer communication platform
Other5,871
Ubuntu-Linux
Ubuntu terminal accessible via web browser
Other4,926
Ubuntu SSH + Claude
ARA TM —SSH server with root access + Claude Code pre-installed.
Other4,682
Debian-Linux
Debian terminal accessible via web browser.
Other2,883
Code Server
VS Code in the browser
Other2,787
Kali Linux (Web Terminal)
Instant Kali Linux browser terminal powered by ttyd
Other2,632