Deploy Dittofeed with workers and blob storage

Deploy and host Dittofeed, the messaging Automation for All.

Deploy Dittofeed with workers and blob storage

storage-check

curlimages/curl

Just deployed

/var/lib/postgresql/data

Just deployed

/data

Just deployed

Just deployed

Just deployed

/var/lib/clickhouse

Just deployed

Just deployed

Deploy and Host Dittofeed with workers and blob storage on Railway

Self-host Dittofeed customer-engagement automation with a dashboard, workers and persistent S3-compatible storage.

About Hosting Dittofeed with workers and blob storage

This template includes Dittofeed Lite, a separate worker, bootstrap CLI, PostgreSQL, ClickHouse, Temporal, SeaweedFS and a one-shot storage readiness check. Application images are pinned to the container digests validated for this repair.

Open the generated dashboard domain. Read the generated PASSWORD in the dittofeed-lite service variables and use it for single-tenant login. The session signing key is generated per deployment and shared consistently with the worker and bootstrap service. Configure your own email/SMS providers before sending campaigns.

First deployment: required steps

  1. Deploy and allow the databases, Temporal and application bootstrap to initialize.
  2. Open the generated domain on dittofeed-lite. Read its generated PASSWORD in Railway service variables and use it for single-tenant login. There is no shared default password or signup step.
  3. In the dashboard, obtain the workspace ingestion credentials, connect your application and verify a sample event.
  4. Add your own delivery-provider credentials and test a small campaign before enabling real email/SMS delivery. No provider account or delivery credit is bundled.

Already configured and expected service states

No MinIO console, manual bucket creation, mc command, custom domain or manual infrastructure-secret generation is needed. SeaweedFS creates the configured bucket. Keep the generated PASSWORD, SECRET_KEY and storage references consistent across the application services.

storage-check and dittofeed-admin-cli are one-shot jobs. A successful exit after “S3 bucket ready” or “Admin bootstrap finished.” is expected; they do not need to stay running. The dashboard, worker, Temporal, databases and storage are long-running services. Check logs and exit status before treating a stopped one-shot job as a failure.

Custom domains, retention, backups and additional integrations remain your configuration choices. When changing the dashboard origin, review the application URL variables and secure-cookie settings together.

Why Deploy Dittofeed with workers and blob storage on Railway

Provision the connected services and generated credentials in one deployment, with persistent storage and private service references configured for you. RailGenius maintains this community template; it is not an official upstream-hosted service.

Clean installations passed dashboard login, wrong-password rejection, authenticated event ingestion/querying, invalid ingestion-key rejection, and application attachment storage/retrieval. An application-uploaded file survived storage-container replacement. Bootstrap and worker services started successfully. External campaign delivery was not exercised.

Common Use Cases

  • Customer-event ingestion and audience exploration.
  • Journeys and engagement workflows using your configured delivery providers.
  • Event attachments stored in the included S3-compatible bucket.

Dependencies for Dittofeed with workers and blob storage

PostgreSQL, ClickHouse and Temporal use private networking. The dashboard and authenticated S3 endpoint are public. The storage-check service performs an authenticated bucket check and exits; it does not remain running. Configuration logging is disabled to reduce credential exposure.

Deployment Dependencies

  • A Railway account with sufficient resources for the application, databases, workers and volumes.
  • Generated Railway domains for the public endpoints; no custom domain is required for initial setup.
  • Your own credentials for optional third-party integrations or delivery providers.
  • Upstream project documentation and license: Dittofeed source and upstream documentation.

Storage, backups and existing installations

New installations use persistent SeaweedFS S3 storage instead of unavailable MinIO images. Keep its complete /data volume, database backups and application encryption/session keys in your recovery plan.

This template update applies to new installations. Existing projects are not automatically upgraded. MinIO files cannot be mounted directly into SeaweedFS: existing deployments need a separate authenticated S3 export/copy, verification and rollback plan. Preserve existing encryption keys when retaining a database.

Costs and retention

Usage depends on application/worker activity, database memory and CPU, persistent volumes, uploads and retained data. Configure retention and backups for your workload. Your deployed services and volumes incur Railway usage, including while idle.

Storage repair and clean-install validation: 1 November 2026.


Template Content

More templates in this category

View Template
N8N Main + Worker
Deploy and Host N8N with Inactive worker.

jakemerson
121
View Template
Evolution API with n8n
Automate WhatsApp workflows with Evolution API, n8n, and Postgres.

codestorm
113
View Template
Postgres Backup
Cron-based PostgreSQL backup to bucket storage

Railway Templates
866