License

GNU Affero General Public License v3.0

PearlPBX2 is free and open-source software under AGPL-3.0-or-later. Here's what that means in practice.

In plain language

You may freely use, modify, and deploy PearlPBX2 for any purpose — including running your own commercial telephony business. There is no more exception for "competing" use.
If you deploy a modified version as a network service (for example, as SaaS for your own customers), you must offer the users of that service the complete corresponding source code of the exact version they are using.
When distributing copies — modified or not — you must keep the copyright and license notices intact and provide the source code, or a way to get it.
Derivative works may only be distributed under the same AGPL-3.0-or-later license — you cannot close off a fork and release it under different terms.
The software is provided "as is", with no warranty; the copyright holder's liability is limited to what the license text says.
Contributing to the project itself (not a fork) requires signing a CLA — it documents the provenance of each contribution and does not change the rights AGPL-3.0 already grants every user.

This is a short summary, not legal advice. The full text below is what governs.

Full license text

gnu.org/licenses/agpl-3.0.html · LICENSE on GitHub · CLA.md

Copyright license

The copyright holder grants you an unconditional license to use, study, run, and modify the software for any purpose.

Conveying source code

When you convey a copy of the program — on its own or as part of something larger — you must accompany it with the complete corresponding source code, or a written offer to provide it, and keep all copyright and license notices intact.

Network use (AGPL section 13)

This is what sets AGPL apart from plain GPL. If you modify PearlPBX2 and let users interact with it over a network — for example, by offering it as a hosted service — you must offer them a way to get the complete source code of the exact version they are using, even if you never handed them a single file directly.

Copyleft on derivative works

Any work that contains or is derived from PearlPBX2's code may only be distributed under the terms of AGPL-3.0-or-later. A fork cannot be relicensed under more restrictive terms.

No additional restrictions

You may not impose any further legal restrictions on recipients of the software beyond what this license already sets out.

Patent grant

Every contributor grants users a patent license covering their own contribution. If you bring a patent infringement claim related to the software, your rights under this license terminate.

Termination and reinstatement

Violating the license terms terminates your rights automatically. If the copyright holder notifies you of a violation for the first time, your rights are reinstated as long as you cure the violation within 30 days of that notice.

No warranty

To the extent permitted by law, the software is provided "as is", without any warranty, and the copyright holder is not liable for damages arising from its use.

CLA for contributions

To send a pull request to the PearlPBX2 project itself (not a fork), you need to sign a Contributor License Agreement — by commenting a fixed piece of text on your first PR. This gives the maintainer documented provenance for every contribution and does not change the rights AGPL-3.0 already grants every user.