Configure · Order what you want
One engine. Configured to your workflow.
Choose what you are building or operating, the action that must not run without a named person’s current authority, where Regulayer™ runs, and the capability packages you want switched on. The page writes the configuration, what your customer sees and what an outsider can verify, then sends it as a licensing enquiry, scoped in writing.
Runs inside your environment. Your data does not leave it.
1 of 5
What are you building or operating?
The licence follows this answer: your own estate, a product you ship, or a book you underwrite.
2 of 5
Which action must not run without a named person’s current authority?
Start with one. The engine checks it before it takes effect, every time.
3 of 5
Where will Regulayer™ run?
It runs outside the model, in front of your systems. Nothing about the work is sent to us.
4 of 5
Included in every licence. Add what you need.
Every licence checks a named person’s authority before an action takes effect, seals every decision, and lets anyone verify the record offline. Those three are in every licence. The packages below are optional: choose any, or none.
- The check: a named person’s current authority, before the action takes effect
- The seal: every decision recorded, allowed or stopped
- Open verification: anyone can check the record offline, without us
5 of 5
What scope are you licensing?
A licence is scoped in writing: the authority boundary, the capabilities, the deployment and the distribution rights.
What a licence covers
The engine, at the level the control problem requires.
Regulayer™ is licensed as the complete engine, as an individual capability, or embedded within another company’s platform or product. Your customers receive the control, the record and the verification inside what you already deliver.
Every configuration writes into the same record. Switch a package on later and the earlier records still verify.