---
title: "Deploy Dagster"
description: "Dagster data orchestrator: webserver, daemon, code server, Postgres, S3"
category: "Automation"
url: https://railway.com/deploy/dagster-1
---

# Deploy Dagster

Dagster data orchestrator: webserver, daemon, code server, Postgres, S3

**[Deploy Dagster on Railway](https://railway.com/template/dagster-1)**

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

- **Creator:** Agaz Self-Host
- **Category:** Automation
- **Total deploys:** 2

## Template content

### dagster-daemon https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/png/dagster.png

- **Source:** https://github.com/aalfath/dagster-railway-template
- **Health check:** /healthz

### dagster-code https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/png/dagster.png

- **Source:** https://github.com/aalfath/dagster-railway-template
- **Health check:** /healthz

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18

### dagster-webserver https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/png/dagster.png

- **Source:** https://github.com/aalfath/dagster-railway-template
- **Health check:** /healthz
- **Public domain:** Yes

## Buckets

- **dagster-storage**

## Documentation

# Deploy and Host Dagster on Railway

Dagster is an open-source (Apache-2.0) data orchestrator for building, scheduling and observing data pipelines. You define assets (tables, files, models) in Python, and Dagster runs them, tracks their lineage and materialization history, and runs schedules and sensors. This template deploys Dagster 1.13.30.

## About Hosting Dagster

A production Dagster deployment is several cooperating processes. This template runs them as separate Railway services, in the layout Dagster's docs recommend. **dagster-webserver** serves the UI and GraphQL API on the public domain, behind a basic-auth login, because Dagster OSS has none. **dagster-daemon** runs schedules, sensors, automation, the run queue and run monitoring. **dagster-code** is the gRPC code server that loads your definitions and executes runs. A Railway **PostgreSQL** database stores runs, events and schedules, and a Railway **Bucket** stores the captured step logs. The services find each other over the private network and start in dependency order. The webserver applies schema migrations on every start.

## Common Use Cases

* Scheduling and monitoring ELT jobs, dbt projects and warehouse refreshes
* Building a catalog of data assets with lineage, checks and run history
* Running Python data and ML pipelines on a schedule or from sensors

## Dependencies for Dagster Hosting

* PostgreSQL (Railway PostgreSQL) for runs, event logs, schedules and the asset catalog
* S3-compatible object storage (Railway Bucket) for captured step stdout/stderr

### Deployment Dependencies

* Dagster: https://github.com/dagster-io/dagster (release 1.13.30)
* Official image: https://hub.docker.com/r/dagster/dagster-k8s (pinned `1.13.30@sha256:97501f44…`)
* Dagster deployment docs: https://docs.dagster.io/deployment/oss
* Template repo: https://github.com/aalfath/dagster-railway-template

### Implementation Details

**After deploy:** open the `dagster-webserver` domain and log in as `admin` with the password in the webserver's `DAGSTER_PASSWORD` variable (generated at deploy). An example code location `railway` is loaded, with two assets, an asset check, a job and an hourly schedule that starts stopped. Click **Materialize all** to run it.

**Services:**

* `dagster-webserver`: UI and GraphQL API, Caddy basic auth, health check `/healthz`
* `dagster-daemon`: schedules, sensors, run queue (`DAGSTER_MAX_CONCURRENT_RUNS`, default 4), run monitoring
* `dagster-code`: gRPC code server on port 4000 (private), runs execute here; volume `/data` holds asset values
* `Postgres`: Dagster storage, on a volume
* `dagster-storage`: bucket for step logs, viewable in the UI

**Your own code:** fork the template repo, put your package under `code/project/` and extra packages in `code/requirements.txt`, point the `dagster-code` service's source at your fork, and set `DAGSTER_MODULE` (for example `my_project.definitions`).

**Updates:** every service builds from the template repo, so Railway shows an "update available" notice when we release a new Dagster version. Read the repo's CHANGELOG.md before you apply it.

## Why Deploy Dagster 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 Dagster 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.



## 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/dagster-1
