What it does
7 features
Langflow · Builder for agents and workflows
Product and access
Langflow is an open-source project. A blog post dated 25 February 2025 names DataStax as parent company and announces IBM’s planned acquisition of DataStax. DataStax now appears under IBM’s name, but the reviewed provider pages do not state completion.
Core features
7 features from provider sources · checked on 5 November 2026. Availability and limits are directly below.
Visual flow editor
Components are connected by drag and drop. Python lets you add custom components.
Source 2Agents with tools
According to the documentation, the Agent component can use any component as a tool, including other agents and MCP servers. You enable Tool Mode on the component for this.
Source 6Serve as API and MCP server
Flows can be served as an API. Each project gets its own MCP server whose tools MCP clients can use. A flow needs a Chat Output component for this.
Source 7Use MCP tools
The MCP Tools component connects external MCP servers via STDIO, HTTP/SSE or a JSON configuration.
Source 8Webhook triggers
A POST to the webhook endpoint starts a flow. The response only confirms the start, not the result. A Langflow API key is required by default.
Source 9Built-in chat memory
The Agent component has chat memory enabled by default, grouped by session ID. The default is a SQLite database; another database can be configured.
Source 10
Show all 7 features
Flow version history
You save snapshots of a flow as versions, preview them read-only and restore them. Versions are stored in the installation’s database.
Source 11
Usable AI models
Open choice
You add your own key per provider in the settings and pick the model in the agent. Included by default are Anthropic, OpenAI, Google, IBM, Cohere, Ollama and an OpenAI-compatible endpoint, among others. Mistral, DeepSeek, xAI, OpenRouter and LiteLLM come through add-on packages.
Model families named
- Anthropic (Claude)
- OpenAI (GPT)
- Google (Gemini)
- IBM (Granite)
- Cohere
- Mistral
- DeepSeek
- xAI (Grok)
- Other models can be connected freely
- Model choice
- You choose
- Your own API key
- Yes
- Router or custom endpoint
- Yes
- Local models
- Yes
The rating covers the generally available main access. Documented · Sources accessed on
Langflow: Use agents · Langflow: Language Model · Langflow: Bundle list
Does it fit my task?
2 practical tasks · 7 requirements and limits
A good fit if …
- you want to build agents and workflows visually and serve them as an API or MCP server
- you want to run the software yourself and choose model providers freely
- you want to add your own Python components and external MCP tools to a flow
Less suitable if …
- you expect fixed roles and permissions without an extra plugin
- you need schedules or approval before tool calls built in
- you are looking for a solution hosted by the provider
Editorial assessment based on provider documentation. Not a product test.
Practical tasks
Editorial examples based on documented features. No product tests performed.
Serve an agent with tools as an API
- Your input
- A flow from the Simple Agent template with a configured model provider.
- Possible result
- The agent answers requests in the Playground and can be called as an API.
- What to check
- Test in the Playground, read the message logs and keep an eye on model costs.
Start a flow by webhook
- Your input
- A flow with a Webhook component that receives JSON from an external application.
- Possible result
- Each POST starts a run; a Parser component turns the data into text.
- What to check
- Check results inside the flow, because the response only confirms the start.
Build a support agent with your own knowledge source and serve it as an API.
Your possible prompt
Design a process for new requests: capture information, sort it by topic, and create a proposed response. Plan an approval step before external actions.
Adjust the task, data and permissions.
Requirements and limits
Requirement
Model access required
The quickstart uses an OpenAI key as its example. Only one key can be added per provider, and the account needs sufficient credits.
Source 5Requirement
Python and uv for the package install
The Python package needs Python 3.10 to 3.14 and uv. The minimum is a dual-core CPU and 2 GB RAM; more cores and at least 4 GB are recommended.
Source 4Limitation
Desktop without Shareable Playground and Voice Mode
According to the installation page, some features are unavailable in Langflow Desktop, such as the Shareable Playground and Voice Mode.
Source 4Limitation
Role-based access only via plugin
Role-based access control needs a registered authorisation plugin, which Langflow does not include. Without one, every authenticated user is allowed.
Source 13Limitation
MCP server without authentication is public
If a project has no authentication set, anyone can use its MCP server without credentials. The documentation advises this only in trusted environments.
Source 7Limitation
Webhook returns no result
The webhook response only shows that the flow started. The webhook page describes no schedules.
Source 9Limitation
Hosted offering removed
According to DataStax, hosted Langflow was removed from Astra on 9 April 2026. The Langflow homepage still mentions a free cloud account, but no sign-up for it or other hosted offering could be found.
Source 19
Can I use it?
Availability still unclear
Europe & regional availability
Website, documentation and telemetry page reviewed. They name no country release or data regions.
Reviewed scope: Self-operated software; model providers separately
Reviewed on:
Availability still unclear
Europe: no provider statement
When self-hosting, flows and chat history are stored in a local SQLite database by default. The reviewed pages say nothing about Europe or regions of the cloud offering. On telemetry, the documentation names DO_NOT_TRACK=True to opt out; it does not state the default explicitly. It lists items such as durations and version data, plus the registered email address in the desktop version.
Region, reason and source
Region covered: EU/EEA, United Kingdom and Switzerland
Documented reason: The reviewed sources name no country release for this.
Official source · docs.langflow.org · Official source · docs.langflow.org · Official source · www.langflow.org
Accounts & permissions
Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use.
Configuration covered: Self-operated Langflow installation with your own model access
Sources reviewed:
Show all 3 points
Documented
Account used
According to the documentation, built-in sign-in with username and password is always available and the default; it issues short-lived session tokens. Alternatively an identity provider handles sign-in through a proxy. You add the model provider key in settings under Model Providers.
Evidence · EvidenceDocumented
Admin approval
Role-based access control requires an authorisation plugin, which Langflow does not include. Without a plugin, Langflow allows every authenticated user.
EvidenceDocumented with conditions
Data access & team sharing
Reach depends on configuration. Webhooks require an API key by default; without authentication, calls are treated as sent by the flow owner. An MCP server without authentication is publicly reachable. The Shareable Playground, meant for testing only, makes a flow’s Playground usable at a public URL without installing Langflow or an API key.
Evidence · Evidence · Evidence
Memory and conversation continuity
3 of 6 criteria documented
Chat histories are stored in the Langflow database by default, grouped by session ID, and can be viewed, edited and deleted in the Playground.
Chat memory of the Agent component and the Message History component
Sources accessed:
Documentation by criterion
StorageDocumented
Storage and scope
By default Langflow stores data in a SQLite database, with messages in the messages table. LANGFLOW_DATABASE_URL lets you use another database, including for chat memory only.
SelectionPartly documented
Selection and timing
The Agent component has chat memory enabled by default and retrieves a limited number of earlier messages; the number is configurable, and the page gives no default. The pages do not describe how content is selected for lasting memory.
Edit & deleteDocumented
Inspect, edit and delete
In the Playground you open the message logs from a session’s options, edit or delete individual messages and delete whole sessions. Editing changes the messages table.
Access boundariesPartly documented
Agent and channel boundaries
Histories are grouped by session ID; the default ID is the flow ID. For multiple users the documentation suggests custom session IDs. The page does not show whether messages are separated across projects.
RetrievalDocumented
Retrieval
The agent can retrieve earlier messages of the same session. The Message History component reads data even outside a chat. For semantic search across sessions the page points to a memory base rather than chat memory.
New conversationsPartly documented
Session reset and compaction
A different session ID, in the editor or via the API, starts a separate session. According to the documentation the agent works with a rolling context window per session. The reviewed pages describe no new-chat button or compaction.
Cost and effort
1 plan · Prices as of 5 November 2026
Prices and included usage
Pricing checked
Langflow is available under the MIT licence for self-hosting. Model costs depend on your provider. According to DataStax, hosted Langflow was removed on 9 April 2026.
| Plan | Price | Included |
|---|---|---|
| Langflow (open source) | No software fee stated | Open-source software for self-hosting under the MIT licence. |
- A pricing page at www.langflow.org/pricing could not be retrieved (404).
Setup
Install the desktop app, the uv package or Docker, add a model provider API key and build a flow from a template such as Simple Agent.
Operation & oversight
Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.
Deployment covered: Self-operated installation (desktop, package or Docker)
Sources reviewed:
Editorial assessment
You operate Langflow yourself and are responsible for sign-in, database and logs. Set authentication for webhooks and MCP servers deliberately and plan your own approvals and error monitoring.
Show all 6 points
Documented with conditions
Sign-ins
Official release packages and tagged source archives disable automatic login by default; development branches do not. For new Python package installations, the quickstart says to set LANGFLOW_AUTO_LOGIN=false with a strong superuser password; Docker images require authentication by default. On session lifetimes the reviewed pages say only that tokens are short-lived.
Evidence · Evidence · EvidenceDocumented with conditions
Detecting errors
Logs go to stdout by default, with ERROR as the default level; a file can be configured. Log retrieval through an endpoint is off by default. The MCP server’s default tool timeout is 180 seconds. A Parser component can fail to build if it receives no or bad data. The pages describe no alerting on errors.
Evidence · Evidence · EvidenceDocumented with conditions
Resuming after failures
Saved versions of a flow can be restored, optionally backing up the current draft. If a flow was saved elsewhere, Langflow refuses the save and offers update, duplicate or load latest. The reviewed pages do not describe resuming an interrupted run.
Evidence
Evidence and open questions
19 sources · 1 open point
Open points
The reviewed sources contain no reliable information on these points. A gap says nothing about the product.
Europe: Availability still unclear
Sources and evidence
Provider website, documentation, blog and repository reviewed. A pricing page could not be retrieved. Feature descriptions come from the provider; example tasks are editorial. Hands-on tests are still pending.
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
Provider
The project is developed in the langflow-ai/langflow repository under the MIT licence. The blog names DataStax as parent company (as of February 2025).
- Operator
- Langflow
- Organization
- Open-source project
- Website
- www.langflow.org
- Repository
- langflow-ai/langflow
- GitHub stars
- 156.355 · Reviewed
- License
- MIT
Changes to this profile 1
A visual builder for agents and workflows, usable as an API or MCP server.
These notes describe editorial changes. Source and pricing review dates appear in their respective sections.