Closed-source distribution
Embed Kronroe in proprietary iOS, Android, desktop, or server apps without publishing your source code.
Ship Kronroe in your product without AGPL obligations.
The open-source release is AGPL-3.0. If your product cannot comply with AGPL (closed-source distribution, SaaS, embedded deployment without source disclosure), a commercial licence removes that constraint.
What the commercial licence includes
SaaS deployment
Run Kronroe server-side in a hosted product without triggering AGPL network-use provisions.
All crates included
The licence covers the full monorepo: core engine, agent memory, MCP server, Python bindings, iOS, Android, and WASM.
AGPL-3.0 vs commercial
| AGPL-3.0 (free) | Commercial | |
|---|---|---|
| Use in open-source projects | Yes | Yes |
| Internal use (no distribution) | Yes | Yes |
| Closed-source distribution | No — must share source | Yes |
| SaaS / network use | No — AGPL network clause | Yes |
| Embed in mobile apps | Must disclose app source | Yes |
| All features & crates | Yes | Yes |
| Priority support | Community only | Included |
Who needs this?
Teams shipping a product that embeds Kronroe and cannot (or prefer not to) release their own source under AGPL. Common cases:
- Mobile apps (iOS / Android) with embedded temporal graphs
- Enterprise tools with on-device AI memory
- Healthcare platforms with strict data residency
- SaaS products with server-side or on-device components
Pricing
Pricing depends on team size, distribution model, and use case. Reach out and we will send you terms that fit — no generic pricing page, because every deployment is different.
Frequently asked questions
Do I need a commercial licence for internal tools that aren't distributed?
No. AGPL obligations are triggered by distribution or network interaction with third parties. If Kronroe runs inside your organisation and is not exposed to external users, AGPL-3.0 is sufficient.
What counts as "distribution" under AGPL?
Distributing a binary or source to someone outside your organisation, or providing network access to AGPL-covered functionality (e.g. a SaaS product), both trigger AGPL obligations. Embedding Kronroe in an app on the App Store or Google Play counts as distribution.
Does the commercial licence cover future versions?
Yes. Commercial licences include all updates within the major version covered by your agreement. Upgrades to new major versions can be negotiated as part of renewal.
Can I evaluate Kronroe before buying a licence?
Absolutely. The AGPL-3.0 release is fully functional — same engine, same features. Use it freely for evaluation, prototyping, and internal development. You only need a commercial licence when you ship to external users under closed-source terms.
Is the open-source licence going away?
No. AGPL-3.0 is permanent. Commercial licensing exists alongside open source, not instead of it. Open-source users, contributors, and the community are unaffected.
What about Kindly Roe?
Kindly Roe (the iOS app by the project owner) has a perpetual irrevocable commercial licence that survives any future relicensing. This is documented in the repository.
Open source stays open
The AGPL-3.0 licence is permanent. Commercial licensing exists alongside open source, not instead of it. Open-source users, contributors, and the community are unaffected. Every feature available under the commercial licence is also available under AGPL-3.0.
Ready to talk?
Tell us about your use case and team size. We'll respond within two business days with terms that fit.