Deploy Conductor
Netflix-born workflow engine: server, UI, Postgres, Elasticsearch and Redis
Just deployed
/var/lib/postgresql/data
Elasticsearch
Just deployed
/usr/share/elasticsearch/data
Conductor
Just deployed
/app/data
Redis
Just deployed
/data
Deploy and Host Conductor on Railway
Conductor is an open-source durable workflow and agent orchestration engine that started at Netflix and is now maintained as Conductor OSS. You define workflows as JSON (or in code), run workers in any language, and Conductor handles state, retries, timeouts, scheduling and history, with a web UI to start, search and debug executions.
About Hosting Conductor
Conductor needs a server plus its storage: a database for workflow state and queues, a search index for the execution search pages, and a lock service. This template runs Conductor 3.34.0 (server and UI) with Railway Postgres, Railway Redis and Elasticsearch 8, wired over the private network, each with its own volume. Passwords are generated, so the deploy form asks for nothing. Conductor has no user accounts of its own, so the public URL is protected with HTTP basic auth. The first start takes a few minutes while Conductor creates its tables and indices. Updates arrive as Railway update notices when the template repo bumps the version.
Common Use Cases
- Orchestrate microservices and background jobs with retries, timeouts and full execution history
- Run AI agent and LLM workflows, human-in-the-loop approvals and scheduled pipelines
- Replace hand-written job queues and cron scripts with workflows you can inspect and rerun
Dependencies for Conductor Hosting
- Conductor: the Conductor server (REST and gRPC API on private port 8080) and the Conductor UI, behind nginx with basic auth on the public domain. Volume at
/app/datafor files uploaded through Conductor's file storage API - Postgres (Railway): workflow and task state, metadata, queues, the scheduler and large payloads
- Elasticsearch 8.19 (built from the template repo): search index for workflow and task executions, security on, private only
- Redis (Railway): distributed workflow execution lock
Deployment Dependencies
- Conductor OSS on GitHub and release v3.34.0
- Conductor documentation
- Template repo with the Dockerfiles and changelog
Implementation Details
After deploy, open the Conductor service's public URL and sign in as admin with the CONDUCTOR_PASSWORD from the Conductor service's Variables tab. Point workers and SDK clients at https://YOUR-DOMAIN/api with the same basic-auth login, or, from services in the same Railway project, at http://conductor.railway.internal:8080/api (private network, no auth). Optional settings go on the Conductor service: JAVA_OPTS for the heap (default -Xms256m -Xmx1g), CONDUCTOR_LOAD_SAMPLE=true for upstream's sample workflow, and AI provider keys such as OPENAI_API_KEY or ANTHROPIC_API_KEY for Conductor's LLM tasks.
Conductor and Elasticsearch build from the template's GitHub repo with pinned image digests. When a new version is merged, Railway shows an update notice in your project; read the repo's CHANGELOG before you apply it.
Why Deploy Conductor 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 Conductor 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
Elasticsearch
aalfath/conductor-railway-templateConductor
aalfath/conductor-railway-templateRedis
redis:8.2