---
title: "Deploy Conductor"
description: "Workflow orchestration engine with UI, password-protected"
category: "Automation"
url: https://railway.com/deploy/conductor
---

# Deploy Conductor

Workflow orchestration engine with UI, password-protected

**[Deploy Conductor on Railway](https://railway.com/template/conductor)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/conductor/manifest.json

- **Creator:** zer0person's Projects
- **Category:** Automation
- **Total deploys:** 1

## Template content

### Conductor

- **Image:** conductoross/conductor:next
- **Start command:** `sh -c "echo 'admin:{PLAIN}'$CONDUCTOR_PASSWORD > /etc/nginx/.htpasswd && sed -i 's#server_name conductor;#server_name conductor; auth_basic Conductor; auth_basic_user_file /etc/nginx/.htpasswd; location = /healthz { auth_basic off; return 200 ok; }#' /etc/nginx/conf.d/default.conf && export SPRING_DATASOURCE_URL='jdbc:sqlite:/data/conductor.db?busy_timeout=15000&journal_mode=WAL' && exec /bin/sh /app/startup.sh"`
- **Public domain:** Yes

## Documentation

# Deploy and Host Conductor on Railway

[Conductor](https://github.com/conductor-oss/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

- [Conductor on GitHub](https://github.com/conductor-oss/conductor)
- [Documentation](https://conductor-oss.org)
- [Docker image](https://hub.docker.com/r/conductoross/conductor)

## 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.


## Similar templates

- [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker.
- [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — Automate WhatsApp workflows with Evolution API, n8n, and Postgres.
- [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage

Open this page in a browser: https://railway.com/deploy/conductor