Deploy and Host Twenty on Railway

Twenty is a modern open-source CRM for managing contacts, companies, opportunities, pipelines, tasks, notes, dashboards, and automated workflows. Its adaptable data model, table and Kanban views, APIs, and team collaboration features let organizations shape customer operations around their own processes while retaining control of their data.

About Hosting Twenty

Hosting Twenty requires a public application server, a private background worker, PostgreSQL, Redis, and durable storage for both relational data and uploaded files. This Railway template pins Twenty 2.23.2, PostgreSQL 16.8, and Redis 7.4.2. The server runs database setup and upgrades, registers recurring jobs, serves the UI on port 3000, and exposes /healthz; the worker runs yarn worker:prod without repeating migrations or cron registration. Railway supplies private networking, HTTPS, a shared S3-compatible bucket, persistent database/cache volumes, and generated database and application secrets. Email, calendar, and OAuth integrations remain optional and are configured by each deployer after setup.

Common Use Cases

• Manage contacts, companies, sales opportunities, pipelines, tasks, and notes in one self-hosted CRM
• Build team-specific objects, fields, views, dashboards, and automated workflows
• Integrate customer operations with APIs, webhooks, email, Google Workspace, or Microsoft 365

Dependencies for Twenty Hosting

• PostgreSQL 16.8 for users, workspaces, CRM records, configuration, and migrations
• Redis 7.4.2 with noeviction for queues, caching, and background work
• A shared Railway S3-compatible bucket for files plus persistent PostgreSQL and Redis volumes

Deployment Dependencies

• Twenty 2.23.2 source
• Twenty Docker Compose self-hosting guide
• Twenty self-hosted configuration guide
• Twenty 2.23.2 Docker Compose contract
• Umbrel Twenty 2.23.2 package

Implementation Details

PG_DATABASE_URL and REDIS_URL use Railway service references. SERVER_URL and the requested FRONT_BASE_URL point to https://${{Twenty.RAILWAY_PUBLIC_DOMAIN}}. Railway generates APP_SECRET once on Twenty, and Twenty Worker references that authoritative value rather than generating another secret. Both processes use STORAGE_TYPE=S_3 and resolve the same bucket endpoint, name, region, and credentials through references, so worker-side file jobs operate on the files uploaded through the server.

The deployer selects the Railway bucket region during template deployment. The template does not pin a region; ${{Twenty Storage.REGION}} resolves to the region chosen for that deployment.

The first user creates the single workspace and becomes its administrator. SMTP, Gmail/Google Calendar, Google OAuth, and Microsoft 365 credentials have no defaults and are not copied from the template source. Add them after initial setup under Settings → Admin Panel → Configuration Variables.

Why Deploy Twenty on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Twenty on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.