Regulayer Enterprise licensing
Main site The engine By problem What is licensed Deployment Assurance AI audit trail Human authorship and review The record format What it proves Security review Begin with the problem

SignalDrop · a Regulayer surface

The evidence has to reach someone outside. That is where it fails.

SignalDrop delivers a complete proof as one file that opens with one action, for a recipient who installs nothing and holds no account with anyone. Sealed at the source, it proves itself in the act of arriving.

The situation

Proof that opens only inside your own tooling is not proof to a regulator, an opposing party or an insurer. The moment evidence has to travel, it fragments: a file here, a key there, a service the recipient must trust before they can believe anything.

For five thousand years the sender handed over a sealed envelope, and the envelope was the proof. Software broke the envelope into separate services and handed the recipient the job of coordinating them. A Drop restores the envelope. The wax is cryptography, and the seal answers for itself when it arrives.

What a Drop is

No cloud

The world inside the file runs on the device that opens it.

No connection

It works with the network cable out. A signal is not required.

Data stays local

Nothing inside the Drop reports home. You cannot leak what was never stored.

Proof built in

The Drop carries its own governance and signs its own record. Verification is a property of the cryptography, not of any service.

How it is licensed

Branded Drops are the intended form: a MedDrop, an EduDrop, a Drop of your own, carrying your evidence into someone else's hands in a form they can check without you. The capability is public and runs in working code. The mechanism is part of the filed estate, and the detail travels under non-disclosure.

Where it belongs

Regulator submissions

Evidence that verifies itself, for a reader who owes you nothing.

Opposing parties and courts

Disclosure that the other side can check without trusting your systems or ours.

Insurers and auditors

The record of conduct, delivered complete, to a party adverse to everyone involved.

Cross-border evidence

Where residency forbids a service, a file is still lawful to receive.

Deployment

It runs on your machines, and nothing of the work leaves the building.

The kernel binds the loopback interface and refuses any client that is not local. The signing key is generated on your own machine on first run and never leaves it. In the default mode there is no outbound call of any kind. Where independent time is required, a single cryptographic digest goes to a public timestamp authority, never the file and never its contents. The source ships readable, so your own security function can satisfy itself line by line.

Every answer your security function will ask for, on one page you can forward

The estate

Part of the filed estate: eighteen patent filings and a PCT. Patent pending across the estate.

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