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

LEF licenses builds, each made from Engine Core, and now also from Verification, for one named program. The builds and Test Data available today are proofs of concept; this page is about how a licence for one is set up.

What is never transferred

Ownership. Anything Living Eden Frameworks LLC produces stays its own: no ownership right in any of it passes to another person or entity, under any route below. The one exception is a fork or change to a build, which can pass only under a contract signed by LEF and the licensee. A licence grants the right to use, never ownership. What a build produces when ran on a users records, in their environment, is theirs.

What you receive and may use

A build, in a container. The tool and the engine scaled to it, working together in your environment, delivered with its handover documents. Every build ships with its baseline library as standard, filled to a working level measured for that build in test, as a dated snapshot: you can switch it off, we never update it after delivery, and your own runs grow it. An empty library means weaker results on day one. The licence grants the right to use all of it. It does not transfer ownership of any of it.

Before confidential information is exchanged with a non-government party, both sides sign the mutual NDA, published openly and e-signable.

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

The 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.

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 licensing conversation to reach the engine; the contracting routes below are open.

Broad Agency Announcements and open needs processes. White papers to program officers, including AFOSR’s open BAA, AFRL, NRL and DLA announcements, and the Defense Intelligence Agency’s NeedipeDIA, against a numbered agency need.
Solution marketplaces. Submissions under assessment at IARPA and DARPA ERIS, and in the ONIX OTA marketplace.
Commercial Solutions Openings. Submitted under Golden Dome for America, ERDC ITL and NIWC Pacific UNACORN, and a Research/Solution Brief to the FAA’s Research and Commercial Solutions Opening (RCSO); registered for the USSF Kronos Family of Systems.
SBIR / STTR, where the topic fits the instrument rather than the reverse.
Grants and cooperative agreements. Proposals in at NSF and IES.
Simplified acquisition. Government purchase cards accepted (set up with the buyer at award); pre-priced engagements under FAR Part 13 micro-purchase and simplified acquisition thresholds.

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

Secure Enclave: your build in your own environment

Your build runs sealed inside your own confidential-compute environment: neither your own administrators nor the cloud provider can read it while it runs, and it reaches nothing beyond the hosts its build names. Before it starts, it proves which image it is and reads its licence from your vault by name. Every build is delivered this way; the Field License below is what you may do with it.

For organizations whose data cannot leave their own environment.
Available under the Field License; pricing is set to scope in conversation.

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

Field License Active

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

A license is scoped to one named program

A license grants the right to operate one named build 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 engine and every other build everywhere else, always.

What this looks like in practice

A government program office licenses a build to read its own multi-source federal record inside its own boundary.
A state agency licenses a build for a defined program area, and the collection tasks it emits go to that agency alone.
A federally funded research center licenses a build for structural gap detection across a portfolio it already holds.
A program office licenses a build to check its own specifications and datasets before anyone relies on them.

How it's structured

Fee structure follows the agreement. A field license is typically a one-time fee with a flat annual; work funded through a grant, contract or other funded instrument is structured to that instrument instead, usually as milestones. No running royalty, on any route. 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.
Any fork or change to the build, made by either side, belongs to Living Eden Frameworks, unless otherwise agreed in a contract signed by LEF and the licensee.

Exclusivity, where it applies

Within a single named program, a license may be granted exclusively, so no competing party operates the same build inside that program. This matters where more than one party works inside the same named program — several primes on one effort, or multiple vendors under one contract — and it means the licensee is the only one running that build there. It is priced as a larger one-time fee plus an annual exclusivity premium, and the premium maintains it: if the premium lapses, the license reverts to non-exclusive and continues.

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 engine or any other build anywhere else. Full terms in the Field License, §2.4.