Deploy Dittofeed
Open-source customer messaging: email, SMS, push journeys with Temporal
Just deployed
/var/lib/postgresql/data
ClickHouse
Just deployed
/var/lib/clickhouse
Just deployed
Dittofeed
Just deployed
Deploy and Host Dittofeed on Railway
Dittofeed is an open-source (MIT) customer engagement platform. It sends transactional and marketing messages by email, SMS, mobile push, WhatsApp, Slack and webhooks. You track user events, build segments, and design journeys and broadcasts in a visual editor, as a self-hosted alternative to tools like Customer.io or Braze.
About Hosting Dittofeed
Dittofeed needs four parts: the app itself, Postgres for its data, ClickHouse for events and analytics, and Temporal to run journeys and background work. This template deploys Dittofeed lite v0.23.0 (dashboard, API and worker in one service), Temporal 1.32.2, ClickHouse 24.12 and Railway Postgres, all wired together over the private network. On first start, Temporal creates its own schema in Postgres and Dittofeed creates its tables and the Default workspace. Postgres and ClickHouse keep their data on volumes. After deploy, open the public URL and sign in with the generated PASSWORD from the Dittofeed service's Variables tab, then add your email or SMS provider under Settings.
Common Use Cases
- Transactional messages such as welcome, password reset and receipt emails sent from your own backend
- Lifecycle and onboarding journeys triggered by user events and segments
- One-off broadcasts and newsletters to a segment, with subscription management
Dependencies for Dittofeed Hosting
- Postgres (Railway Postgres) for application data and Temporal's databases
- ClickHouse for user events and analytics
- Temporal server for journeys, broadcasts and background workflows
Deployment Dependencies
- Dittofeed self-hosting docs: https://docs.dittofeed.com/deployment/self-hosted
- Dittofeed source and releases: https://github.com/dittofeed/dittofeed
- Template source (Dockerfiles, start scripts, changelog): https://github.com/aalfath/dittofeed-railway-template
Implementation Details
- No prompts at deploy: the dashboard PASSWORD, the 32-byte SECRET_KEY and the database passwords are generated. Keep SECRET_KEY unchanged after first use, because it encrypts sessions and stored secrets.
- The health check is GET /api, which answers without login. Temporal and ClickHouse are reachable only on the private network.
- If you add a custom domain, set DASHBOARD_URL and DASHBOARD_API_BASE on the Dittofeed service to https://YOUR-DOMAIN.
- Optional, not set by default: blob storage for attachments (ENABLE_BLOB_STORAGE and BLOB_STORAGE_* variables) and LITE_MEM_LIMIT for the Node heap in MB (default 1024).
- Updates: every service except Postgres builds from the template's GitHub repo. When a new Dittofeed version is pinned there, Railway shows an update notice in your project. Read the repo's CHANGELOG.md before you apply it.
Why Deploy Dittofeed 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 Dittofeed 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.
Template Content