Binions runs as one complete, self-contained set on a single host. There is no clustering and no shared state between machines, so “multi-host” simply means running several independent sets — one full installation on each machine. This page explains how that works, what it costs, and the common ways people spread Binions across more than one host.
No cluster to run. Binions deliberately has no Kubernetes, no shared message broker, and no cross-host coordination. Each host is its own standalone system — which keeps every install simple, fast, and easy to reason about.
Binions follows a strict single-host rule: a complete set of daemons runs on one machine, and all the parts talk to each other over localhost. Nothing is split across machines, and nothing is coordinated between them by default.
The payoff is simplicity. There is no orchestration layer to install, secure, or keep alive; one host’s entire platform can be backed up as a single snapshot, and everything you need to debug lives in one place. For how the parts fit together on a single machine, see the Architecture overview.
Because the unit of licensing is a set — one complete installation on one host — running on more machines means paying for more sets.
Worked example. A dev host (non-commercial, free) plus a production host costs one paid set — £13 today. Five production hosts cost five paid sets. There is no volume tier or subscription; each host is simply one more one-time set. See the plan comparison for the full breakdown, and the set licensing model for the rules.
There is no special multi-host installer and nothing extra to configure. You simply repeat the normal single-host install on each machine.
apt install, exactly as you would for a single host.Full steps are on the Install via apt (single host) page. Activation and tokens are covered under Licensing & Purchase.
If you want two or more Binions hosts to cooperate, you connect them the same way you connect any other services — over the network. One host calls another host’s HTTP endpoint, sends it a webhook, or hands off a message; the receiving host treats that just like any other incoming event.
Heads up. Hosts never share state automatically. If two hosts need to coordinate, that coordination is yours to build with playbooks — Binions will not do it behind the scenes.
Running several independent sets opens up a few familiar deployment shapes: