Licensing
Dual-licensing protocol
Dual licensing protocol
Apache 2.0 vs Commercial Enterprise
| Capability | Apache 2.0 | Commercial Enterprise |
|---|---|---|
| Source code access | ✓ full | ✓ full |
| Modify and redistribute | ✓ | ✓ (subject to contract) |
| Production deployment | ⚠ research | ✓ |
| Closed-source distribution | ✗ | ✓ |
| SLA / support | ✗ | ✓ 24/7 enterprise |
| GPU autoscaling deployment | ✗ | ✓ |
| 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 | ✗ | ✓ |
Every Rust crate and Python module in this workspace is published under the Apache-2.0 SPDX identifier (see omnipulse-rs/Cargo.toml:16). Commercial enterprise agreements unlock production SLAs, managed infrastructure, and indemnification.
Commercial inquiries: shekhawatsamvardhan@gmail.com