Vtiger Public License (VPL) is derived from the Mozilla Public License (MPL), a file-level copyleft license. It means that only files you modify from the original Vtiger source must remain open under the same license. Everything you build on top, such as new modules, themes, or integrations, can remain proprietary.
The VPL is designed to give you the best of both worlds: the freedom to use internally or build and sell your own solutions, while maintaining Vtiger’s open-source foundation as transparent and community-friendly.
OK:
Not OK:
You can freely use Vtiger Open Source within your organization for internal business needs — such as CRM, support, project management, or analytics — without any licensing obligations, as long as you’re not redistributing or selling it.
Put it simply:
However, if you want to sell or share the modified version with another company, this now counts as commercial distribution and must follow commercial use rules.
Commercial use means you’re using Vtiger Open Source to generate revenue — either by selling a modified version of the software, or by offering it as a hosted (SaaS) service.
You may modify and sell derivative products built on Vtiger Open Source under the following conditions:
You don’t need to open source:
OK: You customize Accounts.php and release it under VPL while keeping your new file, BillingAutomation.php, proprietary.
Not OK: You rename and market your product as “Vtiger CRM Professional Edition,” implying official affiliation or removing copyright headers.
You can host and sell Vtiger Open Source as a SaaS product. Because you’re not distributing the code, you’re not required to release your source modifications publicly.
However, you must:
OK: You offer “AcmeCRM Cloud,” built on Vtiger Open Source, with your own branding and design, while retaining Vtiger’s copyright notices.
Not OK: You host a Vtiger-based service and claim it’s “The Official Vtiger Cloud CRM,” or use Vtiger’s name and logo as your own brand identity.
Yes, you can rebrand the software with your own name and design. But you must not claim your version is the official Vtiger CRM, and you must keep Vtiger’s copyright and license notices in the code.
OK: You rebrand the software as ACME CRM and use your own logo, while retaining license headers.
Not OK: You delete copyright headers or claim “Built by ACME Inc.” That removes proper attribution.
You cannot make the original Vtiger files proprietary or change their license.
However, new files that you create — such as custom modules, APIs, or extensions — can remain closed source.
OK: You build a proprietary AI engine that connects to Vtiger via APIs—it can remain closed source.
Not OK: You modify Leads.php and keep it private — modified files must remain under VPL.
You only need to release your modified files if you distribute your version to others (for example, selling or sharing the software).
If you’re only offering it as a SaaS (hosted) service, you do not have to release your source code.
Allowed:
Not Allowed: You distribute modified Vtiger files and refuse to share them — this breaks the license.
Yes, you can combine open and closed components, as long as you keep the Vtiger parts under VPL and maintain clear separation.
OK: You integrate Vtiger with a proprietary mobile app. The app stays closed; the Vtiger base remains VPL.
Not OK: You merge Vtiger code into a private backend and distribute it without sharing modified files — this violates the license.
To respect Vtiger’s intellectual property and protect community trust:
You may not:
You may:
These guidelines govern naming conventions for partner and community solutions built on Vtiger CRM.
You can rebrand Vtiger CRM and offer it as your own solution, but it must clearly carry your brand name.
Correct:
Incorrect:
Plugin names should not include “Vtiger” at the beginning, except as a qualifier at the end.
Open Source software empowers innovation, collaboration, and freedom. We ask everyone in our community to use it responsibly and ethically.
Please: