Read all about it here!
A visual framework for building multi-agent and RAG applications
Open-source, Python-powered, fully customizable, LLM and vector store agnostic
Docs - Join our Discord - Follow us on X - Live demo
- 📝 Content
- 📦 Get Started
- 🎨 Create Flows
- Deploy
- 🖥️ Command Line Interface (CLI)
- 👋 Contribute
- 🌟 Contributors
- 📄 License
You can install Langflow with pip:
# Make sure you have >=Python 3.10 installed on your system.
python -m pip install langflow -U
Then, run Langflow with:
python -m langflow run
Creating flows with Langflow is easy. Simply drag components from the sidebar onto the workspace and connect them to start building your application.
Explore by editing prompt parameters, grouping components into a single high-level component, and building your own Custom Components.
Once you’re done, you can export your flow as a JSON file.
Load the flow with:
from langflow.load import run_flow_from_json
results = run_flow_from_json("path/to/flow.json", input_value="Hello, World!")
DataStax Langflow is a hosted version of Langflow integrated with AstraDB. Be up and running in minutes with no installation or setup required. Sign up for free.
You can also preview Langflow in HuggingFace Spaces. Clone the space using this link to create your own Langflow workspace in minutes.
Follow our step-by-step guide to deploy Langflow on Google Cloud Platform (GCP) using Google Cloud Shell. The guide is available in the Langflow in Google Cloud Platform document.
Alternatively, click the "Open in Cloud Shell" button below to launch Google Cloud Shell, clone the Langflow repository, and start an interactive tutorial that will guide you through the process of setting up the necessary resources and deploying Langflow on your GCP project.
Use this template to deploy Langflow 1.0 on Railway:
Follow our step-by-step guide to deploy Langflow on Kubernetes.
Langflow provides a command-line interface (CLI) for easy management and configuration.
You can run the Langflow using the following command:
langflow run [OPTIONS]
Each option is detailed below:
--help
: Displays all available options.--host
: Defines the host to bind the server to. Can be set using theLANGFLOW_HOST
environment variable. The default is127.0.0.1
.--workers
: Sets the number of worker processes. Can be set using theLANGFLOW_WORKERS
environment variable. The default is1
.--timeout
: Sets the worker timeout in seconds. The default is60
.--port
: Sets the port to listen on. Can be set using theLANGFLOW_PORT
environment variable. The default is7860
.--env-file
: Specifies the path to the .env file containing environment variables. The default is.env
.--log-level
: Defines the logging level. Can be set using theLANGFLOW_LOG_LEVEL
environment variable. The default iscritical
.--components-path
: Specifies the path to the directory containing custom components. Can be set using theLANGFLOW_COMPONENTS_PATH
environment variable. The default islangflow/components
.--log-file
: Specifies the path to the log file. Can be set using theLANGFLOW_LOG_FILE
environment variable. The default islogs/langflow.log
.--cache
: Selects the type of cache to use. Options areInMemoryCache
andSQLiteCache
. Can be set using theLANGFLOW_LANGCHAIN_CACHE
environment variable. The default isSQLiteCache
.--dev/--no-dev
: Toggles the development mode. The default isno-dev
.--path
: Specifies the path to the frontend directory containing build files. This option is for development purposes only. Can be set using theLANGFLOW_FRONTEND_PATH
environment variable.--open-browser/--no-open-browser
: Toggles the option to open the browser after starting the server. Can be set using theLANGFLOW_OPEN_BROWSER
environment variable. The default isopen-browser
.--remove-api-keys/--no-remove-api-keys
: Toggles the option to remove API keys from the projects saved in the database. Can be set using theLANGFLOW_REMOVE_API_KEYS
environment variable. The default isno-remove-api-keys
.--install-completion [bash|zsh|fish|powershell|pwsh]
: Installs completion for the specified shell.--show-completion [bash|zsh|fish|powershell|pwsh]
: Shows completion for the specified shell, allowing you to copy it or customize the installation.--backend-only
: This parameter, with a default value ofFalse
, allows running only the backend server without the frontend. It can also be set using theLANGFLOW_BACKEND_ONLY
environment variable.--store
: This parameter, with a default value ofTrue
, enables the store features, use--no-store
to deactivate it. It can be configured using theLANGFLOW_STORE
environment variable.
These parameters are important for users who need to customize the behavior of Langflow, especially in development or specialized deployment scenarios.
You can configure many of the CLI options using environment variables. These can be exported in your operating system or added to a .env
file and loaded using the --env-file
option.
A sample .env
file named .env.example
is included with the project. Copy this file to a new file named .env
and replace the example values with your actual settings. If you're setting values in both your OS and the .env
file, the .env
settings will take precedence.
We welcome contributions from developers of all levels to our open-source project on GitHub. If you'd like to contribute, please check our contributing guidelines and help make Langflow more accessible.
Langflow is released under the MIT License. See the LICENSE file for details.