Deploy and Host Relaticle on Railway

Relaticle is an open-source CRM: people, companies, opportunities, tasks and notes in a fast Filament interface, with custom fields, CSV import, team workspaces, an AI assistant that works on your own records, and an MCP server so Claude or ChatGPT can read and update the CRM for you. A self-hosted alternative to HubSpot, Pipedrive and Attio.

About Hosting Relaticle

Relaticle is a Laravel application that needs PostgreSQL, Redis, queue workers, a scheduler and a websocket server. This template deploys the official ghcr.io/relaticle/relaticle image pinned to v3.6.8 next to Postgres 17 and Redis, wired over Railway's private network. The web server, queue workers, scheduler and realtime server run together in the Relaticle service so uploads and imports share one volume. Database migrations run automatically on every boot.

Nothing to fill in at deploy time: the app key and the database and Redis passwords are generated for your deployment.

Common Use Cases

Sales pipeline: track deals through stages on a board, with values, owners and close dates
Contact and account management for a small team, with custom fields per workspace
Moving off HubSpot, Pipedrive or a spreadsheet: import people and companies from CSV
Asking the AI assistant about your pipeline, or letting an AI agent work on the CRM over MCP
Recruiting, fundraising or investor tracking with your own fields and stages
Keeping customer data on infrastructure you control

Dependencies for Relaticle Hosting

PostgreSQL 17 (included)
Redis for cache, sessions and queues (included)
A volume for uploads and imports (included)

Deployment Dependencies

Relaticle source: https://github.com/relaticle/relaticle
Website: https://relaticle.com
Self-hosting guide: https://relaticle.com/self-hosted
Image: https://github.com/relaticle/relaticle/pkgs/container/relaticle

Implementation Details

First login. Open your Relaticle URL once the deploy is green, enter your email, choose a password and click Sign up. You then name your workspace. The new workspace comes with sample records so you can look around; anything you add sits alongside them. Sign-up checks that your email domain can receive mail, so use a real address.

Sign-ups stay open. Relaticle is multi-tenant and has no setting to close registration. Anyone who finds the URL can create an account, but they only get their own empty workspace and cannot see yours. Teammates join yours through Invite teammates. If you want a check against bots, turn on Cloudflare Turnstile with RELATICLE_FEATURE_SIGNUP_CHALLENGE=true, TURNSTILE_SITE_KEY and TURNSTILE_SECRET_KEY.

Back up APP_KEY. It encrypts sessions and stored secrets. Copy it from the Relaticle service's Variables tab somewhere safe. If it is lost or changed, encrypted values cannot be read and everyone is signed out.

AI assistant. Add OPENAI_API_KEY or ANTHROPIC_API_KEY to the Relaticle service and redeploy. To run a local model instead, set OLLAMA_BASE_URL and OLLAMA_MODEL, or SELF_HOSTED_AI_URL, SELF_HOSTED_AI_KEY and SELF_HOSTED_AI_MODELS for any OpenAI-compatible server. The AI-guided setup chat for new workspaces is off by default because it needs a key; turn it on with RELATICLE_FEATURE_SETUP_CONVERSATION=true.

Optional settings (add them to the Relaticle service any time, then redeploy):

Email: MAIL_MAILER=smtp, MAIL_HOST, MAIL_PORT, MAIL_USERNAME, MAIL_PASSWORD, MAIL_ENCRYPTION and MAIL_FROM_ADDRESS. Until then, invitations and password reset mails are only written to the logs. Once mail works you can set REQUIRE_EMAIL_VERIFICATION=true.
Sign in with Google: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI=https:///auth/callback/google (register the same URI in Google Cloud), then RELATICLE_FEATURE_SOCIAL_AUTH=true.
Gmail and Outlook sync: RELATICLE_FEATURE_EMAIL_INTEGRATION=true plus GMAIL_CLIENT_ID/GMAIL_CLIENT_SECRET or AZURE_CLIENT_ID/AZURE_CLIENT_SECRET. See .env.example in the Relaticle repository for redirect URIs.
Custom domain: add it in the service's Networking settings, then set APP_URL to https://your.domain.

First boot takes one to two minutes while Postgres initializes and migrations run. The log may show Waiting on default database connection for a while; that is expected.

Background work. Queue workers process imports, AI chat and email sync, and the scheduler runs reminders and cleanup, all inside the Relaticle service. This template uses plain queue workers instead of Laravel Horizon to keep memory low, so the /horizon dashboard shows as inactive. That is expected.

Upgrading. Change the Relaticle service's image tag to a newer release (for example ghcr.io/relaticle/relaticle:3.7.0) and redeploy. Migrations run on boot. Read the release notes first; going back to an older image on a migrated database is not supported.

Scaling. Everything runs in one service with local file storage, which suits a single team. To run more web replicas, move uploads to S3 first (MEDIA_DISK, FILESYSTEM_DISK and the AWS_* variables), because a Railway volume attaches to one service only.

Why Deploy Relaticle 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 Relaticle 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.