Licensing
Compare AGPLv3 use with Startup, Growth, and Enterprise commercial rights, and the steps to associate a commercial license with one legal entity and named product.
The complete SDK is available under AGPLv3 or a separate commercial agreement.
| License | Intended use | Fulfillment |
|---|---|---|
| Community | Products that can comply with AGPLv3 | No fee |
| OpenE2EE — Startup Commercial License | One proprietary product and legal entity | Public self-service, $5,000/year |
| OpenE2EE — Growth Commercial License | Configurable product scope, support, and services | Quote and signed order form, from $20,000/year |
| OpenE2EE — Enterprise / OEM Commercial License | Portfolio, redistribution, OEM, security, and SLA terms | Negotiated MSA or order form, from $50,000/year |
The current published SDK license plans cover @open-e2ee/signal-protocol-sdk. The controlling agreement must explicitly grant rights to any future component family, such as open-e2ee-client-sdks-v1.
The signed agreement controls
This documentation summarizes the model and is not legal advice. The repository license or executed commercial agreement controls the actual grant.
Buying a Startup license
The Startup commercial license covers one named product owned by one legal entity. Checkout records both values, the sdk_license_startup_v1 plan, and the licensed @open-e2ee/signal-protocol-sdk component before it issues a downloadable license record.
- Sign in to the console.
- Choose the Startup license.
- Enter the exact legal entity and covered product name.
- Review and accept the commercial agreement.
- Complete annual Stripe Checkout.
- After the payment webhook passes its check, download the license record.
Growth, Enterprise, and OEM scopes require a meeting. An order form must describe support, additional products, redistribution, or portfolio rights.
The record is signed with Ed25519 and can be checked offline against a published key: see verify a license record.
The agreement is the authority
The downloadable record summarizes the current Stripe entitlement and accepted terms. Its signature proves origin and integrity. It is not an enforcement token and does not replace the executed commercial agreement.
No SDK phone-home requirement
The portable SDK does not need to contact the licensing console during normal cryptographic operation.
See pricing or purchase Startup.
Security and protocol policy
Spec revision pins, post-quantum policy defaults, the deliberate divergence from Signal Messenger, the identity trust model, audit status, and the responsibility split.
Verify a license record
Check the Ed25519 signature on a downloaded license record offline, against the public key published here.