Quickstart
Sign up, copy the install script from your portal, run it as root. apt install the binions you want. systemd takes it from there. Sixty seconds to your first running daemon.
Prerequisites
step 0 · 1
Ubuntu 22.04 LTS or 24.04 LTS. Two vCPU and two gigabytes of RAM is plenty to run the full stack.
step 0 · 2
The install script writes to /etc/apt/keyrings, /etc/apt/auth.conf.d, and /etc/apt/sources.list.d. Read-only after that.
step 0 · 3
Free at portal.binions.io. Magic-link email login. Accept the non-commercial terms to activate your free set, then grab each set's install script from its row on the dashboard.
Three commands
apt install.Run as root. Total time: 60 seconds for the first daemon, plus apt's download time.
1
Every set of binions has its own install script — open the set's row on the portal dashboard and copy it. The script adds the archive keyring, the set's credentials and APT source, installs the set, and redeems its license on this host.
$ sudo bash install-binions.sh # copied from your set's dashboard row
2
apt install binions pulls the whole set — every daemon, each a single static binary, mold-linked, systemd unit shipped.
$ sudo apt update && sudo apt install -y binions
3
Operator console talks to all thirteen daemons over local health endpoints. Twelve UP with NRestarts=0 and you're done.
$ binions-cliconsole status
Sample output
Every daemon exposes /health/ready on its loopback port. binions-cliconsole status fans out the requests in parallel with a 500 ms timeout and prints a single tidy table. If you see twelve UP rows with three-millisecond latency, you're good.
Logger writes JSONL to /var/log/binions/*.jsonl; journalctl -u binions-* still works for systemd-side diagnostics.
$ binions-cliconsole status
| service | url | state | latency |
| logger | http://127.0.0.1:9100/health/ready | UP (200) | 3 ms |
| database | http://127.0.0.1:9102/health/ready | UP (200) | 3 ms |
| traefiklinker | http://127.0.0.1:9103/health/ready | UP (200) | 3 ms |
| aiinjector | http://127.0.0.1:9104/health/ready | UP (200) | 3 ms |
| datatransporter | http://127.0.0.1:9105/health/ready | UP (200) | 3 ms |
| dataanaliser | http://127.0.0.1:9106/health/ready | UP (200) | 2 ms |
| mailbox | http://127.0.0.1:9107/health/ready | UP (200) | 2 ms |
| playbook | http://127.0.0.1:9108/health/ready | UP (200) | 3 ms |
| webhookcaller | http://127.0.0.1:9109/health/ready | UP (200) | 2 ms |
| scheduler | http://127.0.0.1:9110/health/ready | UP (200) | 2 ms |
| showman | http://127.0.0.1:9111/health/ready | UP (200) | 2 ms |
| modbus | http://127.0.0.1:9112/health/ready | UP (200) | 2 ms |
Next steps
Drop a YAML file into /etc/binions/playbook/, send a Fact event, watch the orchestrator route it through your stack.
Configure binions-mailbox in the portal, link IMAP credentials, ingest incoming mail into the Redis bus as Fact.Mail.Received events.
Repeat on host two with the same install script. Each extra host is a paid set, auto-provisioned from your portal account; no manual key shuffling.