OEM, platform and enterprise licensing
Human control.
Inside what you ship.
License the Regulayer™ engine. Before your AI acts, it checks that a named person still allows the action. If not, it stops it. Either way it seals the record. Your customers get the control, the Transponder™ record, and proof anyone can check without you or us.
The whole engine, or one capability. It runs on your customer’s machines. The records still verify after the licence ends.
What is licensed
One engine. A scope that fits your product.
In the product you sell
Platforms, software vendors and OEMs build the engine into what they ship. The licence names the products, the environments and the right to distribute.
In your own operations
You put the engine in front of the actions that matter in your own systems. The licence names the workflows, the actions and the environments.
One capability
License one control or one kind of evidence when that is all you need. Its scope says exactly what it checks, stops or records.
What customers receive
The control. The view. The evidence.
The engine
Before the action takes effect, it checks that a named person still allows it. If not, it stops. Which actions, and what happens if the check cannot run, is agreed when we connect it.
The Transponder™
What the agents did, who allowed it, and what was stopped, as it happens. Your customer reads it and chooses what to share.
Independent verification
Anyone handed a record can check it, licence or no licence. The record says which agents it covers, how the person was identified, and where its time came from.
Licence scope
The rights, not only the capabilities.
| Scope | What is agreed |
|---|---|
| Engine and capabilities | The whole engine, or the capabilities you choose. |
| Deployment and distribution | Inside your own company, or inside named products. Which customer deployments and environments. The right to distribute. |
| Commercial structure | An annual licence. Deployment fees or royalties where agreed. The written scope states the basis and any minimum. |
| Integration and support | The connection work, the interfaces we support, updates and support. |
| Branding and evidence | How Regulayer™ appears in your product, who holds the keys, who may read the evidence, and what a recipient can check. |
The configuration starts the conversation. Rights and fees are agreed in writing. The enterprise note on what is licensed.
See your proposed scope.
Choose the workflow, the environment and the capabilities. The page writes the configuration and sends it as the enquiry.
From evaluation to deployment
One workflow first. A licence next.
- Define the scope. The action, the named person, the evidence, the environment, and where it will ship.
- Run the paid pilot. An allowed action, a stopped one, a withdrawn authority, and the records checked, on your own systems.
- Agree production rights. Deployment, acceptance, support and fees, in writing, before rollout.
The pilot fee is credited back in the first quarter after the licence is signed.