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

Start a pilot

One workflow. Human control, proven on your own systems.

Pick one place where an AI action carries consequences. Regulayer™ runs inside your environment, checks every action against a named person’s current authority, and seals a record your carrier, auditor or regulator can check without us.

Runs inside your environment. Your data does not leave it.

How a pilot runs

Five steps, on your own work.

  1. 1Choose the workflow. A claims decision, a bind, a payment, a batch release, a filing. One action that matters.
  2. 2Name the people and set the authority, once. Who may let the AI do what, how much, and for how long.
  3. 3Regulayer™ goes in the path. On your servers, or in a sandbox for the pilot. Model-agnostic, so your agents stay as they are.
  4. 4Run it, and push it off course. Watch actions allowed, sent back, held and stopped. Withdraw an authority mid-run, and the same request stops.
  5. 5Read the record. Every decision, allowed or stopped, sealed as it happened. Hand it to anyone to verify offline.

From your side

What you provide.

The workflowThe workflow and its target system.
The peopleThe named people and their authority.Who may allow what, at what limits, for how long.
The agentThe agent’s identity.
The environmentA server or sandbox to run on.Inside your environment. Your data does not leave it.

Success criteria

How success is measured.

  1. 1Every consequential action in the workflow passes the check.
  2. 2Actions outside authority stop before they take effect.
  3. 3A withdrawal mid-run stops the next action.
  4. 4Every record verifies offline, and a changed record fails.
  5. 5Legitimate work inside authority completes, and wrongful holds are counted.
  6. 6The time the check adds is measured against a budget agreed at the start.

Control your AI: the Regulayer™ six-week pilot. Share it inside your company.

What you receive

Evidence, not a slide.

The recordOne sealed record per action.Who allowed it, under what authority, and whether that authority held at the moment it took effect.
The Transponder™A live view of your AI.Actions, stops and withdrawals, by workflow, agent and named person.
The read-outStops, counted.Conduct Signal per 1,000 actions, what was held, and how fast a withdrawn authority took hold. For an insurer, these are the rating variables.

Insurance pilot

An insurance pilot, pictured.

Who takes partFour people, named at the start.The person who answers for the AI, the owner of the workflow, someone from IT or security, and the reviewer who will read the record. For an underwriting pilot, the insured’s team runs it and your underwriter reads what they share.
What access it needsOne workflow, inside your own systems.The workflow and its target system, the named people and their authority, the agent’s identity, and a server or sandbox to run on. Regulayer™ has no cloud of its own and no access to your data.
How longSix weeks, once scoped.Set up, connect, run and test, check, decide. Each pilot is scoped with the company first.
What you have at the endFour deliverables.Agreed coverage boundaries, the results, the verification files and a production recommendation.

For insurers

Bring one insured, or a book.

Start with the Transponder™: the insured runs Regulayer™ and the carrier reads the record, with the insured’s agreement. Add Regulayer™ Control, and actions outside the agreed authority are stopped before they take effect.

The pilot is paid, and the fee is credited back in the first quarter after the licence is signed.

Next

Tell us the workflow. We will show you the record behind it.

Regulayer™ supplies the evidence. Your carrier, auditor, regulator or court makes the determination. Patent pending.