Licensing and third-party attribution

Costs, commercial use, and distribution

The framework, official examples, and runtime components are free. No dedicated support service or response-time guarantee is offered.

Before commercial use or distribution, review project licenses, runtime notices, and the actual component/font/image licenses. Commercial use does not waive applicable source, copyright, or notice obligations. Names and logos follow separate branding rules. See GNU's official licensing FAQ.

License for project-owned code and documentation

Current notices license ACGGIT-owned source, documentation, examples, QA, build scripts, and maintenance tools under GPL-3.0-or-later, except separately licensed files/directories. Full terms ship with source; the standalone website retains GPL license text, Project notice and Third-party index.

Preserve applicable copyright/licenses, provide complete corresponding source and rebuild materials for GPL-covered binaries, mark modifications and dates as required, and add no conflicting restrictions. Even when an add-on ships only built web output, provide corresponding editable source, locked dependencies, and build scripts separately. The release's full license terms govern; this summary does not replace them.

GPL permits paid distribution under its terms. This project follows GPL-compatible distribution with an embedded framework and offers no proprietary exception or dual licensing. Private use without distribution does not require publishing source to everyone.

Read the full GNU GPL version 3. The project's own notice establishes or-later applicability; the license text alone does not.

Framework and runtime each carry notices

Preserve framework LICENSE, NOTICE.md, and applicable third-party notices when copying. Separately distributed runtime packages must include project licensing/runtime notices, the matching CEF license, and Chromium third-party records. A repository-wide summary does not replace package materials.

Windows packages also carry platform/dependency records. These responsibilities do not imply every locally built package is release-ready. See Package and deliver your add-on.

Third-party materials retain their licenses

Preserve licenses and sources for component libraries, icons, fonts, and images. Integration does not make them framework-owned; check the actual materials in your add-on.

Project-owned diagrams, illustrations, backgrounds, and logo graphics explicitly listed in notices may be modified/reused under GPL-3.0-or-later. Copyright permission for graphics does not grant trademark rights or endorsement. Other images, HDRs, and fonts retain their own notices.

Names, logos, and official affiliation

Nexus UI Web and ACGGIT are independent of the Blender Foundation and are not published, sponsored, or endorsed by Blender.

Blender names, logos, and community badges follow separate trademark/use rules. Software licensing does not grant trademark rights. Clearly identify your own project without implying affiliation. See Blender trademark policy and Logo and community badge guidance.

Start with these records after obtaining source

• Root LICENSE, NOTICE.md, and THIRD_PARTY_LICENSES.md: project scope and third-party index.
• Matching framework notices: redistribution and runtime boundaries.
• Skill and template LICENSE/NOTICE.md: retain them when extracting independently.
• Each example's THIRD_PARTY_LICENSES.txt: libraries, fonts, and assets actually included.
• Notices and matching source for the actual runtime package, not another version's records.

Framework source, official examples, and starter templates are available in the project's GitHub repository. Obtain matching framework and template versions before building. Runtime components are installed separately through the add-on's download card. Check licensing and attribution against the actual source, binaries, and third-party materials distributed.