Langflow

Deploy Langflow, an open source, Python-based framework for building AI agents and other AI applications using a drag-and-drop visual interface.

1. Deploy Langflow

Estimated deployment time: 5–10 minutes

Follow the deployment instructions from the Get started section to configure the app, deploy it, and verify software installation.

For information on the app-specific configurations, see the Configuration options section.

Software included

Software installed on your Linode when deploying the app.

Package	Description
Langflow	An open source visual framework for building AI agents and workflows.
PostgreSQL	An open source relational database that serves as Langflow’s backing store.
NGINX	A web server and reverse proxy that fronts Langflow and terminates SSL.
Docker	A container runtime used to run the Langflow and PostgreSQL services.
Docker Compose	A tool for defining and running the multi-container Langflow deployment.

Base distribution and plan

Supported distribution: Ubuntu 24.04 LTS
Recommended plans: Use a plan with at least 4 GB of memory, such as the 4 GB Shared CPU plan. Langflow runs both the application and its PostgreSQL database as containers on the instance. For better responsiveness when building and running larger flows, use a higher-tier plan.

Configuration options

Configure the required options to deploy your instance. For additional customization, add advanced options.

The table maps the Cloud Manager UI fields to their corresponding API/CLI keys (stackscript_data) required for automated deployments.

StackScript ID: 2141983

UI field	API/CLI key	Description
Required options
Limited sudo user	`user_name`	Your preferred username for the limited sudo user, entered without any capital letters, spaces, or special characters. When adding a limited sudo user, the user is created with a strong generated password for your new Linode instance, and the account is assigned to the `sudo` group, which provides elevated permissions when running commands with the `sudo` prefix. Note: For easier and more secure access with the sudo user, add an account SSH key for the Cloud Manager user during deployment and select that user as an `authorized_user`. Their SSH pubkey will be assigned to both the root and limited sudo users.
Email address (for the Let's Encrypt SSL certificate)	`soa_email_address`	The email used to receive notifications about the renewal of the Let's Encrypt SSL certificate.
Advanced options
Disable root access over SSH	`disable_root`	Applies to a limited sudo user. To block the root user from logging in over SSH, select Yes. Defaults to No. Note: When you disable the root user from logging in over SSH and don't provide a valid Account SSH Key assigned to the `authorized_user`, you can still switch to the root user. To do that, log in as root via the Lish console and run `cat /home/$USERNAME/.credentials` to view the generated password for the limited sudo user.
Linode API token	`token_password`	Applies to a custom domain. The Linode API token if you want to use Linode's DNS Manager to manage DNS records for your custom domain. Follow Manage personal access tokens to get your token on your account with `Read/Write` access to `Domains`. If you provide the token along with the subdomain and domain, the installation attempts to create DNS records via the Linode API. If you don't provide the token, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance.
Subdomain	`subdomain`	Applies to a custom domain. The subdomain you want to use, like `blog` for `blog.example.com`. Use it only if you specify a Domain.
Domain	`domain`	Applies to a custom domain. The domain name you want to use, like `example.com`. Use it only if you specify a Linode API token.
Optional data exporter Add-ons	`add_ons`	An option to include add-ons for your deployment. Possible values are: none (default) alloy node_exporter mysqld_exporter newrelic opentelemetry_collector

Notes:

After the app deployment completes, the password for your limited sudo user is generated and stored in the .credentials file in the home directory, along with application-specific passwords. Log in to your instance as root through the Lish console or SSH, then run cat /home/$USERNAME/.credentials to view its contents.

You can automatically configure a custom domain (optional) during deployment. To do that:

First, configure your domain to use Linode’s name servers via your registrar. See Configure your domain's authoritative name servers for details.

Once you complete that, specify the Linode API token, subdomain, and domain for the app in Cloud Manager or via API/CLI/Terraform.

Use API, CLI, or Terraform

In addition to deploying the app to a new Linode instance via Cloud Manager, you can also use the Linode API, CLI, or Terraform. When running the operation, you need to provide the StackScript ID, supported Linux distribution, and app-specific fields along with the standard Linode deployment configurations.

Note: Generate a personal access token to authenticate your API, CLI, or Terraform requests.

curl --location 'https://api.linode.com/v4/linode/instances' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Bearer abc123def456hij789klm' \
    --data-raw '{
        "region": "us-east",
        "type": "g6-standard-2",
        "image": "linode/ubuntu24.04",
        "label": "my-langflow-one-click-app",
        "root_pass": "@C0mpl3x#P@ssw0rd",
        "stackscript_id": 2141983,
        "stackscript_data": {
            "user_name":"jsmith",
            "soa_email_address":"jsmith@example.com"
        }
    }'

linode-cli linodes create \
    --region us-east \
    --type g6-standard-2 \
    --label my-langflow-one-click-app \
    --image linode/ubuntu24.04 \
    --root_pass @C0mpl3x#P@ssw0rd \
    --stackscript_id 2141983 \
    --stackscript_data '{"user_name":"jsmith", "soa_email_address":"jsmith@example.com"}'

resource "linode_instance" "my-linode" {
    region         = "us-east"
    type           = "g6-standard-2"
    label          = "my-langflow-one-click-app"
    image          = "linode/ubuntu24.04"
    root_pass      = "@C0mpl3x#P@ssw0rd"
    stackscript_id = 2141983
    stackscript_data = {
        "user_name"         = "jsmith"
        "soa_email_address" = "jsmith@example.com"
    }
}

2. Access Langflow

Once your app has finished deploying, you can log in to the Langflow web interface using your browser.

Open your web browser and navigate to one of these:
- https://DOMAIN/, where DOMAIN can be replaced with your custom domain entered during deployment.
- Your Linode instance's rDNS domain. For example, https://192-0-2-1.ip.linodeusercontent.com. See the Manage IP addresses on a Linode guide for details on viewing IP addresses and rDNS.
Log in with the Langflow admin username and password from the .credentials file.

To get the credentials, log in to your Linode instance through the Lish console or SSH and run the cat /home/$USERNAME/.credentials command.

The credentials file also contains your limited sudo user’s password and the PostgreSQL database credentials.
Once you are logged in to Langflow, go to the canvas.
Drag components from the left panel onto the board and connect them to build a flow.

Running a flow that calls an LLM or embeddings provider requires you to add your own provider API key (for example, OpenAI) in the relevant component or under Settings > Global Variables. To learn more, see Langflow Global Variables.

Additional resources

For more information about the installed packages, see their official documentation.

📘
Note that we can't vouch for the accuracy or timeliness of externally hosted resources.