Deploy and Host Conductor on Railway

Conductor is an open source workflow orchestration engine: define long-running workflows as JSON, run workers in any language, and watch executions in a web UI.

About Hosting Conductor

This template runs the official conductoross/conductor:next image (server plus UI) with its built-in SQLite storage on a persistent volume at /data, so no separate database is needed. Conductor itself has no authentication, so the template puts HTTP basic auth in front of the whole site (UI and /api): the username is admin and the password is the generated CONDUCTOR_PASSWORD variable on the service. Open the public URL, sign in, and the Conductor UI appears. Workers and SDK clients reach the API at https:///api with the same basic-auth credentials.

Common Use Cases

Orchestrate microservices and background jobs with retries and timeouts
Build human-in-the-loop and approval workflows
Run scheduled and event-driven pipelines with full execution history

Dependencies for Conductor Hosting

One service with a volume; SQLite is used, so no Redis or Elasticsearch

Deployment Dependencies

Why Deploy Conductor on Railway?

Railway gives you a public HTTPS URL, a persistent volume and automatic restarts with no server to maintain. The SQLite setup suits evaluation and small workloads; for heavy production use, connect Conductor to PostgreSQL or Redis.