How to contribute to Seitiate, what the AGPL-3.0 means in practice, and how the project thinks about commercial products, ownership, and portability.
We welcome builders, developers, and researchers who want to improve the engine. The best place to start is the public repository, where you can review the code, open issues, and propose pull requests.
If you want to contribute, start with the repository documentation and contribution guidance that ships with the codebase.
OPEN THE REPOSITORY →Seitiate is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). In practical terms, if you modify the engine and make that modified version available over a network, the AGPL generally requires you to provide the corresponding source code under the same license.
The license is meant to keep the core engine open rather than allowing someone to privatize the engine layer while still benefiting from the community's work.
Yes. A commercial product can be built on top of Seitiate, provided you comply with the AGPL-3.0 or enter into any separate commercial arrangement that may apply to your use case.
Charging for managed compute, storage, governance, managed environments, operations, support, or user experience is compatible with the project boundary. The engine and the product experience are not the same thing.
Our position is that products may charge for service and experience without claiming ownership of the person's work. We also reject lock-in through inaccessible derived context. If a hosted product is built on Seitiate, portability and export should remain part of the product boundary rather than being withheld indefinitely behind payment.
The open-source license is a current legal reality. So is the project's public position that users should retain ownership of their content and that portability matters.
By contrast, the exact mechanics of exports, hosted-product safeguards, stronger encryption guarantees, or provenance features may vary by implementation and may still be evolving. Those details should be documented in the relevant product or repository materials rather than assumed from this page alone.
Hosted-product contracts, data-processing terms, enterprise security representations, and any product-specific ownership or portability language should still receive formal legal review before being treated as finalized public commitments.