Windmill v1 Scripts, Flows and Internal Apps

Windmill 1.830.0 is an open-source platform that turns Python, TypeScript, Go, Bash and SQL scripts into flows, generated UIs, internal apps, webhooks and cron jobs. This template deploys the self-hosted stack with a scalable worker pool, a native worker, editor services and Postgres.

What you get

  • Windmill server (API and UI) that runs database migrations on start
  • Default worker group of 3 replicas, adjustable, plus a native worker group for queries and HTTP calls
  • Windmill Extra for editor language servers and the debugger, behind a Caddy proxy that is the only public service
  • PostgreSQL 18 with a volume, which also holds the job queue
  • A one-shot bootstrap job that replaces the default admin password on first boot

Good for

  • Turning scripts into shareable tools with generated input forms
  • Scheduled jobs and data syncs with retries and run history
  • Multi-step flows with branches, approvals and error handlers
  • Internal apps and authenticated webhooks on top of existing databases and APIs

Services in this template

  • Windmill Extra · image ghcr.io/windmill-labs/windmill-extra:1.830.0
  • Windmill · image ghcr.io/windmill-labs/windmill:1.830.0
  • Windmill Native Worker · image ghcr.io/windmill-labs/windmill:1.830.0
  • Admin Bootstrap · from baranberkay96/windmill-railway
  • Postgres · image ghcr.io/railwayapp-templates/postgres-ssl:18
  • Windmill Worker · image ghcr.io/windmill-labs/windmill:1.830.0
  • Proxy · from baranberkay96/windmill-railway

Questions people ask

How do I log in?

Wait until the Admin Bootstrap logs show the password was rotated, then copy WINDMILL_ADMIN_PASSWORD from that service's Variables tab. Open the Proxy's public URL and sign in as admin@windmill.dev. Then add your own superadmin user and change or disable the default one. If the bootstrap job failed, sign in at once with the default password changeme and change it, because the URL is public.

How do I scale workers?

Change the Windmill Worker replica count; each replica runs one job at a time and registers itself on the Workers page. Dependency caches are local, so the first run with new packages on a new replica downloads them again. Past about 10 worker replicas, lower DATABASE_CONNECTIONS or raise Postgres max_connections.

What are the limits on Railway?

Railway has no privileged containers, so nsjail sandboxing is unavailable and per-job PID isolation may fall back to none. Treat everyone who can write scripts as trusted. Enterprise-only parts, Docker-in-Docker and SMTP email triggers are not included.

What licence applies?

The Community Edition images are distributed under Windmill Labs' own terms: free use and redistribution as is, but selling, reselling, offering as a managed service, modifying or wrapping them requires an agreement with Windmill Labs. This template deploys the unmodified images. Check the terms for your use.

How do I upgrade?

Back up the Postgres volume, then set the same new tag on Windmill, Worker, Native Worker and Extra. Migrations run on start and are not designed to be rolled back, so test in a separate environment first.

Full template README

Deploy and Host Windmill with Railway

Windmill is an open-source developer platform that turns Python, TypeScript, Go, Bash and SQL scripts into flows, auto-generated UIs, internal apps, webhooks and cron jobs. This community template runs the full self-hosted stack on Railway: API server, scalable worker pool, native worker, editor services and Postgres.

About Hosting Windmill

A production Windmill install is more than one container. The server serves the UI and REST API and runs database migrations; workers pull jobs from a queue stored in Postgres and execute your code; a native worker handles lightweight queries and HTTP calls in-process; the windmill-extra service provides editor autocompletion and a step-through debugger over websockets. Because Railway gives each service a single public port, a small Caddy proxy sends editor websocket paths to windmill-extra and everything else to the server. Everything except the proxy stays on Railway's private network, all images are pinned to the same Windmill release, and the default admin password is replaced automatically on first boot.

Common Use Cases

  • Turn one-off Python or TypeScript scripts into shareable tools with generated input forms
  • Run scheduled jobs and data syncs (ETL, reports, clean-ups) with retries and run history
  • Chain scripts into multi-step flows with branches, approvals and error handlers
  • Build internal apps and dashboards on top of existing databases and APIs
  • Expose scripts as authenticated webhooks for other systems to call

