Deploy Twenty CRM with Worker & Shared S3

Deploy and Host Twenty CRM with Worker & Shared S3 on Railway

CRM with Postgres, Redis, background worker and shared S3 file storage.

About Hosting Twenty CRM with Worker & Shared S3

Deploying this template creates Postgres, Redis, Twenty, Twenty Worker in your Railway project. The application receives an HTTPS domain automatically. Database and Redis services, when included, use private networking and generated credentials. Persistent data is stored on the included volumes or object storage, so application redeploys do not discard it.

Why Deploy Twenty CRM with Worker & Shared S3 on Railway

• Separate Twenty web and background worker services, using the same official image digest.
• Private PostgreSQL 16 and password-protected Redis with persistent storage.
• One Railway S3-compatible bucket shared by server and worker; files are not split across local disks.
• Generated encryption/signing keys, referenced by the worker rather than generated twice.

Common Use Cases

• Track contacts, companies and sales opportunities.
• Coordinate customer follow-ups and background integrations.
• Keep uploaded CRM files available to both web and worker services.

Dependencies for Twenty CRM with Worker & Shared S3

• A Railway account and a plan with capacity for 4 service(s).
• Included services: Postgres, Redis, Twenty, Twenty Worker.
• 2 persistent volume(s), provisioned by this template.
• One shared Railway S3-compatible object storage bucket, provisioned by this template.
• External integrations, mail delivery and your own business data are configured after installation as needed.

First launch

1. Deploy and wait for the database, Redis and storage bucket to become ready. Apps may restart while their dependencies initialize.
2. Open the Twenty web domain and complete the first-workspace setup.
3. Keep the Twenty Worker service running for background jobs.
4. Configure SMTP, calendar and email integrations in the application when you need them.

Operations

Back up PostgreSQL and the TwentyFiles bucket; preserve ENCRYPTION_KEY. The server runs migrations and cron registration while the worker disables both. No unused local file volumes are included. After a domain change update SERVER_URL on Twenty; the worker follows it by reference.

Images are pinned to verified upstream image digests captured on 2026-10-17. Review upstream release notes, back up persistent data and update the image deliberately when upgrading. Railway charges the deployer for running services, storage and network usage.

Support and upstream

For Railway template wiring or deployment issues, use the discussion/support link on this template page. Include service names and redacted logs; omit passwords and tokens. Application documentation:

Official deployment configuration · Twenty self-hosting