Activating Binions means turning your licence into a running set on one host. It takes a single command, copied from your account, that adds the package repository, signs in with your one-time token, and installs the whole set. From then on the licence is tied to that one machine, and every daemon checks it as it starts.
What is a set? A set is one complete installation of Binions — all of its background services (its daemons) — on a single host. You licence and activate the set as a whole, not one daemon at a time. See Licensing & Purchase for the full model.
Activation is a short, one-time flow — you start in your account and finish on your host:
The exact install command is generated per account, so the shape below is illustrative only — always copy the real one-line command from your account page.
# Illustrative shape only — copy the real command from your account page.
# It adds the Binions repository, authenticates with your one-time token,
# and installs the full set in one step.
curl -fsSL https://<your-account-install-url> | sudo bashWhen it finishes, confirm the set is up. These checks are generic — the exact daemon names and health endpoint appear on your host and in the installation guide:
# Is a daemon active?
systemctl is-active binions-logger
# Is the platform answering its health check?
curl -sf http://127.0.0.1:9100/health/ready && echo OKYour token is yours alone. The install command on your account page is unique to you and carries a single-use token. Copy it from your own account each time — never reuse one from elsewhere. If activation fails, see License problems.
Each install token is single-use and ties your set to exactly one host. Two mechanisms keep it that way:
A token’s lifecycle runs Unused (waiting on your account page) → Redeemed (activated and bound to one host’s fingerprint) → Invalidated (the host was released; never usable again) — at which point a fresh Unused token appears automatically for your next install.
Why it works this way. Rotation and host binding keep one licence on one machine at a time, so a single licence can’t be quietly copied onto many hosts — while you stay free to move your set whenever you need to.
Your licence follows you — it simply lives on one machine at a time. To move a running set, release the old host first, then activate on the new one:
Reinstalling follows the same pattern: release, then activate with the fresh token. Because the binding is tied to the host’s identifiers, a clean OS reinstall counts as a new host — so release first. Always release the old host before activating elsewhere. If a machine has failed and you can’t uninstall on it, contact support through your account (see License problems).
Every daemon verifies its licence each time it starts. Each daemon’s licence is a small signed file kept at /etc/binions/<daemon>.license, and one shared set token unlocks all of them on the host. At boot, a daemon runs three checks:
apt update keeps it current.