Run a pilot in your environment.

A Verillian pilot is a full deployment on your own devices and infrastructure, scoped to the rules you answer to. Your policies decide real requests, and the signed records they produce stay yours whether or not you buy.

Run a pilot Book a demo

Your endpointsYour keysYour records

Demo data.

How a pilot runs, stage by stage

Scope it

Agree the devices, the rules you answer to and who reviews the result.

Stand it up

Verillian goes on your devices, and the console on your own infrastructure.

See a real request

A real request from an enrolled device is decided and recorded.

Enforce your policy

A rule you wrote is applied to a real request, and the record shows the ruling.

Run at full scope

Every device in scope runs under your policy while you watch the results.

Review the record

You open the record on your own screen with us and decide what comes next.

One allowed AI request in the record drawer: person, device, provider and model, with the content sealed. Demo data. — Demo data.

See a real request and its record

Each request that crosses the checkpoint becomes a signed record. This one shows who asked, on which device, to which provider and model, with the content sealed.

How a signed record is built

A pilot runs inside your environment

Your devices, your server and your keys carry the pilot. Verillian never receives your prompts, your files or your record.

Your enrolled devicesThe checkpoint on each device rules every request against your policy.

Signed record

Your own infrastructureThe console and the records, under your key.

Requests your policy allows

The AI providers your policy namesOutside your environment.

Your prompts, files and record

VerillianReceives none of them.

Read this diagram as text

Your enrolled devices run the checkpoint, which rules each request against your policy.
The checkpoint writes a signed record to your own infrastructure, where the console reads it under your key.
Requests your policy allows go on to the AI providers it names, which sit outside your environment.
Verillian receives none of your prompts, your files or your record.

What a pilot gives you, and needs

Part	What you get	What we need from you
The checkpoint	You getVerillian on the devices you enroll, deciding on each device.	We needDevices to enroll and someone who can install on them.
The console	You getThe admin console and the signed records, on your own infrastructure.	We needA server and a database in your environment.
Your policy	You getRules you write, ruling real requests. Blocking runs on Claude Code and the Claude API; other supported providers are recorded.	We needThe rules you answer to, and the request you most want refused.
The record	You getA signed record of each captured request, kept under your key.	We needA reviewer on your side to open it with us.
The limits	You getAligned to the rulebooks it names, not certified. Redaction is best effort, and verified on the Claude API. No part of it runs in a Verillian cloud.	We needA scope agreed in the sales conversation, before anything is installed.

Who a pilot fits

Teams in regulated sectors where people already use AI, and a reviewer will ask what happened. Pick the sector closest to yours.

Tell us which devices you would enroll

Start with a few lines about your organization and your environment. We read every request and reply. Terms are agreed in the sales conversation.

Not ready? Book a demo first