Clear boundaries. Better evidence. No fake promises.
CommsOpen helps creators describe what is open source, what remains independently licensable, what a buyer declared, and which version of the terms they accepted.
Keep GPL rights intact.
Published scripts that use Blender’s Python API generally must be GPL-compatible. You may sell them, but buyers receive the corresponding GPL freedoms; personal-only or studio-only restrictions cannot be added to that covered code.
License what you created.
Artwork, .blend data, node-group libraries, media, templates, training, and other independent assets may have their own license when they are genuinely separate from the GPL-covered program.
Price ongoing value honestly.
Hosted APIs, cloud processing, collaboration, support, and future update delivery can be sold as services. Ending a service must not revoke rights to GPL code already conveyed.
How CommsOpen supports a personal/studio distinction
- The creator identifies each file, asset, service, and code component and its applicable license.
- Studio-tier terms attach only to separately licensable value, never to GPL-covered Blender code.
- The buyer provides legal name, organization, team size, seats, intended use, and an accuracy declaration.
- The selected tier, term version, fingerprint, declaration, and receipt become exportable evidence.
- A correction and upgrade path comes before escalation when the wrong tier was selected by mistake.
These records can clarify a dispute, but they cannot guarantee enforcement, replace legal counsel, or create rights the creator does not already have.
Official sources
Blender License · GNU GPL FAQ · GNU GPL v3 · SPDX License List · Creative Commons licenses
This guide is general educational information, not legal advice. Licensing outcomes depend on product architecture, distribution, dependencies, terms, and jurisdiction.