License
©️ 2026 邱敬幃 Pardn Chiu. Agenvoy is licensed under the GNU Affero General Public License v3.0 and comes with absolutely no warranty, to the extent permitted by law. Full license text: LICENSE. Corresponding source, as AGPL-3.0 §13 requires: github.com/agenvoy/Agenvoy. This page is what the License entry under Settings > Other in the web interface opens.
Agenvoy is dual-licensed: AGPL-3.0 for open source use, and a commercial license for use that cannot meet the AGPL-3.0 source-disclosure requirement. Both cover the same software — the difference is what you owe in return.
For any commercial licensing need, contact the developer directly at dev@pardn.io — there is no reseller, no sales form, and no public price list; terms are agreed per engagement.
Which one applies to you
| Your situation | License |
|---|---|
| Personal use, research, evaluation | AGPL-3.0 — no action needed |
| Internal tool, not offered to users over a network | AGPL-3.0 — no action needed |
| You release your derivative work under AGPL-3.0, source included | AGPL-3.0 — no action needed |
| You offer Agenvoy, or a work derived from it, to users over a network without publishing your source | Commercial |
| You embed Agenvoy in a proprietary product you distribute | Commercial |
| Your organisation's policy prohibits AGPL in the delivered product | Commercial |
The deciding question is AGPL-3.0 §13: if users interact with a modified version over a network, that version's complete source must be offered to them. Running Agenvoy on your own machine, or inside your organisation without exposing it as a network service, never triggers it.
AGPL-3.0
The open source option is the GNU Affero General Public License v3.0, in the repository as LICENSE. You may use, modify and distribute Agenvoy, provided derivative works — and any network-accessible service built on it — are released under the same license with source included.
The project moved to AGPL-3.0 at v1.0.0. Everything in this documentation describes the AGPL-3.0 build; there is no feature held back for the commercial tier.
Required notices (AGPL-3.0 §7(b))
As section 7(b) permits, the LICENSE file carries one additional term, applying to Agenvoy and to every work based on it:
| Item | Detail |
|---|---|
| What must be preserved | The License and Source entries the web interface shows under Settings > Other |
| What they carry | The copyright notice, the warranty disclaimer, the statement that the work is AGPL-3.0, the means to view the license text, and the corresponding-source link §13 requires |
| What you may change | Their position and styling, provided they stay a convenient and prominently visible part of the interface |
| What you may not do | Remove, hide, disable, or otherwise make them inaccessible |
A commercial license obtained from the copyright holder removes this requirement.
Commercial license
Written up in full in COMMERCIAL.md. What it grants:
- Use, modify and distribute Agenvoy without the AGPL-3.0 source-disclosure obligation
- Embed it in closed-source products and hosted services
- Keep your own modifications private
- Remove the License and Source entries from the web interface, which the §7(b) additional terms below otherwise require you to keep
It does not transfer copyright, and it does not restrict anyone else's use of the AGPL-3.0 version.
What it does not include: the commercial license grants rights to the software only. It buys no time from the developer. Any work on the project requested from the developer is quoted and charged separately from the license fee — custom features, changes to existing behavior, bug fixes raised on your schedule, integration, deployment, migration, version upgrades, maintenance, a support commitment or SLA, and training are each a separate engagement, agreed and priced on their own. Holding a commercial license does not put a request ahead of anyone else's, and does not oblige the developer to take it on.
Pricing and terms depend on deployment scale and distribution model, and are agreed per engagement. There is no public price list.
Harness core source
Separately negotiable, outside the commercial license above: a one-time buyout of the harness core source.
| Item | Detail |
|---|---|
| What is sold | An unbranded harness core — the execution engine on its own |
| What is not included | The Agenvoy product and its trademark, and the pardnchiu/* modules it otherwise depends on |
| Version | Fixed at the latest release on the date of sale |
| After delivery | Yours to maintain. No updates, no upstream sync, and no tie to later Agenvoy or pardnchiu/* development |
| Fee | A single payment for the source as delivered, with no recurring fee. Development assistance from the developer is quoted separately, on the same terms as above |
Enquire at dev@pardn.io.
Getting a commercial license
Contact the developer directly — 邱敬幃 Pardn Chiu, the maintainer and sole copyright holder. Email dev@pardn.io with:
- Your organisation
- How Agenvoy would be deployed (hosted service, on-premise, embedded in a distributed product)
- Approximate scale (seats, instances, or end users)
- Any timeline you are working to
Contributions
Contributions are accepted under AGPL-3.0. Opening a pull request grants the maintainer the right to also distribute that contribution under the commercial license, which is what keeps the dual-licensing above available.
Third-party components
Agenvoy depends on external modules — go-llm-router, go-pkg, go-bot, go-browser, go-scheduler, go-sqlkit, the official MCP go-sdk, and others listed in go.mod — each under its own license. A commercial license for Agenvoy covers Agenvoy itself; the dependencies keep their own terms.
[!NOTE] This page summarises
LICENSEandCOMMERCIAL.mdin the repository. Those files are the binding texts; if they and this page ever disagree, they win.