Our license
Updated
PRPOS uses the GNU Affero General Public License v3.0, usually called AGPL-3.0. You can use it in your shop, change it and host it yourself. The license keeps those freedoms available to people who receive the software or use a modified version over a network.
Why we chose it
We want repair shops to have a say in the software they rely on. That means being able to inspect the code, change what doesn’t fit and run it independently.
AGPL carries that freedom into modified versions, including hosted services. People using those versions can get the covered source and build on it. That fits a project we want shops to keep improving together.
What you can do
- Run PRPOS in a business, including your repair shop.
- Self-host it and adapt it to your workflow.
- Share copies and improvements under the license’s conditions.
- Charge for copies, hosting or support while meeting those conditions.
What you can’t do
AGPL allows reselling PRPOS, including modified versions. Those versions still have to meet the license’s source-sharing and user-rights requirements. You can’t:
- Distribute a closed-source edition of the covered PRPOS software.
- Withhold required source from people who receive the software or use a modified version over a network.
- Remove required copyright, license or warranty notices from copies you distribute.
- Add terms that prevent recipients from modifying or sharing the covered software under AGPL.
When source must be available
If you distribute PRPOS, preserve the required notices and license, identify your changes, and meet its source-sharing requirements. Recipients keep the rights to use, modify and redistribute the covered software.
If you modify PRPOS and let people use it over a network, give every one of those users a prominent way to download the complete corresponding source for that version at no charge. That can include staff using a modified installation over your shop’s network. The source includes the covered code and scripts needed to build, install, run and modify it.
You don’t have to send us a pull request or post it on a public GitHub repository to meet that requirement. The people entitled to the source can share it onward.
Separate programs that connect to PRPOS aren’t automatically covered. Whether an integration forms part of the covered software depends on how it is built and combined.
Your shop’s records
Using PRPOS doesn’t require you to publish customer details, repair tickets, sales records or your shop’s database. AGPL’s source-sharing rules concern the covered software.
How it fits our community
Sending improvements back to PRPOS is optional and welcome. If you want a change included in our hosted version, submit it for review. We check the code and affected workflows before merging; a contribution doesn’t guarantee inclusion.
Free core software and free hosting are our commitments. AGPL allows commercial services; it doesn’t require anyone to provide free hosting. Optional managed services may have separate costs, as explained on the PRPOS page.
Read the full license
This is a short explanation, not a replacement for the license or legal advice. The LICENSE file supplied with your copy of PRPOS governs that software. You can read the full AGPL-3.0 terms and the GNU licensing FAQ for more detail.