--- title: "Deploy Flowise with Workers" description: "[Jul'26] Flowise with workers, Redis, Postgres & persistent storage. 🚀" category: "AI/ML" url: https://railway.com/deploy/flowise-with-workers --- # Deploy Flowise with Workers [Jul'26] Flowise with workers, Redis, Postgres & persistent storage. 🚀 **[Deploy Flowise with Workers on Railway](https://railway.com/template/flowise-with-workers)** - **Creator:** codestorm - **Category:** AI/ML ## Template content ### flowise-web https://i.imgur.com/PCQwxlP.png - **Image:** flowiseai/flowise - **Public domain:** Yes ### Redis https://cdn.sanity.io/images/sy1jschh/production/0ce0bfdcfbdbf69662b1116671f97c2dd788b655-157x157.svg - **Image:** redis:8.2.1 - **Start command:** `/bin/sh -c "rm -rf $RAILWAY_VOLUME_MOUNT_PATH/lost+found/ && exec docker-entrypoint.sh redis-server --requirepass $REDIS_PASSWORD --save 60 1 --dir $RAILWAY_VOLUME_MOUNT_PATH"` ### flowise-worker https://i.imgur.com/PCQwxlP.png - **Image:** flowiseai/flowise-worker ### Postgres https://devicons.railway.app/i/postgresql.svg - **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18 ## Documentation ![Railway](https://img.shields.io/badge/Railway-Supported-blue?logo=railway) # Deploy and Host Flowise with Workers on Railway Flowise with Workers is an advanced, production-style deployment for building AI agents, chatbots, RAG pipelines, and LLM workflows with a visual web UI. This template combines Flowise Web, Flowise Worker, Redis, PostgreSQL, and persistent storage so workloads can be processed through a queue-based architecture. ![](https://i.imgur.com/hbOkfpX.png) ## About Hosting Flowise with Workers Deploying Flowise with Workers on Railway provides a scalable Flowise setup using multiple services. Flowise Web runs the browser-based UI on port `3000`, while Flowise Worker processes queued jobs in the background. Redis acts as the queue and message broker between the Web and Worker services, and PostgreSQL stores Flowise database records. A Railway Volume is mounted on the Flowise Web service at `/root/.flowise` to persist local Flowise files, API key files, secret files, logs, and blob storage across restarts and redeployments. > **Note** > This is an advanced Flowise template. It runs multiple Railway services and may cost more than a basic single-service Flowise deployment. ## Common Use Cases * Running Flowise with background workers for queue-based job processing * Building AI agents, chatbots, and LLM workflows with a visual web UI * Prototyping and hosting RAG pipelines with document loaders, embeddings, and vector stores * Running a more durable Flowise setup with PostgreSQL-backed database storage * Scaling AI workflow execution by separating the Web UI from background worker processing ## Dependencies for Flowise with Workers Hosting * Flowise Web service using the official Flowise Docker image * Flowise Worker service using the official Flowise Worker Docker image * Railway Redis service for queue-based job processing * Railway PostgreSQL service for database-backed Flowise data * Railway Volume mounted on Flowise Web at `/root/.flowise` * Public HTTP access through Railway on port `3000` * Default dashboard credentials using `admin` and `admin123` ### Deployment Dependencies * Flowise GitHub repository: [https://github.com/FlowiseAI/Flowise](https://github.com/FlowiseAI/Flowise) * Official Flowise Docker image: [https://hub.docker.com/r/flowiseai/flowise](https://hub.docker.com/r/flowiseai/flowise) * Official Flowise Worker Docker image: [https://hub.docker.com/r/flowiseai/flowise-worker](https://hub.docker.com/r/flowiseai/flowise-worker) * Flowise documentation: [https://docs.flowiseai.com](https://docs.flowiseai.com) * Flowise queue mode documentation: [https://docs.flowiseai.com/configuration/running-flowise-using-queue](https://docs.flowiseai.com/configuration/running-flowise-using-queue) * Flowise production guide: [https://docs.flowiseai.com/configuration/running-in-production](https://docs.flowiseai.com/configuration/running-in-production) * Railway PostgreSQL: [https://docs.railway.com/guides/postgresql](https://docs.railway.com/guides/postgresql) * Railway Redis: [https://docs.railway.com/guides/redis](https://docs.railway.com/guides/redis) * Railway Public Networking: [https://docs.railway.com/networking/public-networking](https://docs.railway.com/networking/public-networking) * Railway Volumes: [https://docs.railway.com/reference/volumes](https://docs.railway.com/reference/volumes) * Railway CLI: [https://docs.railway.com/guides/cli](https://docs.railway.com/guides/cli) * Railway SSH guide: [https://docs.railway.com/guides/ssh](https://docs.railway.com/guides/ssh) ### Default Credentials This template includes default Flowise dashboard credentials so users can deploy quickly: ```text Username: admin Password: admin123 ``` Users can change the default username and password from Railway Variables before or after deployment. For public deployments, it is recommended to replace the default password with a stronger value before sharing the Flowise URL. ### Architecture This template uses a queue-based Flowise architecture: ```text Browser | v Flowise Web UI :3000 | v Redis Queue | v Flowise Worker | v PostgreSQL ``` Flowise Web provides the public web UI and API. Redis handles queue communication between Flowise Web and Flowise Worker. Flowise Worker processes background jobs from the queue. PostgreSQL stores Flowise database records, while persistent storage keeps local Flowise files available across restarts and redeployments. ### Public Web Access Flowise Web provides the browser-based UI. After deployment, expose the Flowise Web service using Railway Public Networking and open the generated Railway domain or your custom domain in a browser. Recommended public port: ```text 3000 ``` Once the Railway domain is active, visit the public URL in your browser and log in using the configured Flowise username and password. The default credentials are `admin` and `admin123`, unless changed in Railway Variables. ### Persistent Storage This template uses persistent storage across the main stateful services: * Flowise Web mounts a Railway Volume at `/root/.flowise` for local Flowise files, API key files, secret files, logs, and blob storage. * PostgreSQL uses its default persistent data path at `/var/lib/postgresql/data`. * Redis uses its default persistent data path at `/data`. * Flowise Worker is stateless and does not require a volume. The Worker service processes queued jobs from Redis and uses the same PostgreSQL database as the Web service. For workloads that require shared uploaded files between Web and Worker, use external object storage. ### SSH Usage SSH is optional and mainly useful for diagnostics. Most users should access Flowise through the public web UI instead. #### Prerequisites Ensure you have the necessary setup in place: * The Railway CLI installed on your local machine * Logged in with your Railway account using: ```bash railway login ``` #### Usage You can copy the exact SSH command directly from the Railway dashboard: 1. Navigate to your project in the Railway dashboard. 2. Right-click on the Flowise Web or Flowise Worker service you want to inspect. 3. Select **Copy SSH Command** from the dropdown menu. 4. Paste the command into your local terminal to connect to the running container. Once connected, you can inspect files, review logs, check mounted storage, verify environment variables, test Redis or PostgreSQL connectivity, or debug the running service. ### Implementation Details This template deploys Flowise as a multi-service Railway stack: ```text Flowise Web + Flowise Worker + Redis + PostgreSQL + Persistent Storage ``` Flowise Web runs the public dashboard and API. Flowise Worker runs separately and processes jobs from Redis. Both Flowise services use the same PostgreSQL database and the same encryption secret so credentials and stored data remain consistent across the stack. The Flowise Web service should be exposed publicly on port `3000`. The Flowise Worker service should remain private and does not need a public domain. Redis and PostgreSQL are internal supporting services used by Flowise Web and Flowise Worker. This template includes default dashboard credentials so users can deploy quickly: ```text Username: admin Password: admin123 ``` Users can change both values by editing Railway Variables before deployment or after the services are running. ## Why Deploy Flowise with Workers 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 Flowise with Workers 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 - [Chat Chat](https://railway.com/deploy/-WWW5r) — Chat Chat, your own unified chat and search to AI platform. - [stella](https://railway.com/deploy/stella) — Self-host stella with web, API, Postgres, Redis, and object storage. - [Hermes Agent | OpenClaw Alternative with Dashboard](https://railway.com/deploy/hermes-agent-or-openclaw-alternative-wit) — Self-Hosted Hermes AI Agent for Telegram, Discord & Slack Open this page in a browser: https://railway.com/deploy/flowise-with-workers