Licensing
Public RetroFuse software releases are intended to use the GNU Affero General Public License v3.0, with commercial licensing available when AGPLv3 obligations do not fit a deployment or integration.
Public License
The AGPLv3 keeps source availability attached to networked and service-style use. That matters for RetroFuse because many modules are built to operate as ongoing infrastructure rather than one-time scripts.
The license text controls. This page is a practical explanation, not legal advice and not a substitute for the license itself.
Commercial Use
Commercial licensing is available for private deployments, proprietary internal use, redistribution, hosted/service operation, or integrations that cannot comply with AGPLv3 source-sharing obligations.
Contact Flow
For commercial licensing, include the product of interest, intended deployment, whether it will be redistributed or hosted, and any integration constraints.
Brand Boundary
Open-source availability does not grant permission to imply endorsement, ownership, or official RetroFuse status for modified products or services.
Commercial Contact
Send licensing inquiries to [email protected]. Include enough deployment detail to determine whether AGPLv3 is sufficient or a separate commercial license is appropriate.
Commercial Acceptance
Commercial access requires acceptance of the applicable RetroFuse Commercial License Terms before download, private delivery, hosted access, support, or proprietary-use permission.
Acceptance may be recorded by signed agreement, purchase order referencing the license, approved commercial request form, or written email confirmation from an authorized representative.
RetroFuse may require name, organization, email, product/version, license type, timestamp, and accepted terms version before providing commercial download access.
Release Rule
RetroFuse will keep the public release language explicit: what is open, what is commercial, what is only observed environment state, and what belongs to a separate product lane.