Legal
Non-commercial use is free. Commercial use requires a separate license. Three works are formally filed with the U.S. Copyright Office. This page contains the real terms — not a disclaimer, not boilerplate.
- Personal use
- Research use
- Educational use
- Hobby projects
- Open-source projects (non-commercial)
- Evaluation and testing
- Use in a product or service sold to customers
- Internal business tooling that generates revenue
- Bundling or redistribution in a commercial product
- SaaS, managed service, or hosted deployment
- Consulting or professional services use
- Any use where the primary intent is commercial gain
Commercial licenses available through the project site.
reiva.io →License terms
Grant of use (non-commercial)
Reiva is made available free of charge for personal, research, educational, hobby, and open-source non-commercial use. You may install and run Reiva on your own hardware for any of these purposes without payment or registration.
Restrictions
You may not use Reiva, in whole or in part, for any commercial purpose without obtaining a separate written commercial license from the rights holder. Commercial purposes include, without limitation: incorporation into a product or service offered for sale, internal use within a for-profit organization where the use contributes to revenue-generating activity, redistribution in commercial software, and deployment as part of a managed or hosted service.
Redistribution
You may share Reiva with others for non-commercial use provided that: (a) the software is distributed unmodified and intact as originally released, (b) this license notice accompanies the distribution, (c) no fee is charged for the distribution itself, and (d) the recipient is made aware of the non-commercial restriction.
Modification
Modifications to the Reiva source code for personal, research, or educational use are permitted. Distributing modified versions — whether publicly or within an organization — requires explicit permission from the rights holder. Modified versions may not be represented as the original Reiva software.
No warranty
Reiva is provided "as is" without warranty of any kind, express or implied. The rights holder makes no representations about fitness for a particular purpose, merchantability, or non-infringement. Use at your own risk.
Termination
Your right to use Reiva under this license terminates automatically if you breach any of its terms. Upon termination, you must cease all use and remove the software from your systems. The rights holder may also issue updates to these terms; continued use after such notice constitutes acceptance.
If you want to use Reiva in a commercial context — in a product, as internal business tooling, or as part of a service — you need a separate license. This is not an automated process. Contact the project through reiva.io to discuss terms.
Commercial licenses are available. They are not unreasonably withheld. The distinction exists to protect the integrity of the non-commercial free tier and to ensure that commercial use is properly scoped.
- A researcher using Reiva to study local AI authorization: free
- A developer building a personal home automation project: free
- A student writing a thesis on local-first AI architecture: free
- A hobbyist running it on their own machine for personal system management: free
- An open-source project building non-commercial tooling on top of Reiva: free (with redistribution notice)
- A startup embedding Reiva in a product they sell: commercial license required
- A company using Reiva internally to support revenue-generating operations: commercial license required
Copyright filings
Three works underlying Reiva's architecture are formally registered with the U.S. Copyright Office. These filings predate the public release of the software.
A five-clause formal definition of Automated Intelligence as an architectural class — distinct from Artificial Intelligence — including the authorization topology requirement, the automation/autonomy boundary, and the scope authorship model.
Filed: April 18, 2026. Registered before any public release of the software.
A whitepaper deriving the structural requirement for an authorization topology layer in open-scope AI systems. The theoretical basis for Reiva's per-intelligence authorization model and execution gate architecture.
Filed April 2026. SHA-256 (PDF):
4f09acc013b3137db2a5505f132d14860428a901cd1bdc79358479fe1c536841
An architectural specification for maintaining agent identity across session, platform, and instance boundaries — including the artifact-media basis for continuity, the structural conditions for cross-context re-identification, and the compositional model for persistent agent state.
Filed May 2026. Registered as a distinct architectural work independent of the software.
These registrations are real IP protection, not a formality. The works they protect are the theoretical foundations of the Reiva architecture. Unauthorized commercial use of the software, or derivative works that implement these architectures without license, infringes both the software copyright and the underlying theoretical work.
If you are uncertain whether your intended use is covered, contact us through reiva.io before proceeding. We would rather clarify than litigate.
Contact
For license inquiries, commercial use questions, or IP concerns, reach out through reiva.io. Please include a brief description of your intended use so we can respond meaningfully.
The project is maintained by Michael Gable (Reiva Research). We respond to substantive inquiries. We do not respond to abuse.