---
title: "Deploy Langflow"
description: "Visual builder for LangChain AI workflows: Langflow + Postgres, with auth."
category: "Other"
url: https://railway.com/deploy/langflow-113
---

# Deploy Langflow

Visual builder for LangChain AI workflows: Langflow + Postgres, with auth.

**[Deploy Langflow on Railway](https://railway.com/template/langflow-113)**

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

- **Creator:** Tasha
- **Category:** Other
- **Total deploys:** 1

## Template content

### Langflow

- **Image:** langflowai/langflow:1.13.2
- **Start command:** `python -m langflow run --host 0.0.0.0`
- **Health check:** /health_check
- **Public domain:** Yes

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

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

## Documentation

# Deploy and Host Langflow on Railway

[Langflow](https://www.langflow.org) is an open-source, visual builder for AI and agent workflows. You wire up prompts, models, retrievers, and tools on a drag-and-drop canvas, then expose any flow as an API. This template runs Langflow with a PostgreSQL database so your flows, components, and users persist.

## About Hosting Langflow

Hosting Langflow means running its web application and connecting it to a database. On SQLite (the default) everything lives in a single file on the local disk, which is wiped on every redeploy — so a production deployment needs an external Postgres and persistent storage for uploaded files and custom components. Langflow also ships with open "auto login" by default, meaning anyone with the URL can edit your flows. This template wires Postgres for persistence, puts uploaded files and cache on a volume, and turns on real authentication with an admin account created for you.

## Why Deploy Langflow on Railway?

Railway provisions Langflow and its Postgres database, the private networking between them, and the volume from this single template in one click. Compared with other Langflow templates, this one fixes what makes them unreliable:

- **Pinned, stable version.** Many templates run `langflow:latest`, which pulls breaking changes unpredictably — a common reason a once-working deploy suddenly fails. This one pins a known-good release.
- **Login is on by default.** `LANGFLOW_AUTO_LOGIN` is false and an admin is created from `LANGFLOW_SUPERUSER` / `LANGFLOW_SUPERUSER_PASSWORD`, so your instance is not open to the world.
- **Nothing is lost.** Flows and users persist in Postgres; uploaded files, components, and cache persist on a volume at `/app/langflow`.

## Common Use Cases

- Prototyping and hosting RAG, chatbot, and agent workflows visually
- Exposing a designed flow as an API endpoint for an app
- A shared team workspace for building and testing LLM pipelines

## Dependencies for Langflow Hosting

- A PostgreSQL database (included in this template)
- A persistent volume for uploaded files and cache (included)

### Deployment Dependencies

- [Langflow documentation](https://docs.langflow.org)
- [Langflow configuration](https://docs.langflow.org/environment-variables)

### Implementation Details

On first login, use the `LANGFLOW_SUPERUSER` value (default admin@example.com) and copy `LANGFLOW_SUPERUSER_PASSWORD` from the Langflow service's Variables tab; change them afterwards. Flows and users are stored in the bundled Postgres over the private network; uploaded files, components, and cache live under `/app/langflow` on the attached volume. The service runs as root (`RAILWAY_RUN_UID=0`) so it can write to that volume.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/langflow-113
