Commercial use
Embed it in your product. Run it as a service. Make it yours.
Ship the forest inside what you sell, or operate it for your own customers, without opening your stack. One counterparty, written terms, and the engineering attention that comes with them.
The commercial license
What a commercial license unlocks
Closed distribution
Ship the Station, the Studio or the Clipper inside a proprietary product without publishing your source.
Managed offerings
Operate a modified Station as a service for your own customers, under your own terms.
Written, negotiated terms
A single copyright holder means an actual contract is possible, including field of use, term and territory.
Patent clarity
The engine already carries an explicit Apache-2.0 patent grant; the commercial agreement extends the same clarity to the AGPL-3.0 components.
Now the boring part
What AGPL-3.0 actually means here
Nothing about self-hosting. Everything about distribution and network use. Most teams that ask about licensing discover they need nothing at all, so here is the line, drawn plainly.
Running it internally
Free and unrestricted. An unmodified Station serving your own organisation triggers no obligation whatsoever: no notice, no publication, no license to buy.
Modifying it and serving it
Section 13 applies to network use: if you modify the Station or the Studio and let other people interact with it over a network, you must offer those users the corresponding source of your modified version.
Embedding it in a product
Distributing the Station, the Studio or the Clipper inside a closed product is what the copyleft prevents. The engine itself is Apache-2.0 and may be embedded freely: the line runs between `src/monkeyllm/` and `apps/`.
What comes with it
Governance, SLA and priority support
Support scope is agreed in writing with the license. Nothing on this page is a promise about your infrastructure’s availability, and no benchmark result is warranted on a corpus we have not seen.
- A response-time SLA sized to the deployment, down to four hours for critical incidents.
- A named engineer contact instead of a queue.
- Architecture reviews before you commit to a corpus shape or an ingestion policy.
- Upgrade planning and execution on your infrastructure.
- Scoping and audit design: levels, capabilities, branch scope and key rotation.
- Roadmap input, held to the same exit criteria the project publishes.
Qualified enquiry
Tell us what you are building
A person reads every one of these, and answers, usually within one business day.