Semantic Gravity Fields are licensed to teams building products where memory is the ceiling. You get the integration, the fidelity dial, and lenses, held to a budget you set. The mechanism behind the field stays private, so you build on it without carrying it.
There is no one price on a wall, because a rack deployment and an embedded product are not the same license. A license is scoped to the shape of your deployment: where the field runs, how it is sized, and how it reaches your users.
Every license names the same fields. Change the scope and the terms change with it, agreed under NDA once a pilot has shown the field on your workload.
Illustrative schema. Terms are finalised with pilot partners under NDA.
Each tier is a different shape of deployment, not a different product. The same field, sized and priced to how you ship it.
A scoped, time-boxed engagement on one of your workloads. You bring a workload and a memory budget, we return a measured comparison against your current cache. The fastest way to see the field on your own numbers.
A production license for a serving deployment. The full integration behind your serving layer, the fidelity dial, and lenses, with the field held to a budget you set. Sized to the deployment, not the conversation.
An embedded license for products that ship the field inside them: wearables, handsets, robots, and game engines. One build, one fidelity parameter, from a rack down to a headset, licensed per unit or per platform.
Not sure which fits how you ship? TALK TO US →
A memory interface behind your serving layer: write the field, read the field, pin, and lens. No retraining, no second code path.
One parameter moves the field between lossless and minimal, so the same license scales from a datacenter to a device.
A saved persona, profile, or body of knowledge you can load into a deployment — what it should know and how it should respond — held in one stored field. Versioned and diffable, so you can update what a deployment knows without rebuilding it.
Integration support and ongoing updates to the field for the term of the license, so improvements reach your deployment.
SCOPE: what a license includes is fixed across tiers. What changes is the deployment it covers and the terms scoped to it, agreed under NDA.
The line is the same one that runs through the rest of the site. What you need to build a product is licensed to you: the integration, the dial, the lenses. How centers are formed, scored, and merged is the invention, and it stays patent-pending rather than shipped in the clear.
You license the field: the integration, the fidelity dial, and lenses, sized to your deployment and held to a budget you set.
Center formation, merge scoring, and the pin policy stay ours. You build on the field without owning the mechanism behind it.
Integration internals, parameter-level behavior, and commercial terms are shared under NDA once a pilot is scoped.
Integration support and updates run for the term of the license, so a deployment does not drift away from the current field.
Bring one workload and a memory budget. We return a measured comparison against your current cache, with the configuration that produced it.
Choose the tier that fits how you ship: a production deployment or an embedded build. Terms are scoped to that shape under NDA.
Integrate behind your serving layer or inside your product, set the budget and fidelity, and ship. Support and updates run for the term.
SCOPE: it starts with a pilot. Measured numbers for your workload come out of that engagement, and the license is scoped to what you decide to ship.
A scoped four-week pilot: you bring one workload and a memory budget, we return a measured comparison against your current cache: footprint, recall, and the configuration that produced both.