[{"data":1,"prerenderedAt":117},["ShallowReactive",2],{"seo-verification":3,"blog-heberger-langflow-vps-en":6},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"id":7,"slug":8,"title":9,"excerpt":10,"readTime":11,"views":12,"isPinned":13,"publishedAt":14,"category":15,"categories":21,"featuredImage":23,"bgImage":24,"posterImage":25,"relatedSolution":26,"intro":28,"sections":29,"ctaTitle":72,"ctaBody":73,"ctaButton":74,"ctaUrl":75,"relatedPosts":76},10,"heberger-langflow-vps","How to Host LangFlow on a VPS","Install LangFlow on your VPS to prototype LangChain pipelines visually. Docker, Postgres database, reverse proxy and SSL step by step.",8,570,false,"2026-06-10T00:00:00+00:00",{"id":16,"name":17,"slug":18,"color":19,"icon":20},1,"Artificial Intelligence","intelligence-artificielle","bg-purple-500\u002F10 text-purple-400","ia",[22],{"id":16,"name":17,"slug":18,"color":19,"icon":20},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fheberger-langflow-vps-poster.svg",{"categorySlug":20,"appSlug":27},"langflow","LangFlow is a visual editor for LangChain flows focused on rapid prototyping and Python export. Self-hosted on a VPS, it becomes your private workshop to design, test and then industrialize AI pipelines, with a persistent database and secure access. Here is how to install it properly.",[30,34,44,47,69],{"type":31,"title":32,"body":33},"h2","Why self-host LangFlow on a VPS","LangFlow is aimed at developers who want to iterate quickly on LangChain graphs before freezing them into code. On a VPS, you gain a stable and persistent environment, whereas a local instance on your machine is lost on every restart and cannot be shared with the team. Your flows, your global variables (including API keys) and the execution history live in a PostgreSQL database that you control. You can expose each flow as an API, plug in custom components, and collaborate with several people on the same instance. Above all, your prompt chains and the business logic they encode never pass through any third-party platform.",{"type":35,"title":36,"items":37},"ul","The concrete benefits of a self-hosted LangFlow",[38,39,40,41,42,43],"Persistent instance shared by the team, unlike an ephemeral local setup.","Flows and global variables stored in your own PostgreSQL, backed up at will.","Custom Python components deployable directly on the server.","Each flow exposable as an API endpoint for integration into your applications.","Version freedom: you pin the release that matches your existing flows.","No API key or prompt logic exposed to an external SaaS.",{"type":31,"title":45,"body":46},"Hardware and software requirements","LangFlow is more demanding than average: its interface and its execution engine require memory. Plan for at least 2 vCPU and 4 GB of RAM, and ideally 4 vCPU \u002F 6 to 8 GB for comfortable use with several flows loaded. Add a PostgreSQL database (in a neighboring container) for production: the default SQLite database is fine for testing but quickly shows its limits. Count on 10 GB of disk. Docker and Docker Compose are needed, plus a subdomain (e.g. langflow.your-domain.com) and port 443 open.",{"type":48,"title":49,"steps":50},"steps","Deploy LangFlow with Docker, Postgres and HTTPS",[51,54,57,60,63,66],{"title":52,"body":53},"Prepare the project","Over SSH: `mkdir -p \u002Fopt\u002Flangflow && cd \u002Fopt\u002Flangflow`. There you will place the `docker-compose.yml` describing two services: `langflow` and `postgres`.",{"title":55,"body":56},"Define LangFlow and PostgreSQL","Use the `langflowai\u002Flangflow` image, expose the internal port `7860`, and point `LANGFLOW_DATABASE_URL` to the Postgres service (`postgresql:\u002F\u002Flangflow:motdepasse@postgres:5432\u002Flangflow`). Add a volume for the Postgres data.",{"title":58,"body":59},"Enable authentication","Before the first launch, set `LANGFLOW_AUTO_LOGIN=false`, `LANGFLOW_SUPERUSER` and `LANGFLOW_SUPERUSER_PASSWORD` in the environment. Without this, the instance would be open to anyone who knows the URL.",{"title":61,"body":62},"Launch the stack","Run `docker compose up -d` then monitor `docker compose logs -f langflow`. The first initialization creates the schema in the database and can take a minute.",{"title":64,"body":65},"Configure the reverse proxy and SSL","Route `langflow.your-domain.com` to `localhost:7860` via Caddy or Nginx, with an automatic Let's Encrypt certificate. Enable WebSocket support on the proxy side, indispensable for the real-time canvas to work properly.",{"title":67,"body":68},"Test a flow and its API","Log in, build a minimal flow, add your API keys in the global variables, then retrieve the call code via the flow's API button to validate external integration.",{"type":70,"body":71},"tip","Never leave LangFlow in production with SQLite: the database corrupts under concurrent load and you lose your flows. Migrate to PostgreSQL from the start and back up regularly with `pg_dump`. Also remember to export your flows as JSON (Export menu) as a versionable safety net in Git, independent of the database state.","Prototype your AI pipelines on a ServOrbit Cloud VPS","With a ServOrbit Cloud VPS and its ready-to-use Docker environment, deploy LangFlow and its PostgreSQL database in a few commands. Scale up resources when your flows become heavier.","Set up my Cloud VPS","\u002Fvps-cloud",[77,90,104],{"id":16,"slug":78,"title":79,"excerpt":80,"readTime":81,"views":82,"isPinned":13,"publishedAt":83,"category":84,"categories":85,"featuredImage":23,"bgImage":24,"posterImage":87,"relatedSolution":88},"heberger-open-webui","How to Host Open WebUI on a VPS","A complete guide to deploying Open WebUI on your own VPS. Keep control of your data, avoid cloud API costs, and access your LLMs from a clean web interface.",6,3200,"2026-06-01T00:00:00+00:00",{"id":16,"name":17,"slug":18,"color":19,"icon":20},[86],{"id":16,"name":17,"slug":18,"color":19,"icon":20},"\u002Fblog\u002Fcovers\u002Fheberger-open-webui-poster.svg",{"categorySlug":20,"appSlug":89},"open-webui",{"id":91,"slug":92,"title":93,"excerpt":94,"readTime":95,"views":96,"isPinned":13,"publishedAt":97,"category":98,"categories":99,"featuredImage":23,"bgImage":24,"posterImage":101,"relatedSolution":102},2,"deployer-dify-vps","Deploying Dify on a VPS: AI Workflows Under Control","Install Dify on a ServOrbit VPS to build agents, chatflows and AI apps without losing control of your data.",7,2480,"2026-02-11T00:00:00+00:00",{"id":16,"name":17,"slug":18,"color":19,"icon":20},[100],{"id":16,"name":17,"slug":18,"color":19,"icon":20},"\u002Fblog\u002Fcovers\u002Fdeployer-dify-vps-poster.svg",{"categorySlug":20,"appSlug":103},"dify",{"id":81,"slug":105,"title":106,"excerpt":107,"readTime":108,"views":109,"isPinned":13,"publishedAt":110,"category":111,"categories":112,"featuredImage":23,"bgImage":24,"posterImage":114,"relatedSolution":115},"openclaw-vps","Deploying OpenClaw on a VPS","A guide to deploying OpenClaw on your own VPS. Keep control of your AI agents and your data within your own infrastructure.",5,422,"2026-06-11T00:00:00+00:00",{"id":16,"name":17,"slug":18,"color":19,"icon":20},[113],{"id":16,"name":17,"slug":18,"color":19,"icon":20},"\u002Fblog\u002Fcovers\u002Fopenclaw-vps-poster.svg",{"categorySlug":20,"appSlug":116},"openclaw",1785628439604]