Binions uses Semantic Versioning, so a version number tells you exactly how risky an upgrade is. Every release is labelled MAJOR.MINOR.PATCH, and each of those three numbers has a precise meaning. Read together with the licence model, the version number also tells you whether an upgrade is covered by what you already paid for.
The whole platform ships as one version. All 13 daemons are built and tested together and released at the same version number. You never mix-and-match daemon versions on one host — "the Binions version" is a single number for the whole set.
Binions follows Semantic Versioning. Reading a version left to right, each part signals a different kind of change:
| MAJOR | A breaking change — and a re-licence boundary. Reserved for releases like 2.0.0. Moving up a major needs a new entitlement and may require action on your part. |
| MINOR | A new, backward-compatible capability — for example a new daemon, a new protocol, or a new operation. Existing playbooks and config keep working. |
| PATCH | Bug fixes only, with no change in behaviour. Always safe to apply. |
So 1.4.0 → 1.4.1 is a patch (bug fixes), 1.4.1 → 1.5.0 is a minor (a new feature, added safely alongside the old ones), and 1.x.x → 2.0.0 is a major (a breaking change behind a separate licence). Each release is recorded in a Keep-a-Changelog changelog so you can see what moved.
This is the part that matters for your wallet: a single licence (one set) covers an entire major line. Buying for major 1 covers every release from 1.0.0 all the way through 1.9.9 — every minor feature addition and every patch fix in that line — at no extra cost.
2.0.0 needs a fresh purchase. An upgrade that would cross that boundary is stopped before anything changes — see the major-version gate.What a set costs. A paid set is £1 per binion — £13 one-time per host for today's 13-binion set — and that one purchase covers the whole major line. The free tier (£0) covers one set on one host for non-commercial use. See Renewals & upgrades.
Binions is currently in a pre-production alpha — the 0.x line. Numbered, stable public releases begin at 1.0.
0.x phase — it is early access, not a paid major line.MAJOR.MINOR.PATCH scheme and changelog discipline, so the habits you build now carry straight into the 1.0 line.* Raspberry Pi and other 64-bit ARM hardware are supported from the public 1.0 release. The current alpha packages are 64-bit x86 (amd64) only.