0014: Licensing and commercial model
- Status: amended (see "Amendment: license revocation list" below)
- Date: 2026-09-25
Context
A secrets manager is trusted only if its cryptography and format can be read and audited. Businesses will pay for the things that matter when secrets go wrong: enforcement, audit, compliance evidence and support. The honor-system model (Sublime Text, WinRAR, Fork) works at indie scale when the license text is explicit, buying is trivial and the reminder is mild and offline.
Decision
Two layers, each under its own license, reflecting that the layers earn trust in different ways: the core is trusted because it can be read; the honor system on the apps is trusted because it visibly is not silently enforced against you.
- Apache-2.0, open core.
core/,cmd/(thevaultfoldCLI, TUI, agent, MCP server, hooks), the file format and protocol specs,cloud/(hosted-service server code and the reference relay),scripts/anddocs/are all Apache-2.0. The single top-levelLICENSEfile holds the unmodified Apache License 2.0 text and the top-levelNOTICEfile identifies the copyright holder. - FSL-1.1-Apache-2.0, GUI applications. The future desktop, mobile and
browser-extension apps (
desktop/,ios/,android/,extension/) are licensed under the Functional Source License 1.1, Apache-2.0 future license (FSL-1.1-Apache-2.0), applied WinRAR-style as an honor system:- Free for personal use, family use, and teams of up to 5 members.
- Commercial use beyond a 5-member team requires a paid license.
- Enforcement is reminders only: the app never locks the vault or blocks a command. There is no telemetry in any component, so a reminder is computed only from local state (the member count of the open vault) and never from a phone-home check.
- License keys are offline: a signed blob verified locally, with no network call required to unlock the reminder.
- Each app directory gets its own
LICENSEfile carrying the FSL-1.1-Apache-2.0 text once that directory gains code; none of them exist yet, so no FSLLICENSEfile is added by this change. - The small-team (5-member) threshold and the honor-system license text are subject to legal review before the first app ships; this ADR records the intended shape of the terms, not final reviewed text.
- No telemetry, ever, in any component. No network call is made that the user did not ask for.
- Hosted service, paid, terms separate. The hosted sync and relay
service (enforced write policy, read audit log, compliance export, relay
with push notifications, device and membership directory; zero-knowledge
for secret values) is a paid service governed by its own terms of
service, separate from the source license of
cloud/'s Apache-2.0 code. The relay protocol and the reference relay implementation are open so that self-hosting is possible; push notifications require the hosted tier or the operator's own APNs/FCM credentials. - Payments: Polar (polar.sh) is the payment processor and merchant of record for team licenses and hosted subscriptions, so VAT and sales tax are handled by Polar. Polar offers a license-key benefit, but vaultfold issues its own signed license keys from a Polar order webhook so that verification stays offline and GUI applications never phone home.
- Copyright holder: Venn Labs LLC, for both layers.
Consequences
- Trust is preserved where it matters most for a security product: the code that reads and writes the vault format, and the daemon that holds key material, are fully auditable under Apache-2.0.
- The honor system needs non-OSS terms to be enforceable at all: an Apache-2.0 GUI could not carry a team-size condition, so the app layer needs FSL's source-available terms even though the core does not.
- Accepted cost: because the core, CLI and protocol are Apache-2.0, anyone can build and distribute a fully free competing GUI on top of them, bypassing the honor system entirely. This is accepted as the price of an auditable core rather than treated as a gap to close.
- Forks of the open components are expected and acceptable.
- Billing depends on a third party (Polar); the license-key format is ours, so a change of processor does not invalidate issued keys.
- Each app directory's FSL
LICENSEfile is added when that directory first gains code, not by this ADR; until then there is no FSL text in the repository. - The small-team honor-system clause is not yet legally reviewed; it may
change before the first FSL
LICENSEis added.
Alternatives considered
- Source-available license (BSL, FSL) for the entire codebase, including
core/andcmd/. Rejected: harms adoption and, more importantly, harms trust of a security tool whose format and cryptography need to be independently auditable. - Fully free (Apache-2.0 or similar) for the GUI apps too, with no team-size condition. Rejected: the honor system needs a license condition to attach a reminder to; an OSS license cannot carry a commercial-use restriction, so this would remove the mechanism the reminder depends on, not just the enforcement.
- Fully free with donations. Rejected: does not fund the hosted components.
- Forced paid tiers or feature gating in the CLI. Rejected: contradicts the honor-system approach and the open core.
Amendment: license revocation list
- Date: 2026-09-27
- Context: add-cloud-service group 7 (accounts and billing), ticket 01M3A20PVZYCJQZZ2FPV11CGS2, round 3 review finding R2, orchestrator DECISION: "a full refund revokes that order's license key by adding its id to a signed license revocation list that apps check when online".
License keys stay offline, as this ADR originally decided: Verify
performs no network call and a license keeps working with no
connectivity. That is unchanged. What this amendment adds is a second,
independent, best-effort check for the one case offline verification
structurally cannot see on its own: a refund happening after the license
was already issued and handed to a customer.
- A signed revocation list, not a phone-home check. The billing
module (
cloud/billing) publishes a signed license revocation list atPathLicenseRevocations, an unauthenticated endpoint, naming the license id of every fully refunded order. It is signed by the license signing key under its own context string (cloud/client/license.RevocationSignatureContext), never the capability token issuer key, so a license, a capability token and a revocation list can never be confused for one another. The encoding and anti-rollback rule (a list issued earlier than one already applied is refused) mirror the capability token revocation list (cloud/tokens.RevocationList) exactly, so the two mechanisms are reviewed and reasoned about the same way. - An application checks the list only when it is online, on its own schedule, the same way a relay or sync instance already polls the capability token revocation list; there is still no network call required to unlock a license offline, and no telemetry is added. An application that never goes online again keeps honoring a revoked license, which is accepted: this amendment narrows, rather than closes, the honor-system's existing gap for a customer who never reconnects.
- A partial refund revokes nothing. Only a full refund of the order that issued a license adds its id to the list; a partially refunded order's license and workspace stay entitled, and the event is recorded for the operator to review by hand.
- This does not change the FSL honor-system enforcement model for the GUI apps: it remains reminders only, computed from local state, never a lock or a blocked command. The revocation list only ever answers "does this billing module still stand behind this license", not "how many members are in this vault".