License Agreement
Vibrante-Node uses an open-core model — the runtime and SDK are open source, enterprise components and official plugins require a commercial license.
License Comparison
Different components of Vibrante-Node are governed by different licenses.
| Component | License | Free Use | Commercial |
|---|---|---|---|
| Core Runtime | AGPLv3 | Free | AGPLv3 / MIT terms apply |
| SDK / Public API | MIT | Free | AGPLv3 / MIT terms apply |
| Documentation & Examples | CC BY 4.0 | Free | AGPLv3 / MIT terms apply |
| Official Plugins & Nodes | Commercial | See commercial terms | License required |
| Enterprise Integrations | Commercial | See commercial terms | License required |
Open-Core Architecture
The foundation is free and open. Enterprise features are commercial.
Free Forever
- Individuals
- Students & educators
- Academic research
- Open productions
- OSS contributors
Commercial License
- Studio pipeline deployments
- Client production work
- SaaS / cloud hosting
- Proprietary node packs
- Render farm integration
Enterprise
- Multi-studio deployment
- OEM / product embedding
- Priority support
- Custom integrations
- Negotiated SLA
AGPLv3 — Core Runtime
The execution engine, canvas, and application shell are licensed under the GNU Affero General Public License v3.
You can
- Use for any purpose, including commercial
- Study and modify the source code
- Distribute copies of the software
- Distribute modified versions
- Run privately without disclosure
You must
- Disclose source of distributed copies
- Preserve copyright and license notices
- License modifications under AGPLv3
- Publish source if running as a network service for others
- State changes made to the original
MIT — SDK & Public API
The BaseNode class, public node interface, and utility helpers are MIT-licensed to allow closed-source node development.
The MIT License applies to the public SDK surface — specifically src/nodes/base.py, src/utils/, and the node definition interface. You may build proprietary nodes and pipelines against this API and distribute them commercially without disclosing your source code.
Commercial Licensing
Free for individuals, education, and open productions. Commercial studio deployment requires a license.
Studio Pipeline
Single studio entity — unlimited seats, render farm nodes, artist workstations, and internal pipeline tools.
SaaS / Cloud
Hosting the runtime as a networked service accessible to third parties, including cloud render orchestration.
Proprietary Nodes
Building and distributing closed-source node packs or plugin libraries that extend Vibrante-Node.
Enterprise / OEM
Embedding Vibrante-Node inside a commercial product, multi-studio deployments, or custom integration agreements.
Pricing
Commercial licenses are negotiated per engagement based on studio size, deployment scope, and geography. Contact m.kamalvfx@gmail.com to request a quote. Include studio name, seat count, and intended deployment scope.
Enterprise & Render Farm Usage
Enterprise deployments — including multi-studio networks, cloud render farm orchestration, and OEM product embedding — are covered by individually negotiated enterprise agreements.
Enterprise license holders receive priority support, access to pre-release builds, and the option to negotiate custom integration assistance.
Render farm nodes running Vibrante-Node automation scripts as part of a commercial rendering operation require at minimum a Studio Pipeline license.
Official Plugins & Node Packs
Officially maintained DCC integrations and curated node packs are distributed under commercial terms.
The Houdini Bridge, Maya Headless Executor, Blender Headless Executor, Prism Pipeline integration, and Deadline connector are officially maintained components. While the open-source runtime they run on is AGPLv3, the curated plugin packages and enterprise node libraries require a commercial license for studio deployment.
Third-party developers may build and distribute their own plugins against the MIT SDK without restriction. Naming must follow the Trademark Policy.
Trademark Policy
Guidelines for using the Vibrante-Node name and logo.
Permitted ✓
- "[Plugin] for Vibrante-Node"
- Factual articles and tutorials
- "Compatible with Vibrante-Node"
- "Tested on Vibrante-Node v2.0.0"
- Conference talks and academic papers
Prohibited ✗
- "Vibrante-Node [Anything]" — implies official origin
- Logo modification or recolouring
- Domain names containing vibrante-node
- Implying official endorsement
- Merchandise without permission
Contributor License Agreement
By submitting a pull request you automatically accept the CLA.
You Retain Copyright
Your contribution remains your intellectual property. The CLA grants the project a license to use it, not ownership.
Dual-License Grant
Your contribution may be included in both the open-source AGPLv3/MIT releases and commercial releases of Vibrante-Node.
No Compensation
Contributions are voluntary. The CLA does not entitle contributors to financial compensation from commercial sales.
License File Locations
Frequently Asked Questions
Can I use Vibrante-Node for personal projects?
Yes. Individual use — whether for personal projects, portfolio work, or skill development — is free under the AGPLv3.
Can I use it at a commercial studio without paying?
Studio pipeline deployment — including multi-seat installations, render farm automation, and client production work — requires a commercial license.
Does the AGPLv3 require me to open-source my pipeline?
If you run a modified version of the core runtime as a networked service and let others interact with it, you must publish your modifications. Private internal use without network distribution does not trigger this obligation.
Can I build closed-source nodes with the SDK?
Yes. The SDK (BaseNode, public node API) is licensed under MIT, which allows building proprietary nodes and integrations without publishing source. Distributing those nodes commercially requires a commercial license.
How do I become a contributor?
Submit a pull request. By doing so you automatically accept the CLA, which lets the project dual-license your contribution while you retain copyright ownership.
Can I use the Vibrante-Node name in my plugin?
Yes, with the form "[YourPlugin] for Vibrante-Node". You may not use "Vibrante-Node [Anything]" as it implies official origin. See the Trademark Policy for details.
Questions about licensing?
For commercial licensing inquiries, trademark permissions, or enterprise agreements, contact the author directly. Include your studio name, deployment scope, and start date.