One Binions licence covers one complete set on one host, plus a whole major version line of updates. A set is one full installation of Binions on a single machine, and your licence keeps that set up to date across every minor and patch release within your major version — at no extra cost. This page is the reference for exactly what a licence includes, and for how long.
Good to know. The unit of licensing is the set, not the individual daemon. One licence covers the entire set of daemons on its host — you do not license features one by one.
A single licence ties one set of Binions to one host and entitles that host to a defined line of updates. At a glance:
| Hosts | One host per set — the licence is host-bound (tied to one machine at a time) |
| Daemons | The complete set — every daemon in the installation is covered |
| Version line | One major line, for example 1.0.0 through 1.9.9 |
| Updates within the major | Included — all minor and patch releases in your major are free updates |
| New daemons added in the major | Included — daemons added during your major join your set at no extra cost |
Price & set size. A set is priced at £1 per binion (£13 for today’s 13). If new binions are added during your major, they join your set at no extra cost — you are not re-charged. The per-binion price simply sets what a new purchase costs as the platform grows. See Plan comparison.
Binions uses standard semantic versioning: every release is numbered major.minor.patch. Reading a version like 1.5.2 from left to right:
1). This is the line your licence is bound to. A change here is a big release that may behave differently.5). Each minor adds new features in a backwards-compatible way.2). Patches are fixes and small improvements within a minor.Your licence covers everything inside your major. Within a single major line there are up to 9 minor releases (1.1, 1.2, … 1.9), and each minor can carry up to 99 patch releases (for example 1.5.0 through 1.5.99). Every one of those minor and patch updates is a free update for the life of that major.
The key idea. Buy into a major once, and you keep getting updates — new features and fixes alike — all the way up to the last patch of the last minor in that major (for example, up through
1.9.9). No upgrade is needed until the next major version.
Two kinds of release sit outside a current licence:
2.0.0. A new major is a separate line and is not included in a licence for the previous major. Moving up requires a new or upgrade licence. The upgrade flow is covered on Renewal & major upgrades.0.x releases (such as alpha builds). These are early-access previews and fall outside licence scope.Heads up. A jump to a new major (the first number changing, for example
1.x→2.0.0) is the only update that steps outside your licence. Everything below that — every minor and patch in your major — stays included.
Licensing is per set, and a set lives on exactly one host:
For how the set model works in detail, see The set licensing model. For where the free non-commercial tier ends and paid commercial use begins, see Commercial vs non-commercial.