The Open Source License for our WHMCS Addons, Payment Gateways and Security modules grants direct access to the complete source code and removes every requirement for license keys or outbound validation calls. It is a one-time purchase with no annual upgrade protection fees. Support is limited because the code can be modified by the customer.
These terms exist to balance developer freedom with intellectual property protection. The license is intended for teams with in-house engineering resources who need to inspect, extend, or harden the modules for production use. Review every restriction before purchase to avoid compliance issues later.
#What the Open Source License Provides
Full source visibility lets senior engineers audit logic, add custom hooks, alter payment flows, or integrate with internal tools without vendor involvement. Removing license checks eliminates external dependencies that can fail during network outages or in air-gapped environments. The one-time cost model gives budget predictability for organizations that maintain their own updates rather than relying on vendor release cycles.
In practice this license matters most when standard modules need deep changes to support unique billing models, extra fraud checks, or proprietary authentication. It shifts maintenance responsibility to your team but removes recurring license overhead and call-home latency.
#License Limitations
- You are allowed to use the purchased module on a single WHMCS installation at one time only. The module must be deactivated on any previous system before activation elsewhere.
- You are not allowed to share the module or any of its code, including snippets, with anyone outside of your organization. This rule covers contractors, partners, and public repositories.
- Limited technical support is provided for the module in its original form. No support is provided for modifications or for issues introduced by custom changes.
- All modules still require the ASPnix Licensing & Common system to function. The source for these files is not provided under the Open Source License.
#Support and Maintenance Expectations
Because the license explicitly permits modification, our engineers cannot troubleshoot problems caused by altered code. Keep the original unmodified source under version control and test changes in staging. This workflow lets you isolate whether an issue exists in the base module or in your extensions. Upgrade protection is not included, so you manage compatibility with new WHMCS core releases yourself.
#Common Pitfalls and Best Practices
- Deploying the same licensed copy on multiple live WHMCS instances simultaneously, which violates the single-installation rule and risks license revocation.
- Pushing modified code to public Git repositories or sharing snippets on forums, both of which breach the no-distribution clause.
- Expecting full support after extensive customization. Limit support requests to the supplied code only.
If your workflow requires frequent vendor updates or assistance with modified code, the standard licensed version with upgrade protection is the safer choice. Evaluate your team's capacity to maintain the modules long-term before selecting the Open Source option.
Contact our sales team with any questions or concerns about the Open Source License. They will provide clear answers and help confirm whether the license matches your intended use.
Comments
No comments yet