Licensing | Living Eden Frameworks

Who this serves

Organizations whose records cannot leave their own environment: government program offices, state agencies, federally funded research centers, and institutions operating under sovereignty, classification, or regulatory constraint.

The constraint that usually stops structural analysis is not the analysis. It is that the corpus cannot be handed to a vendor. So the engine goes the other direction: it is delivered into the environment that holds the data, runs sealed inside it, and reports out only what the operator chooses to carry out. Nothing is uploaded to Living Eden Frameworks, and no run phones home.

Everything below describes how an organization reaches that deployment, and what Living Eden Frameworks will and will not agree to along the way.

What you're licensing

Before anything else, be precise about what you want. The LEF Engine is not one product. It is a portfolio of distinct, interlocking assets. Different assets have different terms. Conflating them creates confusion that tends to collapse deals that should have worked.

The substrate

Not licensable, not for sale. The LEF Ai meta-engine, the patent portfolio, the calibration corpus, and the running LEF engine builds themselves (Patents, Research Articles, Biology, future LEF-x) are the intellectual property of Living Eden Frameworks LLC. The substrate is what powers every deployment. It is not available for outright sale, acquisition, transfer, or sublicensing under any of the routes below.

Deployment surfaces

Licensable via the routes below. What customers can license is the operation of named deployments within defined fields of use, delivered as Private Enclave deployments. The license grants the right to use; it does not grant the underlying engine.

Inquiries framed as "acquire the engine," "purchase the Patents build," or "transfer the LEF Ai substrate" are declined by default. The substrate stays with Living Eden Frameworks LLC; only the routes below grant rights to operate on top of it.

Before any licensing or partnership discussion, both sides sign a mutual NDA, published openly and DocuSign-able.

How it deploys

One artifact, three settings, and the difference between them is reach rather than capability.

The shipped container is the product. It carries the engine and everything it needs to run: the analysis, the refutation stage, the calibration. It calibrates against your corpus inside your environment, with no connection back to Living Eden Frameworks. Where deployment provides durable storage, that calibration persists in your environment; it is never held by us.
Development and testing happen on our side, not yours. Features are built and exercised against our own instruments before any container ships. A partner receives a tested article, not a laboratory.
The hosted builds are proof, not the product. The public deployments exist so a prospect can watch the engine work on real public corpora before committing to anything. They run on bounded samples and say so on their own pages. The engine carries no such bound; the demo does, deliberately, so it stays responsive and cheap.

How to engage

Three doors, in the order they are usually taken. The builds are not sold as retail seats or self-serve subscriptions, and there is no checkout anywhere on this site. Every path below begins with a conversation and a human decision on both sides.

Try It. See what the engine produces before committing to anything. Each build offers a Request to Try: tell us what you’d run, and on a fit we send a Try-It code worth 2 runs, one-time, on the house. No commitment. When those runs are spent, the path forward is a field license or an Enclave — not buy-more retail.

Try Patents Try Research Articles Try Biology

Federal vehicles

Living Eden Frameworks is a registered small business and nontraditional defense contractor, and government work is the channel currently in pursuit. An organization does not have to arrive through a commercial license to reach the engine; the contracting routes below are open.

Other Transaction Authority. Cornerstone OTA member; the consortium membership agreement was executed 24 June 2026 and Living Eden Frameworks is award-eligible under it.
Broad Agency Announcements and open needs processes. White papers submitted directly to program officers, including AFOSR’s open BAA under Science of Information, Computation, Learning and Fusion, and the Defense Intelligence Agency’s NeedipeDIA, against a numbered agency need.
Solution marketplaces. Submissions under assessment across DoW and Intelligence Community marketplaces — CDAO Tradewinds, IARPA, and DARPA ERIS.
Commercial Solutions Openings. Registered under open CSOs including Golden Dome for America and the USSF Kronos Family of Systems.
SBIR / STTR and prize competitions, where the topic fits the instrument rather than the reverse.
Simplified acquisition. Government purchase cards accepted; pre-priced engagements under FAR Part 13 micro-purchase and simplified acquisition thresholds.

Where things actually stand. Submissions are under assessment. Three have cleared compliance review, which confirms only that a submission met the stated criteria and says nothing about how it will be assessed. There are no awards to date. That is stated plainly here for the same reason the engine reports leads rather than findings when a sample is thin: a claim you cannot support costs more than the silence it replaces.

UEI EZ5VPPFP6NV3 · CAGE 1A3A2 · SBC SBC_002678090 · NAICS 541715, 541511, 541512, 541519, 611710 · PSC D302, D316, AE16, R408. Full detail on the capability statement.

Start a conversation: TheArchitect@livingedenframeworks.com

Secure Enclave: the engine in your own environment

The substrate runs sealed inside your own confidential-compute environment (a Trusted Execution Environment), so neither your DevOps team nor the cloud provider can read it during execution. It begins with a mandatory paid Data Readiness Assessment and a partner-specific connector, under the Three-Layer IP structure; bring-your-own-AI applies.

For organizations whose data cannot leave their own environment.
Available under either field license; pricing is set to scope in conversation.
Optional bring-your-own-corpus: the engine traverses whatever graph your enclave exposes (e.g. international patent families, non-patent literature, or a dataset you already license).

Full terms: Exclusive / Non-Exclusive Field License · Schedule A, License Schedule · Schedule B (Brand Display Addendum).

Field License Active

The Enclave is how the engine is delivered. The field license is what you are permitted to do with it once it is there. Every deployment carries one.

Scope is a named program, not a market

A license grants the right to operate a named deployment — Federal ISB, Civic ISB, Patents, Research Articles, Biology — inside a defined program or product line, identified in the license schedule. Scope is written to a program a reader can point at, not to a market segment. A government program office licenses for its program; a company licenses for its product line.

This is deliberate, and it is the answer to the question a government buyer asks first: can this capability be locked away from us? No. Scoping to a program means a license cannot foreclose a market, an agency, or another program. Living Eden Frameworks continues to operate the substrate and every other deployment everywhere else, always.

What this looks like in practice

A government program office licenses the Federal ISB to read its own multi-source record inside its own boundary.
A state agency licenses the Civic ISB for a defined program area, and the collection tasks it emits go to that agency alone.
A federally funded research center licenses Research Articles for structural gap detection across a portfolio it already holds.
An institutional research platform licenses Patents for claim-level white space inside its own discovery product.

How it's structured

A one-time license fee plus a flat annual. No running royalty, on any route: the engine's output should not carry a meter into your program's budget. Figures are set to the scope of the program, in conversation.

Typical terms

Program or product line defined narrowly and precisely, and named in the schedule.
Successor programs: where a named program is renamed, restructured, or absorbed, scope follows the successor rather than lapsing.
No right to sublicense.
No right to assign without consent.
Perpetual license back to Living Eden Frameworks for any improvements the licensee makes, for use outside the licensed program.

Exclusivity, where it applies

Within a single named program, a license may be granted exclusively, so no competing party operates the same deployment inside that program. It is priced as a larger one-time fee plus a flat annual, and the annual maintains it: if the annual lapses, the license reverts to non-exclusive.

Exclusivity never extends past the named program. It does not reach a market, a domain, an agency, or any other program, and no exclusive is granted that would prevent Living Eden Frameworks from operating the substrate or any other deployment anywhere else. Full terms in the linked schedules.