One box.
One price. No procurement.
Most file tools price per seat, per month, forever — and a five-person workshop ends up in an enterprise sales call. The small-business license is the opposite shape: one install, one flat annual price, every Pro capability. A signed license file arrives by reply; the binary you already run just starts doing more.
What the license is
flat · annual · per installMultiple roots, the OIDC verifier, session recording, the proxy-header verifier — the complete Pro entitlement set, on one install. No feature switches to argue about, no per-seat math.
The license names your install's ceilings — accounts and roots —
at sizes a small team actually uses, priced once a year. The engine
shows them live on /status, next to what it is running.
The Ed25519-signed release artifacts for x86-64 and arm64, and the signed update channel with upgrade notes — verified before install by the binary itself.
Support by email for the licensed install: questions answered by the people who wrote the engine, not a ticket queue reading a script. Response-time promises arrive with the published terms — we will not print an SLA before it is signed.
Nothing hosted, nothing metered home. The license verifies offline, updates verify offline, and there is no telemetry — the product never learns who you are from running.
The code is and remains AGPL-3.0-only. What you buy is the signed convenience and the capability set — never a lock on your own data or your freedom to rebuild.
Against the free build
what the money changes| capability | wire name | oss | small business |
|---|---|---|---|
| Served roots | multiple_roots | one | several |
| OIDC sign-in (your IdP) | verifier_oidc | — | ✓ |
| Trusted-proxy header auth | verifier_proxy | — | ✓ |
| Terminal session recording | session_recording | — | ✓ |
| Accounts, grants, ledger, plugins, exec, terminal, shares, WebDAV | — | ✓ | ✓ |
| Signed release artifacts + update channel | — | self-built | ✓ |
| Support | — | — |
Everything in the free row is real today — shares, the WebDAV door, media previews and the whole single-box surface ship in the OSS build. The ladder climbs for the multi-box and sign-on surface; the full matrix is on the pricing page.
Why it is shaped this way
a workshop, not a procurementA small business runs one or two machines that matter. Licensing the install matches what you actually own — new hires cost nothing, because accounts on a box you already licensed were never the scarce thing.
One renewal a year, one invoice, no monthly drip and no per-seat true-up audits. If the license lapses the install degrades loudly to the free capability set — your files, sessions and ledger stay exactly where they were.
Start on the free build today — it is the same binary. When the signed license arrives it is dropped in as one file and a restart; accounts, roots, history and the ledger carry forward untouched.
Buy it
three steps, one email- Tell us the install — a name for the license, the account and root ceilings you want (pick generously; ceilings are ceilings, not bills), and whether your sign-on runs an OIDC provider we should expect.
- We reply with the license and the invoice — a signed JSON envelope for your install, verified offline by the binary you already run, and a plain annual invoice a bookkeeper can pay.
- Drop the file in, restart —
[license] pathin the config, one restart, and/statusshows the new capability set live.
Bigger shape — several installs, SAML or Kerberos, LDAP directories, fleet management? That is the enterprise track, and the full ladder is one page over. Between the two and unsure — say so; the honest answer is usually this one.