Licensing
Dual-licensing protocol
Dual licensing protocol
AGPL-3.0 + Commercial vs Enterprise
| Capability | AGPL-3.0 + Commercial | Commercial Enterprise |
|---|---|---|
| Source code access | yes (full) | yes (full) |
| Modify and redistribute | yes | yes (subject to contract) |
| Production deployment | research only | yes |
| Closed-source distribution | no | yes |
| SLA / support | no | yes, 24/7 enterprise |
| GPU autoscaling deployment | no | yes |
| License-token issuance volume | unlimited test | contracted tier |
| Ed25519 key custody | self-managed | managed HSM optional |
| IPFS pinning service | self-hosted | managed |
| Audit attestations | community | SOC 2 + ISO 27001 (roadmap) |
| Indemnification | no | yes |
Every Rust crate and Python module in this workspace is published under the AGPL-3.0-or-later SPDX identifier (see LICENSING.md). Commercial enterprise agreements unlock production SLAs, managed infrastructure, and indemnification.
Commercial inquiries: shekhawatsamvardhan@gmail.com