# Commercial License

## mcp-postgres — Commercial Licensing

This project is dual-licensed:

1. **Open Source** — [GNU Affero General Public License v3.0 (AGPL-3.0)](LICENSE)
2. **Commercial** — Available for organizations that cannot or prefer not to comply with AGPL-3.0 terms

## When You Need a Commercial License

The AGPL-3.0 requires that if you modify this software or use it as part of a network service, you must make the complete source code of your application available under the AGPL-3.0. A commercial license removes this requirement.

You likely need a commercial license if:

- You integrate mcp-postgres into a **proprietary product or service**
- You offer mcp-postgres as part of a **managed or SaaS platform** without releasing your source code
- You **modify** the software and do not want to release your modifications under AGPL-3.0
- Your organization's **legal or compliance policies** prohibit use of AGPL-licensed software

## When You Do NOT Need a Commercial License

- **Personal or non-commercial use** — using the software for personal projects or non-commercial purposes
- **Open-source projects** — integrating with other AGPL-3.0 or compatible open-source projects

## Obtaining a Commercial License

Contact us to discuss commercial licensing options:

- **GitHub Sponsors**: <https://github.com/sponsors/itunified-io>

Commercial licenses are priced based on scope and usage. Sponsoring the project through GitHub Sponsors is the primary way to support development and obtain commercial terms.

## FAQ

**Q: Can I use mcp-postgres for free in my company?**
A: If your company uses mcp-postgres internally as part of commercial operations, you need either full AGPL-3.0 compliance (which means releasing your complete source code under AGPL-3.0) or a commercial license. Free use under AGPL-3.0 is intended for open-source and non-commercial purposes.

**Q: Does the AGPL apply if I just run the MCP server internally?**
A: Running the server internally within a commercial organization still means you are subject to the AGPL-3.0 license terms. If your organization cannot comply with AGPL-3.0 (e.g., releasing source code of any modifications or derivative works), you need a commercial license.

**Q: What if I build a product that includes mcp-postgres?**
A: If your product is proprietary (closed-source), you need a commercial license. If your product is also AGPL-3.0 licensed, you can use it under the open-source license.