No docker run to remember
Langflow starts from a compose file we write, on a server that stays on.
Langflow 1.12.3 AI
Free credit available Limited time
Langflow hosting Build AI agents in the browser, then call them from yourย app.
Selfhost.dev offers one-click Langflow hosting on a dedicated server we provision, secure and run, with PostgreSQL bundled and your admin login set before Langflow starts. Every flow you build can be served as an API on the same HTTPS address.
No docker run, no .env file and no reverse proxy to configure.
Langflowone-click template ready
- editorLangflow 1.12.3
- databasePostgreSQL, bundled
- sign-inadmin + your password
- APIsame HTTPS address
- modelyour own key
European 8 GB server$0.03/hr
In one line
What is Langflow hosting on Selfhost.dev?
What it is
Langflow is an open source visual builder for AI agents, RAG pipelines and LangChain flows. This template runs it with its own PostgreSQL database on a server of your own.
Where to start. Open the console with Langflow selected
Who it is for
Developers and AI teams who design flows in a browser and call them from an app over HTTPS.
When to use it
When a flow has outgrown localhost:7860 and you would rather not build the server around it.
Server
Langflow self hosted, without the setup
Self hosting Langflow means Docker, a compose file, a reverse proxy for HTTPS, a database other than the default SQLite and a superuser with auto-login off. Here it is all done before your first sign-in.
The stack, end to end
Callers
Your browser and apps
Edge
HTTPS
Your project server
Container
Langflow
Database
PostgreSQL
Calls out to
Your model provider
To sign in
Admin login
| Self hosting Langflow by hand | Langflow hosting on Selfhost.dev |
|---|---|
| Rent a server and install Docker | A dedicated server, set up for you |
| Write a compose file with PostgreSQL | Langflow and PostgreSQL, wired together |
| Set LANGFLOW_AUTO_LOGIN=false and a superuser | Your admin login, created before it starts |
| Put Caddy or Nginx in front for HTTPS | HTTPS on a generated address |
Langflow and its PostgreSQL run side by side on one server. Deploy the stack
Docker
Langflow Docker, with PostgreSQL instead of SQLite
The Langflow Docker quickstart is one docker run line on port 7860, with flows in a SQLite file. Longer guides add PostgreSQL and a superuser. This template is that longer setup, finished.
No SQLite file
Flows and accounts are stored in the bundled PostgreSQL database, not in a file inside the container.
No port 7860 to publish
Langflow answers on its own HTTPS address and its API uses the same one.
What you need
Langflow hosting requirements
The console starts Langflow on an 8 GB server, x86 or ARM, with no hard floor. Langflow and its PostgreSQL share it. You bring a password and a model provider key.
What it needs
- Server
- 8 GB, the console's pick for Langflow; x86 or ARM
- Login
- Username admin unless you change it; a password of 8+ characters
- Model
- An API key from your model provider, added after sign-in
- Domain
- Optional; a generated HTTPS address works first
Server size: 8 GB, enough for Langflow. Deploy on an 8 GB server
Quickstart
Deploy Langflow in 3 steps
Launch, sign in, build a flow.
-
Launch the template
Launch opens the Langflow template. Keep admin as the username or pick another and set a password of 8+ characters. The template deploys in about fifteen minutes.
-
Sign in
Open the HTTPS address the console shows and sign in with that username and password.
-
Build and serve a flow
Add your model provider's API key, start from a template or a blank canvas, then call the flow from your app on the same address.
Deploy LangflowStep 1 starts in the console.
Launch Langflow Billing
Langflow hosting cost
Langflow hosting here is one server billed hourly from prepaid credits, with no fee per flow, run or user. A European 8 GB server is $0.03/hr, around $23 a month.
| Item | Cost |
|---|---|
| The Langflow template | $0 |
| The bundled PostgreSQL | $0, it runs on the same server |
| Bandwidth to your flows | $0, included in the server price |
| Optional daily backups | +20% of the server price |
| Server | RAM, cores, disk | Where | Rate | About a month |
|---|---|---|---|---|
cx33 (recommended) | 8 GB, 4 cores, 80 GB | Europe | $0.03/hr | $23.36 |
cax21 (ARM) | 8 GB, 4 cores, 80 GB | Europe | $0.04/hr | $29.20 |
cx43 (room to grow) | 16 GB, 8 cores, 160 GB | Europe | $0.06/hr | $43.22 |
ccx13 | 8 GB, 2 cores, 80 GB | US | $0.16/hr | $119.28 |
cpx32 | 8 GB, 4 cores, 160 GB | Singapore | $0.19/hr | $135.63 |
Monthly figures assume 730 hours. The US and Singapore servers need a first top-up.
If your balance reaches zero
With a card on file or a past top-up, Langflow runs for 5 more days after your balance reaches zero, then stops. Top up within 24 hours to restart it; after that it is deleted, with a 14-day copy you can restore. Welcome-credit-only servers are deleted at zero.
Price a 16 GB server for heavier flows in the calculator, no signup.
API
Langflow flows, served as an API
Build a flow in the editor and your apps can call it straight away, on the same HTTPS address. There is no second service to host.
Call it from your app
Send a request to the flow's endpoint on your Langflow address and get its output back.
Bring your own model
Add your model provider's API key after you sign in; the flows you build then call that provider with it.
Add a vector store for RAG
Point a retrieval flow at a vector database such as Qdrant, another one-click template here.
Status
Five checks before your first flow
- Every service is health-checked every 60 seconds.
- A stalled deploy is retried automatically, without you starting over.
- Done means the URL answers, not just that a container started.
- No open editor. Auto-login is off, so Langflow asks for a login from the first request.
- You see the release it runs. The console flags Update available when a newer one ships.
~15 min to deploy
The console estimates about fifteen minutes for the Langflow template after the server is ready; first-time server provisioning adds time.
Notes
Langflow hosting limitations
- Sign-ups are open on new deployments. Anyone who reaches your Langflow address can create an account and sign in at once. Deactivate any account you did not create in Langflow's admin page.
- Bring your own model key. No model or API key ships with the template. Your flows call the provider whose key you add. That provider bills you for the calls.
- PostgreSQL shares the server. The bundled database is Langflow's own, not a separate managed database, so it uses the same memory and disk as Langflow.
Nothing here in your way? The template deploys in about fifteen minutes.
Launch Langflow Planning
Running Langflow for a team or a product?
Tell us how many flows you run and how often apps call them. We reply with the server we would pick and its monthly cost.
Help
Frequently asked questions
Is Langflow free?
Yes. Langflow is open source under the MIT license, so the software itself costs nothing. What you pay for is the server it runs on, billed by the hour from prepaid credits as the cost table shows. Your model provider bills separately for the calls your flows make.
Does Langflow hosting come with a model?
No. Langflow builds flows around the models you bring. No model or API key ships with the template. After you sign in, add the API key for your model provider in Langflow. The flows you build then call that provider, which bills you for the usage.
Can Langflow serve a flow as an API?
Yes. Every flow can be served as an API on the same HTTPS address as the editor. Your applications send requests to the address the console shows, so there is no second service to deploy. Build and test the flow in the editor first, then call it from your code.
How do I sign in to Langflow?
Open the HTTPS address the console shows and sign in with the username and password you set at deploy time. The username is admin unless you chose another. The superuser is created before Langflow first starts and auto-login is off, so the editor never opens without a login.
How much RAM does Langflow need?
Guides quote 2 to 4 GB for Langflow on its own. Our console starts it on an 8 GB server, because Langflow and its PostgreSQL database share that machine. For heavier flows, scale up from Project Settings; the console shows the downtime and the new price first.
Can I use my own domain for Langflow?
Yes. Langflow first answers on a generated HTTPS address. Once it is running, open the service's Settings, add one domain you own and create the DNS record shown there. When the record resolves, the editor and the API both answer on your own domain as well.
AI flows, built in your browser. Served from your own server.
- Langflow and PostgreSQL on a server of its own
- Your admin login and HTTPS before the first sign-in
- A European 8 GB server, about $23 a month
About Selfhost.dev
Selfhost.dev is a managed self hosting platform for developers and small teams. Open source apps and databases on dedicated servers you control, billed by the hour, in six locations across three continents.
Best for: Langflow beside the vector database and LLM gateway its flows call, plus managed PostgreSQL, MySQL and Redis.