NGINX and keepalived, managed without a controller.
fūin load balancer is a desktop app for running NGINX reverse proxies and load balancers with keepalived high availability. Your configuration lives in git, a small agent applies it on each node, and nothing sits in between.
In testing. App for Windows, macOS and Linux; agent for Debian and Ubuntu.
How it fits together
No central server to install, patch or protect. The app talks to the agents directly, and git is the single source of truth.
-
Git repository
The desired state of every site, upstream and HA group, as readable text files. History, review and approval through pull requests.
-
Desktop app
Edit, plan and apply. Shows live status, drift and alerts. Windows, macOS and Linux.
-
Nodes
A small agent next to NGINX and keepalived on each Debian or Ubuntu node. Checks health and sends alerts on its own.
Changes you can trust
Nothing goes live directly. Every change is a draft first, then a plan you can read, then an apply you can undo.
Plan, then apply
See the exact config diff per node before anything changes. Each apply comes from a commit, so you always know which version runs where.
Automatic rollback
Backup nodes go first, then the master after health checks pass. If a config test or health check fails, the node is rolled back on its own.
Four eyes on production
Production only takes changes from the main branch, so a pull request and review come first. Signed commits are supported.
Drift and conflicts
Manual edits on a node show up as drift. Two admins applying at once cannot overwrite each other: the second is asked to update first.
Example: a change is applied to the backup node first. If its health checks pass, the master follows. If they fail, the backup node is rolled back and the master is not touched.
What it does
The daily work of running a load balancer pair, in one calm window.
HA groups
Pairs or groups of nodes with keepalived, VRRP over unicast or multicast, and a clear view of who is master and why.
Maintenance and failover
Put a node in maintenance or move the virtual IP on purpose, and watch the failover happen.
Sites and upstreams
Domains, locations, TLS and upstreams in a form, with the generated NGINX config always one click away.
Backend roles and sticky sessions
Primary, backup, drain and down per backend. Draining lets sticky sessions run out and reports when a backend is empty.
Active health checks
The agent checks backends itself, so checks and alerts keep running when the app is closed.
Layer 4 balancing
Layer 4 virtual servers with LVS through keepalived, next to your HTTP sites.
Certificates
ACME certificates, such as Let’s Encrypt, over HTTP-01 or DNS-01 (Cloudflare and RFC 2136), or upload your own. Renewal runs on the nodes.
Import what you have
Take over existing NGINX and keepalived configs. A backup is made first, and anything fūin does not understand is kept verbatim.
Alerts and monitoring
Microsoft Teams and email alerts straight from the nodes, plus a local status endpoint and template for Zabbix.
History and restore
Every change is a commit. Browse the timeline, see who changed what, and restore an earlier state.
Built for the keyboard
A command palette, shortcuts for plan and apply, and status that is never shown by colour alone.
Signed updates
App and agent updates are signed and checked before they are installed. Agents are updated from the app.
Security first
A load balancer sits in front of everything. fūin keeps its own footprint on the node as small as it can.
Pinned on both sides
The app and the agents talk over mutual TLS 1.3. Both sides pin each other’s key; there is no certificate authority to trust or lose.
Least privilege
The agent runs as an unprivileged user and listens only on the management network. A tiny helper with a fixed set of commands does the few things that need root. There is no shell access.
No secrets in git
Private keys, webhook addresses and passwords stay on the nodes or in your system keychain. Removing an admin from git and applying revokes their access at once.
What you need
Nodes are enrolled once over SSH. After that, the app only uses its own encrypted connection.
Your computer
Windows, macOS or Linux, with Git and an SSH client.
Your nodes
Debian or Ubuntu with systemd, NGINX mainline from nginx.org (1.29.6 or later) and keepalived.
Your repository
Any git repository you can push to, local or on GitHub. Branch protection on main is recommended.
Availability
fūin load balancer is in testing. Licensing and downloads will be announced on this page.