Installation
Five ways to run Flowfile, from zero-install to a team server. The Python package is the recommended default — it brings the visual editor, the Python API, and all services in one install.
| Path | Best for | Requires |
|---|---|---|
| Python package | Most users — the full platform locally | Python 3.10–3.13 |
| Desktop app | A double-clickable app, no Python | macOS, Windows, or Linux |
| Docker | Teams: auth, sharing, a shared catalog | Docker |
| Browser (Lite) | Trying it with nothing installed | A browser tab |
| From source | Contributing to Flowfile | Poetry + Node |
pip install flowfile
flowfile run ui
Your browser opens the Flowfile designer. If it doesn't, go to http://127.0.0.1:63578/ui#/main/designer manually. Running flowfile with no arguments prints the installed version.
Details and the Python-package specifics: Python Package.
Signed installers, straight from the latest release:
Latest release · all platforms, checksums & signatures
Per-OS steps: Desktop App.
Deploying on a server? The hosting kit runs the published images (version-pinned) behind HTTPS — Caddy with Let's Encrypt, a Cloudflare Tunnel, or plain LAN — with a guided installer that generates secrets and checks your DNS:
git clone https://github.com/Edwardvaneechoud/flowfile-hosting.git && cd flowfile-hosting
./install.sh
Evaluating locally? The main repo's compose builds from source:
git clone https://github.com/edwardvaneechoud/Flowfile.git && cd Flowfile
docker compose up -d # frontend at http://localhost:8080
Security checklist and operations: Docker deployment.
Flowfile Lite runs the visual editor entirely in your browser at demo.flowfile.org — a subset of the full product (no backend services, databases, scheduler, or AI), good for a first look and small files.
Clone the repo and see For Developers for the Poetry + npm setup.
Installed? The Quickstart builds your first real pipeline in about ten minutes. Choosing between these shapes for a team is the deployment overview's job.