Current section
Files
Jump to
Current section
Files
LICENSE
# Pubflow License
**Company:** Pubflow, Inc.
**Primary License:** AGPL-3.0 (GNU Affero General Public License v3.0)
**Alternative License:** Commercial License (available for purchase)
**Contact:** enterprise@pubflow.com
---
## π Primary License: AGPL-3.0
Pubflow is licensed under the **GNU Affero General Public License v3.0 (AGPL-3.0)**.
### What is AGPL-3.0?
AGPL-3.0 is a **strong copyleft** open source license that:
- β
Allows **free commercial use**
- β
Allows **modification** of the code
- β
Allows **distribution** of the software
- β
Allows **private use**
- β οΈ Requires **source code disclosure** if you modify and offer as a web service
- β οΈ Requires **same license** for derivative works
- β οΈ Requires **license and copyright notice** preservation
### Key Points
**You CAN:**
- β
Use Pubflow commercially (in your business)
- β
Use Pubflow in your SaaS application
- β
Modify the source code
- β
Distribute the software
- β
Use for private/internal purposes
**You MUST:**
- β οΈ Disclose source code if you modify and offer as a network service
- β οΈ License derivative works under AGPL-3.0
- β οΈ Keep license and copyright notices
- β οΈ State significant changes made to the code
**You DON'T need to:**
- β Release code if you just USE Pubflow (without modifications)
- β Release code for internal/private use (even if modified)
- β Release your business logic or application code
- β Pay anything (AGPL is free)
---
## π Full License Text
The complete AGPL-3.0 license text is available at:
- **Official Source:** https://www.gnu.org/licenses/agpl-3.0.en.html
- **SPDX:** https://spdx.org/licenses/AGPL-3.0-only.html
- **GitHub:** https://github.com/pubflow/pubflow/blob/main/LICENSE
### License Header
All Pubflow source files include this header:
```
Copyright (C) 2024-present Pubflow, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published
by the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
```
---
## πΌ Alternative License: Commercial License
For organizations that cannot or do not want to comply with AGPL-3.0, we offer a **Commercial License**.
### Why Choose Commercial License?
**You need a Commercial License if:**
- π° You want to modify Pubflow and keep changes private
- π° You're creating a competing PaaS service
- π° Your company has anti-AGPL policies
- π° You need enterprise support and SLA
- π° You need legal indemnification
### What's Included
- β
**No AGPL obligations** - Keep modifications private
- β
**Enterprise support** - Priority support with SLA
- β
**Legal protection** - Indemnification clause
- β
**Custom features** - Request features for your use case
- β
**Training** - Team training and onboarding
### Pricing
**Custom pricing based on your needs.**
**Contact:** enterprise@pubflow.com for a quote.
**Learn more:** [Commercial License Details](https://pubflow.com/dual-licensing)
---
## π― Dual Licensing Model
Pubflow uses a **dual licensing model**:
```
Pubflow Software
βββ License Option 1: AGPL-3.0 (Free)
β β
Free forever
β β
Open source
β β
Commercial use allowed
β β οΈ Must release modifications if offering web service
β
βββ License Option 2: Commercial License (Paid)
β
Keep modifications private
β
No AGPL obligations
β
Enterprise support
π° Custom pricing (contact us)
```
**You choose which license works best for your use case.**
---
## π License Compliance
### How to Comply with AGPL-3.0
If you modify Pubflow and offer it as a web service, you must:
1. **Keep License Notices**
- β
Keep all copyright notices
- β
Keep all license headers
- β
Include AGPL-3.0 license text
2. **Disclose Source Code**
- β
Make source code available to users
- β
Include installation instructions
- β
Provide access for at least 3 years
3. **Document Changes**
- β
Document significant changes (CHANGELOG.md)
- β
Mark modified files
- β
Include modification dates
4. **Provide Notice**
- β
Display notice in your service UI
- β
Link to source code repository
- β
Include AGPL-3.0 license
**Example notice:**
```
This service uses Pubflow software.
Source code: https://github.com/yourcompany/pubflow-fork
License: AGPL-3.0
```
### How to Comply with Commercial License
If you purchase a Commercial License:
1. **Pay License Fee**
- π° Monthly or annual subscription
- π° Based on number of developers
2. **Follow Terms**
- β
Use within agreed scope
- β
Don't redistribute source code publicly
- β
Don't sublicense to competitors
3. **Maintain Subscription**
- β
Keep subscription active
- β
Renew annually
- β οΈ Revert to AGPL if cancelled
---
## β Frequently Asked Questions
### Can I use Pubflow for free?
**YES!** Pubflow is free under AGPL-3.0. You can use it commercially without paying anything.
### Do I need to open-source my entire application?
**NO!** You only need to release modifications to Pubflow's code, and only if you offer it as a web service. Your business logic stays private.
### What if I just use Pubflow without modifying it?
**No obligations!** If you use Pubflow without modifications, you don't need to release any code.
### Can I use Pubflow in a closed-source product?
**YES!** As long as you don't modify Pubflow's code. If you do modify it and offer as a web service, you need to release those modifications or purchase a Commercial License.
### What counts as "offering as a web service"?
Providing access to Pubflow over a network to other users (SaaS, API service, cloud hosting). Internal company systems don't count.
### How do I purchase a Commercial License?
Contact **enterprise@pubflow.com** for pricing and terms.
---
## π Additional Resources
### Documentation
- π [License FAQ](./LICENSE-FAQ.md) - Detailed Q&A about licensing
- π [Commercial License](./COMMERCIAL-LICENSE.md) - Commercial license details
- π [License Comparison](./LICENSE-COMPARISON.md) - AGPL vs Commercial comparison
- π [Examples](./EXAMPLES.md) - Real-world code examples
### Legal
- π [AGPL-3.0 Full Text](https://www.gnu.org/licenses/agpl-3.0.en.html)
- π [SPDX License Info](https://spdx.org/licenses/AGPL-3.0-only.html)
- π [OSI Approval](https://opensource.org/licenses/AGPL-3.0)
### Support
- π¬ [GitHub Discussions](https://github.com/pubflow/pubflow/discussions)
- π¬ [Discord Community](https://discord.gg/pubflow)
- π§ [Enterprise Support](mailto:enterprise@pubflow.com)
---
## π Contact
### Licensing Questions
- π§ **Email:** enterprise@pubflow.com
- π **Website:** https://pubflow.com/dual-licensing
- π **Request Consultation:** https://pubflow.com/contact
### Commercial License Sales
- π§ **Email:** enterprise@pubflow.com
- π **Request Quote:** https://pubflow.com/dual-licensing
---
## βοΈ Copyright
**Copyright Β© 2024-present Pubflow, Inc.**
All rights reserved under the terms of the AGPL-3.0 license or Commercial License.
---
## π License Identifier
**SPDX-License-Identifier:** AGPL-3.0-only
---
**Pubflow, Inc.** - Building the future of backend development.
*Last Updated: 2025-12-14*