Dependencies for Windmill Hosting

  • Windmill server and workers (ghcr.io/windmill-labs/windmill:1.830.0)
  • Windmill Extra for the editor's language servers and debugger (ghcr.io/windmill-labs/windmill-extra:1.830.0)
  • PostgreSQL 18 (Railway's postgres-ssl:18), which also holds Windmill's job queue
  • Caddy 2.11 as the public path-routing proxy
  • A one-shot bootstrap job (curl) that replaces the default admin password

Deployment Dependencies

Implementation Details

Service Role Public Scaling
Proxy Caddy; routes /ws/*, /ws_debug/*, /ws_mp/* to Windmill Extra, everything else to Windmill Yes (only public service) 1
Windmill API server and UI (MODE=server), runs migrations on start No 1
Windmill Worker Default worker group: Python, TypeScript, Bash, Go and other jobs No 3 replicas (adjustable)
Windmill Native Worker native worker group, 8 in-process workers for queries and HTTP calls No 1
Windmill Extra Language servers and debugger behind one gateway No 1
Admin Bootstrap One-shot job that replaces the default admin password, then stops No –
Postgres Database and job queue, persistent volume No 1

First login

  1. Wait until all services are deployed and the Admin Bootstrap logs show Password of admin@windmill.dev rotated. The job stopping afterwards is expected.
  2. Copy WINDMILL_ADMIN_PASSWORD from the Admin Bootstrap service's Variables tab.
  3. Open the Proxy service's public URL and sign in as admin@windmill.dev with that password.
  4. In Instance settings, confirm the Base URL, then add your own user as superadmin, sign in with it, and change or disable admin@windmill.dev.
  5. If the bootstrap job failed for any reason, sign in immediately with Windmill's default password changeme and change it, because the URL is public.

Scaling workers

Each default worker replica runs one job at a time. Raise or lower the Windmill Worker replica count in its service settings; new replicas register themselves on Windmill's Workers page. Workers keep their dependency cache on local disk, so the first run of a script with new packages after a redeploy or on a new replica downloads them again. Do not attach a volume at /tmp/windmill/cache: replicas cannot use volumes, and an empty volume would hide runtimes the image pre-installs there. Postgres allows 100 connections by default; past about 10 worker replicas, lower the server's DATABASE_CONNECTIONS or raise Postgres max_connections.

Pinning and upgrading

Windmill, Windmill Worker, Windmill Native Worker and Windmill Extra all use release 1.830.0. To upgrade, back up the Postgres volume, then set the same new tag (see https://github.com/windmill-labs/windmill/releases) on all four services and deploy; the server applies database migrations on start. Database migrations are not designed to be rolled back, so test upgrades in a separate Railway environment first.

Limits on Railway

Railway does not offer privileged containers, so nsjail sandboxing is unavailable and per-job PID isolation may fall back to none (check worker logs). Treat everyone who can write scripts as trusted. Enterprise-only parts of the upstream stack (search indexer, multiplayer) and the Docker-in-Docker and SMTP email-trigger options are not included.

Why Deploy Windmill on Railway?

Railway runs each Windmill component as its own service with private networking, managed Postgres with a persistent volume, and per-service logs and metrics, so the worker pool can grow by changing a replica count instead of editing compose files on a server. You pay for the resources the stack actually uses, and every image tag is pinned so upgrades happen when you choose.

Guides for this template

View Windmill v1 Scripts, Flows and Internal Apps on railway.com

Similar templates

TemplateCategoryDeploymentsDeploys
N8N (w/ workers)
A powerful workflow automation tool for technical people
Automation114,737
n8n
n8n [Nov '26] (Workflows/Integrations/API Automation/AI Coding) Self Host
Automation17,560
Typebot
Build advanced chatbots visually
Automation8,968
n8n
n8n workflow automation on PostgreSQL, webhooks and secrets preconfigured
Automation5,850
n8n with workers
A complete setup for n8n with workers
Automation4,040
N8N (w/ webhook processors)
A powerful workflow automation tool for technical people
Automation3,386