Licensing
License the core. Build the product.
This is where the commercial side lives. The rest of the site is about the engines; this page is about working together.
Framework Labs licenses its reasoning cores to companies building domain-specific products. You bring the domain, the product, and the customers. The lab provides the core underneath — and keeps developing it.
How licensing works.
You license a core as a component of your product. You own the product, the brand, the customers, and the domain expertise. The lab owns the core and continues to develop it.
This is the arrangement running in production today. Chiron's Forge builds a product on Concordia; Tenure Systems builds one on Continuum. Both are independent companies, and neither is owned by Framework Labs. A third core, Praxis, is in development and open to early conversations.
The structure is deliberate: the core improves over time and every licensee benefits from that improvement, while the things that make a product yours — the domain, the interface, the customer relationship — stay entirely with you.
The questions a technical buyer asks first.
Who owns the output the core produces?
You do. The core is the instrument; the results it produces inside your product are yours.
What is proprietary, and what do I get?
The core's internal reasoning, reconciliation, and verification logic stay proprietary to Framework Labs. You receive a documented, supported interface to the core and the right to build your product on it.
Where does it run?
Deployment is part of the conversation. We work through the options — including isolated and dedicated arrangements — against your security and compliance requirements, rather than offering a single fixed model.
What about my data?
Data handling is defined in writing, in the license, before anything is integrated. Your data is not routed anywhere it does not need to go.
Can I depend on it?
Support terms, update cadence, and reliability commitments are written into the agreement. The core is a dependency you are taking on, and the arrangement treats it that way.
What a license includes.
On performance claims.
The cores are under measurement in production, and the results are being prepared for independent peer review. We will share validation data directly in the course of a licensing conversation, and publish it once it has been reviewed.
We would rather tell you the numbers are in review than show you a figure we cannot yet defend. For a lab whose cores verify their own output before returning it, that is the only consistent position.
Who this is for.
Licensing makes sense if you are building a product whose core depends on machine reasoning you would otherwise have to build and maintain yourself — and if you would rather own your domain and your customers than own the core.
If that is your situation, the fastest way to find out whether there is a fit is a direct conversation.
Contact
Start a licensing conversation.
Tell us what you are building and which core it needs. We will tell you, plainly, whether there is a fit.
Contact the lab