Free to self-host. Commercial if you need it.
z4j's default path is free, open source, self-hosted. Commercial licensing exists for orgs whose policies exclude AGPL. Same software, different license.
Open source
Self-hosted. Full feature set. AGPL-3.0-or-later brain, Apache-2.0 adapters. Run it on your own infrastructure.
- ✓ Every feature z4j has, no paywalled edition
- ✓ Unlimited projects, unlimited users, unlimited tasks
- ✓ Community support via GitHub Discussions
- ✓ Security fixes ship in the open-source release on the same day as any commercial release
- ✓ No telemetry, no 'phone home'
- ✓ No CLA. DCO (git commit -s) only
Commercial license
For organizations whose policies disallow AGPL. Same software, different license; keeps z4j's network-copyleft clause out of your compliance stack.
- ✓ Commercial (non-AGPL) license for the brain
- ✓ Agent packages remain Apache-2.0 (no license needed)
- ✓ Same software; no feature differences
- ✓ Priority bug reports
- ✓ Security embargo coordination
- ✓ Direct support channel, scope agreed per organization
Managed (cloud)
Hosted z4j on our infrastructure. Agents would still run in your cloud. Nothing is built yet: it is conditional on community traction, with no launch date and no committed feature set. Join the waitlist and we will tell you if it becomes real.
what we promise
License commitments
z4j offers a commercial license alongside the open-source one, so we spell these commitments out to avoid ambiguity.
- ✓
Every shipped release keeps its license permanently. No retroactive re-licensing.
- ✓
90-day announcement before any future license change, with public reasoning. Previous releases remain on their original license.
- ✓
No CLA. DCO sign-off only (git commit -s). You own your contributions.
- ✓
Security fixes ship in the open-source release on the same day as any commercial release, never delayed, never gated.
- •
We do not promise "free forever" or "no paid features ever," and we'll be honest about that. Shipped versions stay shipped; future commercial features are a possibility we'll announce transparently.
Questions about licensing?
We answer AGPL questions in plain English. No legal boilerplate.