Summary
Langflow is an open-source, Python-based framework for building AI agents and retrieval applications by wiring components together in a visual editor. Flows built in it become services you host and serve yourself, and every component can be extended with custom Python.
- From
- Free
- Free tier
- YesThe whole product is free open-source software with no paid tier: Docker and pip installs require no account or payment, and no feature is metered. The macOS desktop build is the one gated route, requiring a contact form before download. Inference is not included, so you pay your own model provider.
What it does
- Writes code
- YesLangflow Assistant turns a natural-language prompt into whole flows or into Python for a single custom component, scoped to Langflow artifacts rather than an application codebase.
Langflow Assistant understands the structure of the Langflow graph, so it can build complete flows or create individual components from natural…
docs.langflow.org/langflow-assistant - Whole-codebase work
- NoThe vendor bounds the assistant's context to the single flow open on the canvas, so it cannot carry a change across a repository or even across flows.
The language model in Langflow Assistant only has the currently opened flow in your workspace for context.
docs.langflow.org/langflow-assistant
Not established: Debugs and fixes
How much it does unattended
- Runs autonomously
- YesAgents you assemble call tools in a loop and decide themselves which to invoke, so a run can finish without a person intervening; approval gates are opt-in.
Agents extend Large Language Models (LLMs) by integrating tools, which are functions that provide additional context and enable autonomous task…
docs.langflow.org/agents - Multi-agent
- YesOne agent can be put in Tool Mode and attached to another, and the A2A component reaches agents outside the instance, so several agents can share a task.
To create multi-agent flows, you can set another Agent component to Tool Mode, and then attach that agent as a tool for your primary Agent component.
docs.langflow.org/agents-tools - Agent permissions
- PartlyDefault is ungated tool calling; approval is opt-in per tool, and then the run checkpoints and waits for a human Approve or Reject before continuing.
The Agent component can pause before calling a gated tool, create a stateful checkpoint, and then resume after a human decision.
docs.langflow.org/agents-tools
Which models it runs on
- Claude
- YesAn Anthropic bundle supplies Claude chat models, and the vendor notes basic Anthropic support ships in every install through the core Language Model component.
The Anthropic component generates text using Anthropic Chat and Language models like Claude.
docs.langflow.org/bundles-anthropic - GPT
- YesOpenAI is a first-class provider with its own bundle, and the GPT model names are enumerated in the component's own parameter table.
Input parameter. The name of the OpenAI model to use. Options include "gpt-3.5-turbo" and "gpt-4".
docs.langflow.org/bundles-openai - Open models
- YesOpen-weight models run through local servers: Ollama, vLLM and LM Studio each have components that point at an instance you operate.
To use the Ollama component in a flow, connect Langflow to your locally running Ollama server and select a model:
docs.langflow.org/bundles-ollama - Model choice
- YesYou choose the provider and model per component; the vendor states plainly that no particular model or vector store is required.
It supports important AI functionality like agents and the Model Context Protocol (MCP), and it doesn't require you to use specific large language…
docs.langflow.org
Where you use it
- In your editor
- NoThe vendor enumerates every way to run Langflow and none is an editor plugin: it is a desktop app, a container, or a Python package serving a browser canvas. IDEs reach it only as MCP clients.
Docker Run Langflow in a container in isolation. Python package Full control over environment, dependencies, and versioning.
docs.langflow.org/get-started-installat… - On the command line
- YesTwo terminal surfaces exist: the langflow CLI that runs and manages the server, and lfx for one-shot flow runs and serving.
The Langflow command line interface is the main interface for managing and running the Langflow server.
docs.langflow.org/configuration-cli - In your pipeline
- PartlyThe DevOps toolkit scaffolds GitHub Actions to validate, test and push flows, but nothing claims Langflow itself reviews or acts on a pull request.
.github/workflows: GitHub CI tooling.
docs.langflow.org/flow-devops-sdk - In a browser
- YesThe visual editor and Playground are served in a browser by the instance you start; there is no vendor-run SaaS in the deployment docs.
To confirm that a local Langflow instance is running, navigate to the default Langflow URL http://127.0.0.1:7860.
docs.langflow.org/get-started-installat…
Whose machine it runs on
- Self-hosted
- YesSelf-hosting is the only hosting the docs describe: a published Docker image, a Helm chart for production Kubernetes, or the Python package.
You can use the Langflow Docker image to start a Langflow container.
docs.langflow.org/get-started-installat… - Open source
- YesThe vendor calls its own codebase open source and documents installing from the public repository; the docs themselves do not name the licence in prose.
As an open-source codebase in a rapidly developing field, Langflow welcomes contributions, whether it be in the form of a new feature, improved…
docs.langflow.org/contributing-how-to-c…
What it costs to run
- How it meters
- NoLangflow meters nothing at all: no seats, credits, tokens or runs. Inference cost lands on the provider account whose key you paste in.
The key must have permission to call the models you want to use in your flow, and your account must have sufficient credits for the actions you want…
docs.langflow.org/get-started-quickstart - Free tier
- YesDocker and pip installs need no account, key or payment step; only the desktop build is gated behind a contact form.
Langflow can be installed in multiple ways. Choose an option below to jump to the steps.
docs.langflow.org/get-started-installat… - API access
- YesEvery flow is callable over HTTP with a Langflow API key, and the vendor ships a TypeScript client plus generated curl, Python and JavaScript snippets.
The Langflow API is the primary way to access your flows and Langflow servers programmatically.
docs.langflow.org/concepts-publish - MCP server
- YesEach project runs its own MCP server so an external agent can call your flows as tools, and Langflow is an MCP client in the other direction.
Langflow integrates with the Model Context Protocol (MCP) as both an MCP server and an MCP client.
docs.langflow.org/mcp-client - Bring your own key
- YesYou paste your own provider keys into the Model Providers pane, and the OpenAI-compatible provider points at any endpoint you host yourself.
In the API Key field, add your provider's API key. Some providers require additional configuration fields.
docs.langflow.org/components-models
Buying it for a team
- A company can buy it
- PartlyNo software licence is sold, so there is nothing to procure for the engine itself; an organisation can only buy an IBM support subscription around its own deployment.
IBM Elite Support for Langflow is a subscription to the Langflow expertise at IBM.
docs.langflow.org/luna-for-langflow - Seat model
- NoMulti-user accounts and roles exist, but no seat price, seat floor or seat ceiling is published anywhere: the software is free to run for as many users as you provision.
Langflow seeds three built-in system roles that an enforcement plugin uses as a starting point for policy sync. These roles cannot be deleted.
docs.langflow.org/authorization - Admin controls
- YesA superuser can hide components, templates, providers and models from the builder, block custom components, and restrict which fields API callers may override.
Superusers can create catalog and model policy to hide components, templates, model providers, and models from the Langflow visual builder.
docs.langflow.org/api-governance-policy - Audit log
- PartlyAn admin audit table exists but is off by default, covers only authorization decisions and share administration, and the vendor calls the default producer best effort.
Write an audit log row for every authorization decision and share-administration action.
docs.langflow.org/authorization - Single sign-on
- PartlyOIDC works by validating a token an upstream proxy forwards, with just-in-time user creation from claims; SAML is not mentioned anywhere and Langflow does not run the login itself.
External authentication lets an upstream identity provider, OIDC proxy, or corporate SSO gateway handle login.
docs.langflow.org/external-authenticati…
What happens to your code
- Opt out of training
- PartlyAnonymous usage telemetry is on by default and switched off with one variable, but the vendor makes no statement about training models on your data either way.
To opt out of telemetry, set DO_NOT_TRACK=True in your Langflow environment variables before starting Langflow. This disables telemetry data…
docs.langflow.org/contributing-telemetry - Data residency
- YesJurisdiction is whichever one you deploy into: flows, message history and logs sit in a SQLite file or a Postgres instance you operate.
In this configuration, all structured application data from Langflow, including flows, message history, and logs, is instead managed by PostgreSQL.
docs.langflow.org/configuration-custom-… - Getting out
- YesFlows export as plain JSON from the UI or the API, individually or as a zipped project, and there are no credits that could expire.
Exported flows are downloaded to your local machine as JSON files named FLOW_NAME.json. If you export an entire project, the JSON files are packaged…
docs.langflow.org/concepts-flows-import - Certifications
- NoNo SOC 2, ISO 27001 or GDPR attestation is claimed; the single GDPR mention assigns the obligation to whoever operates the server.
Follow industry best practices and legal requirements for data privacy and encryption of data in transit and at rest, including GDPR requirements,…
docs.langflow.org/deployment-prod-best-…
29 sourced claims on this page. Checked 2026-09-03. How we check.
Filed under
Sources and updates
Pages we read on docs.langflow.org23
Every fact below comes from the vendor. Nothing here is independently corroborated yet.
- /get-started-installation4 fields
- /agents-tools2 fields
- /authorization2 fields
- /langflow-assistant2 fields
- /1 field
- /agents1 field
- /api-governance-policy1 field
- /bundles-anthropic1 field
- /bundles-ollama1 field
- /bundles-openai1 field
- /components-models1 field
- /concepts-flows-import1 field
- /concepts-publish1 field
- /configuration-cli1 field
- /configuration-custom-database1 field
- /contributing-how-to-contribute1 field
- /contributing-telemetry1 field
- /deployment-prod-best-practices1 field
- /external-authentication1 field
- /flow-devops-sdk1 field
- /get-started-quickstart1 field
- /luna-for-langflow1 field
- /mcp-client1 field
Updates1
- Capabilities · Commercial terms · Free tier
