Deploy and Host Flowise on Railway

Flowise is an open-source visual builder for AI agents, chatbots and LLM workflows. You connect nodes on a canvas (models, prompts, tools, memory, document loaders, vector stores), test the result in the built-in chat, and call every flow over a REST API or an embeddable chat widget. It works with OpenAI, Anthropic, Google, Mistral, Ollama, OpenRouter and many other providers.

About Hosting Flowise

This template deploys the latest official Flowise image with Railway Postgres and a volume. Flowise 3 no longer uses FLOWISE_USERNAME/FLOWISE_PASSWORD: on a fresh install, whoever opens the URL first can create the owner account. This template closes that gap:

No open first-run setup. The owner account is created from FLOWISE_ADMIN_EMAIL and a generated FLOWISE_ADMIN_PASSWORD before Flowise opens its public port. Sign-up attempts after that are refused. If the account can't be created, the service stops instead of starting unprotected.
No default password. The owner password is generated per deploy and shown in the flowise service's Variables tab.
Postgres, not SQLite. Flows, users, API keys, chat history and document store metadata live in Railway Postgres over the private network.
Credentials survive redeploys. FLOWISE_SECRETKEY_OVERWRITE (the key that encrypts the API keys you save in Flowise) and the login token secrets are generated variables, so redeploys don't log users out or make saved credentials unreadable.
Files on a volume. Uploads, document store files and logs go to a Railway volume at /home/node/.flowise.
Healthcheck. Railway waits for /api/v1/ping before sending traffic to a new deployment.

Getting started

Deploy. Optionally change FLOWISE_ADMIN_EMAIL first; it is your login name.
Wait for the flowise service to turn green. The first boot takes a few minutes because Flowise starts twice: once on a private port to create the owner account, then normally.
Open the flowise service's public URL and log in with FLOWISE_ADMIN_EMAIL and the FLOWISE_ADMIN_PASSWORD value from the Variables tab.
Open Credentials and add your model provider key (for example an OpenAI API key).
Create a Chatflow or Agentflow, or start from one in Marketplaces, and test it in the chat panel.
To call a flow from your app, create a key under API Keys, assign it to the flow, and send POST /api/v1/prediction/FLOW_ID with Authorization: Bearer YOUR_API_KEY.

Common Use Cases

Customer-support and internal chatbots that answer from your own documents (RAG)
AI agents with tools, MCP servers and human-in-the-loop steps, served as an API
Embeddable chat widgets for websites
Prototyping prompts and multi-step LLM pipelines with a team

Dependencies for Flowise Hosting

flowiseai/flowise:latest (official Flowise image)
Railway Postgres 18 (ghcr.io/railwayapp-templates/postgres-ssl:18) with a volume
A Railway volume at /home/node/.flowise for uploads, document store files and logs

Deployment Dependencies

Implementation Details

Key variables on the flowise service:

Variable	Value	Why
`FLOWISE_ADMIN_EMAIL`	`admin@example.com`	Login email of the owner account created on first boot
`FLOWISE_ADMIN_PASSWORD`	generated	Owner password, unique to each deploy
`FLOWISE_SECRETKEY_OVERWRITE`	generated	Encrypts saved credentials; never change it after the first deploy
`JWT_AUTH_TOKEN_SECRET`, `JWT_REFRESH_TOKEN_SECRET`, `EXPRESS_SESSION_SECRET`, `TOKEN_HASH_SECRET`	generated	Login, session and token signing secrets that stay the same across redeploys
`DATABASE_TYPE`, `DATABASE_HOST`, ...	`postgres`, `${{Postgres.PGHOST}}`, ...	Private-network Postgres connection
`BLOB_STORAGE_PATH`, `LOG_PATH`, `SECRETKEY_PATH`	under `/home/node/.flowise`	Files on the volume
`APP_URL`	`https://${{RAILWAY_PUBLIC_DOMAIN}}`	Links Flowise generates point at your domain
`RAILWAY_RUN_UID`	`0`	Lets the start command give the volume to the image's `node` user; Flowise itself runs as `node`

The service's start command is a short Node script that creates the owner account on a loopback-only port when the database has no account yet, then starts Flowise normally. FLOWISE_ADMIN_EMAIL and FLOWISE_ADMIN_PASSWORD are only read at that point: editing them later does not change an existing login. Change the password from Flowise's account settings instead. Password-reset emails need Flowise's SMTP variables (SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, SENDER_EMAIL).

A flow's prediction endpoint answers anyone who knows the flow ID until you assign an API key to that flow. Assign one before you share or embed it.

The image tracks latest, so every new deploy starts on the current Flowise release. To upgrade an existing install, redeploy the flowise service; database migrations run on boot. To hold a version, set the image to a specific tag. Flowise uses about 600 to 800 MB of memory at idle. The service runs as a single replica because the volume can only be attached to one.

Why Deploy Flowise 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 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.