Skip to content
Regulayer™Human Control for AI
Book a live demo

Security review

The page your security function can forward.

Every answer a review committee asks for in the first ten minutes, stated completely: where it runs, what leaves, who holds the keys, what code is inside, and what happens when the license ends.

Deployment facts

Where does it run?

On your machines, in your estate, in the supported deployment profile, including disconnected environments where the deployment is set up for them. The control surface is reachable only from within the deployment.

What leaves the building?

In the default mode, nothing. There is no outbound call of any kind. Where independent time evidence is used, the underlying content remains within the customer environment.

Who holds the keys?

You do. Signing keys are generated within your deployment, never transmitted, and never escrowed with us.

Is air-gapped operation a configuration?

It is architecture, not a setting: no egress, no account, no dependency on any network in the local profile. Disconnected operation is demonstrated in the selected deployment during the pilot.

What third-party code is present?

A small set of permissively licensed libraries implementing published mathematics. License texts ship with the software. Using audited public implementations is deliberate: an opposing expert checks the mathematics against a public reference, which is a stronger position than a private one.

Verification and continuity

Who can verify a record?

Anyone holding the file, with public mathematics, free and permanently. No account, no license, no call to any service we operate. Verification is a capability of the record itself.

What happens if the license ends?

Every record already issued remains valid. A lapsed license stops covering new records. It never reaches backwards.

What third-party assurance exists?

The public materials are demonstrations, the published record format and internal test results, each checkable against public references. They are not a third-party audit or certification. Ask for any release-specific external assessment as part of diligence. Patent pending across the estate.

What does it establish?

It records the declared or observed facts at the assurance level stated in the record, and anyone holding the file can verify that the record has not changed, permanently and without contacting us. Identity, review and authority carry their own evidence. Certification of compliance and admissibility are determined by a court or a regulator, which is where those determinations belong.

The one-sentence summary for the forward

The kernel does not observe the work. It records the decision about the work, on your machines, with your keys, and enforcement and evidence signing require no network egress.

Licensing begins with the problem, not the product.

Describe the system, what it decides, and what it would cost you to be unable to prove it. A written scope follows before any call.

Ways to begin:

A scoped pilot, inside your estate, on your machines. An architecture briefing, for your security function, one hour. The diligence pack: the record format and the estate, in writing. The problem itself, in your own words.

hello@regulayer.com