---
title: "Deploy Flowise + Postgres"
description: "Flowise AI agents with Postgres, persistent storage, and auth."
category: "AI/ML"
url: https://railway.com/deploy/flowise-postgres
---

# Deploy Flowise + Postgres

Flowise AI agents with Postgres, persistent storage, and auth.

**[Deploy Flowise + Postgres on Railway](https://railway.com/template/flowise-postgres)**

- **Creator:** leodev
- **Category:** AI/ML
- **Total deploys:** 5

## Template content

### postgres https://devicons.railway.com/i/postgresql.svg

- **Image:** postgres:16-alpine

### flowise https://avatars.githubusercontent.com/u/128289781?s=200&v=4

- **Image:** flowiseai/flowise:latest
- **Health check:** /
- **Public domain:** Yes

## Documentation

# Deploy and Host Flowise + Postgres on Railway

Self-host Flowise for visual AI agents and LLM workflows with Postgres, persistent storage, generated credentials, and private networking.

## About Hosting Flowise + Postgres on Railway

- `flowise`: public Flowise web service
- `postgres`: private Postgres database
- Persistent storage for uploads and credential key material
- Generated auth, session, and credential secrets
- No bundled model provider keys

## Why Deploy Flowise + Postgres on Railway

The published template deploy test created the Flowise app and Postgres database, reached `SUCCESS`, served HTTP `200`, and was cleaned up after validation. It uses Postgres instead of default SQLite so project metadata and workflow state survive redeploys.

Flowise has strong marketplace demand, but many users need a clean persistent database-backed variant rather than a demo setup.

## Common Use Cases

- Visual AI agent builders
- LLM workflow prototypes
- Internal automation demos
- Teams testing Flowise before committing to a longer-term stack

## Dependencies for Flowise + Postgres Hosting

Flowise depends on Postgres for durable app/workflow data, persistent local storage for uploads and credential material, generated auth secrets, and a deployer-provided model provider key.

### Deployment Dependencies

- `DATABASE_URL`: private Postgres connection string
- `FLOWISE_USERNAME`: generated or deployer-provided username
- `FLOWISE_PASSWORD`: generated or deployer-provided password
- `SECRETKEY_PATH`: persistent credential key path
- Model provider keys: deployer-owned, not bundled

## After Deploy

1. Open the Flowise public URL.
2. Sign in with the generated credentials.
3. Add model provider keys inside Flowise or as Railway variables.
4. Keep Flowise as one app instance unless storage and queue mode are redesigned for horizontal scale.

## Support Checklist

If a deploy fails, include `flowise` and `postgres` deployment IDs, public URL behavior, and log lines mentioning Postgres, auth, or credential secret setup.


## 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-postgres