# License ## Licensing Qpoint is available under two licensing options: 1. **GNU AGPL v3** - A free license for open source applications 2. **Commercial License** - For commercial and enterprise use ### GNU AGPL v3 License The GNU Affero General Public License v3 (AGPL v3) is designed for developers building open source applications. This license is fully featured but requires compliance with specific terms: * If you distribute, host, or create derivative works of Qpoint.io over a network, you **must distribute the complete corresponding source code** of the combined work under the same AGPL v3 license. * This requirement applies whether or not you modified Qpoint. You can view the full license at . ### Commercial License The commercial license is designed for: * Organizations that cannot or do not want to comply with AGPL v3 terms * Environments requiring enhanced functionality: * Advanced pre-encryption language support * PII Scanning * Control Plane features * Enterprise support and SLA's Our Qpoint Pro Agent offering includes both the commercial license and these enhanced features. For pricing and details, please [contact our sales team](https://qpoint.io/#request-demo). ### GPL-Licensed Components Qpoint includes eBPF programs that are licensed under GPL-compatible terms as required by the Linux kernel. While the main Qpoint application remains under the licensing terms described above, these eBPF components are subject to GPL requirements. **Source Code Availability**: The complete source code for all GPL-licensed eBPF components is available upon request. You may obtain this source code for a period of **three years** after our distribution of the software, with the earliest request date being **April 16, 2025**. **How to Request**: To request the GPL-licensed source code, please contact our legal compliance team at: * **Email**: * **Subject Line**: "GPL Source Code Request" * **Include**: Your name, organization, and the specific Qpoint version/release We will provide the source code at no charge beyond reasonable handling costs. This offer is valid for any party who has received Qpoint commercial software containing these GPL-licensed components. **License Terms**: The eBPF source code is provided under GPL licensing. The complete license text is included with the source code distribution. ### Understanding License Compliance #### What constitutes a derivative work? Creating combined or derivative works of Qpoint requires releasing all such works under the AGPL v3 license, unless you have a commercial license. Examples of combined works include: * Including Qpoint source code in the same executable file * Modules designed to run linked together in a shared address space The following are typically considered separate programs: * Communication via pipes, sockets, or RESTful APIs * Command-line arguments between separate programs However, if the communication exchanges complex internal data structures, this might still be considered a combined program. #### What is not affected? Merely aggregating Qpoint.io into your distribution does not constitute a derivative work. ### Recommended Actions 1. **Review Your Usage**: Determine how your application interacts with Qpoint 2. **Consult Legal Counsel**: If you have questions about compliance, we recommend consulting your attorney 3. **Consider Commercial Licensing**: Purchasing a commercial license removes AGPL v3 obligations for Qpoint.io For additional guidance, we recommend reviewing the [Free Software Foundation's interpretation](https://www.gnu.org/licenses/gpl-faq.html) of the GNU AGPL v3 license.\ \ \\ --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.qpoint.io/license.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.