Want to build AI agents using Flowise but prefer to fully control your infrastructure? By self-hosting Flowise on a Ubuntu server, you can cut down costs and manage your data yourself!

Looking for something simpler? If you’d rather skip server management and deploy Flowise in just 1 minute for €9/month, check out our guide on how to deploy Flowise using Sliplane.

Follow along this easy-to-understand guide to learn how you can deploy your own Flowise instance using Docker and Caddy Web server for automatic HTTPS.

For this post, we’re using an affordable server from Hetzner. Hetzner is known to provide great service at an exceptional price/performance ratio, making it an excellent choice for hosting AI applications like Flowise.

Prerequisites

Before we start, make sure you have a Hetzner Cloud account (or be ready to create one).

Step 1: Setup Your Hetzner Server

If you don’t have a Hetzner server yet, follow these steps to create one (the video tutorial is attached below):

1. Go to the Hetzner Cloud Console, choose a project or create a new one, then navigate to Servers → Add Server
2. Follow Hetzner’s guidelines to choose:

• Server type: Select a server type that fits your needs.
• Location: Choose a data center location closest to you or your users.
• Image: Select Ubuntu (latest LTS version recommended).

Add SSH key: Add your SSH public key for secure access. If you don’t have an SSH key yet, you can generate one using ssh-keygen:

ssh-keygen -t ed25519 -C "your_email@example.com"

Click Create & Pay to provision your server

Once your server is created, note down its IP address. You’ll use this to connect via SSH in the next step.

Step 2: Update Your Server

Open your terminal and log into your Ubuntu server via SSH:

ssh root@[your-IP-address]

and update the system to ensure it has the latest security patches and updates:

sudo apt-get update
sudo apt-get upgrade -y

Once finished, your server is ready for installing the software.

Step 3: Install and Configure UFW Firewall

Only keep necessary ports open: SSH (22), HTTP (80), HTTPS (443).

Install UFW and configure the firewall as follows:

sudo apt install ufw -y
sudo ufw allow 22    # SSH
sudo ufw allow 80    # HTTP
sudo ufw allow 443   # HTTPS
sudo ufw enable

Check your firewall configuration:

sudo ufw status verbose

Note: Docker can sometimes ignore UFW rules. To tackle this, verify extra settings as explained here.

Step 4: Docker Installation

Docker will be the container system running Flowise. Install Docker by running these commands:

Setup dependencies and Docker’s GPG key:

sudo apt-get update
sudo apt-get install ca-certificates curl gnupg

sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg \
| sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg

Add Docker repository:

echo \
"deb [arch=$(dpkg --print-architecture) \
signed-by=/etc/apt/keyrings/docker.gpg] \
https://download.docker.com/linux/ubuntu \
$(. /etc/os-release && echo $VERSION_CODENAME) stable" \
| sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt-get update

Install Docker Engine and compose-plugin:

sudo apt-get install docker-ce docker-ce-cli \
containerd.io docker-buildx-plugin docker-compose-plugin -y

Check installation:

sudo docker run hello-world

If you see the "hello-world" message, Docker is ready.

Step 5: Installing Caddy for Automatic HTTPS

Caddy simplifies HTTPS configuration since it handles SSL certificates automatically from Let’s Encrypt.

Install Caddy:

sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl

curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' \
| sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg

curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' \
| sudo tee /etc/apt/sources.list.d/caddy-stable.list

sudo apt update
sudo apt install caddy -y

Before configuring Caddy, you need to point your domain to your server’s IP address. If you haven’t configured DNS yet, follow these steps:

Configure DNS for Your Domain

1. Log into your domain registrar’s dashboard (where you purchased your domain)
2. Navigate to the DNS settings or DNS management section
3. Add an A record with the following settings:

• Type: A
• Name: @ (for root domain) or a subdomain like flowise (for flowise.yourdomain.com)
• Value/Target: Your Hetzner server’s IPv4 address

1. Add an AAAA record for IPv6 support:

• Type: AAAA
• Name: @ (for root domain) or the same subdomain you used for the A record
• Value/Target: Your Hetzner server’s IPv6 address

Note: DNS changes can take a few minutes to several hours to propagate. You can check if your DNS is configured correctly using tools like dig or online DNS checkers. Once the DNS record is active, you can proceed with Caddy configuration.

Configure Caddy

Edit the Caddyfile configuration file:

sudo nano /etc/caddy/Caddyfile

Enter your domain and configure reverse proxy. Replace "yourdomain.com" with your actual domain name:

yourdomain.com {
reverse_proxy localhost:3000
}

If no domain yet, use this temporarily:

:80 {
reverse_proxy localhost:3000
}

Restart Caddy to load the config:

sudo systemctl restart caddy

Step 6: Running Flowise with Docker Compose

We’re going to use Docker Compose for easier setup. First create a directory for Flowise and navigate to it:

mkdir ~/flowise
cd ~/flowise

Create compose.yml with the following content:

services:
flowise:
image: flowiseai/flowise:3.0.12
restart: always
ports:
- "3000:3000"
volumes:
- flowise_data:/root/.flowise
environment:
- DATABASE_PATH=/root/.flowise
- SECRETKEY_PATH=/root/.flowise
- LOG_PATH=/root/.flowise/logs
- BLOB_STORAGE_PATH=/root/.flowise/storage

volumes:
flowise_data:

This setup ensures:

• Your database persists across container restarts
• Secrets don’t reset
• Logs and file uploads are kept between restarts

Now deploy Flowise by running Docker compose:

sudo docker compose up -d

Docker pulls the Flowise image and runs it in background mode using port 3000.

Step 7: Accessing Your Self-Hosted Flowise Instance

Visit your domain in any web browser. Your Flowise instance should now load successfully at https://yourdomain.com. Follow the setup steps in the interface to complete your initial setup.

Security Recommendations

Public servers should always be secure. The following practises are recommended:

• Regularly apply updates and security patches.
• Set strong passwords and control user access.
• Monitor server logs for suspicious activity.
• Install tools like Fail2ban for extra security.

Updating your Flowise Installation

When you want to update your Flowise instance, first check the latest version on Docker Hub, then update the image version in your compose.yml file and run:

sudo docker compose pull
sudo docker compose up -d

Docker will download updated versions automatically and replace your current containers.

Cost Comparison with Other Providers

Self-hosting Flowise typically results in lower cost compared to hosted services:

Provider	vCPU	RAM	Disk	Monthly Cost
Render.com	1	2 GB	40 GB	~$35
Fly.io	2	2 GB	40 GB	~$17–20
Railway	2	2 GB	40 GB	~$15–30
Sliplane.io	2	2 GB	40 GB	~€9.50 flat
Hetzner Cloud (self-hosted)	2	2 GB	40 GB	~€5–10/month

You maintain complete control and avoid additional usage-based charges by self-hosting. But of course there is no free lunch and you’re now responsible for managing your own server!

Deploy Flowise in minutes with Sliplane now!