Licensing and name
OpenAIIS separates open protocol adoption from any future commercial products or services. The grants below already apply and do not depend on buying anything.
| Material | Licence |
|---|---|
| Python reference implementation, local HTTP services, source tooling and code samples | Apache License 2.0 |
| Whitepaper V4.0 and Protocol V5.0 | CC BY 4.0 |
| The OpenAIIS name, marks and project branding | Separate; see below |
Reusing the documents
You may copy, share and adapt the whitepaper and protocol for any purpose, including commercial use. Name the work and its version, credit Tarun Sethi, link to the licence and say whether you changed it. For example:
Adapted from OpenAIIS Protocol, Version 5.0, © 2026 Tarun Sethi, licensed under CC BY 4.0. Changes were made.
Do not suggest the author endorses your changes, products or services. CC BY 4.0 covers copyright only. It grants no patent or trademark rights. The Apache 2.0 patent grant applies to contributions to the licensed software within that licence's terms; it is not a blanket patent licence for every independent implementation of the protocol.
Using the name
You can refer to OpenAIIS truthfully without asking: to identify it, credit its authors, describe compatibility with the protocol or compare another product with it. Neither licence lets a fork, product or service present itself as the official OpenAIIS project or release, as certified or endorsed by it, or as operated by its author when it is not. A separately branded fork should use its own name and visual identity while keeping the required attribution.
No trademark registration is claimed. Forks and independent commercial implementations remain permitted under their licences; this guidance does not restrict the copyright permissions above.