Verillian
Menu
Book a demo
A woman in yellow headphones works at a desk with several monitors beside a bright window.

Your servers. Your keys. Your records.

The system of record for your agency's AI use stays on your servers. Reviewers you authorize open records, and each open is recorded. Verillian never receives your organization's key.

Book a demo

What stays in your hands

Your server, not ours

The admin server runs on your infrastructure. Verillian gets no copy.

Decided on the device

Policy is applied on each enrolled device before a prompt leaves.

Signed by the device

Signed with the device's own key. The server keeps only the public half.

Signed policies

A checkpoint rejects any policy that is not signed.

A name on every record

Each request is recorded under the person assigned to the enrolled device.

Stop when you decide

An administrator can stop AI use for one provider or everyone.

Where your data goes, and where it never goes

Your enrolled devices
  • Decides before a prompt leaves
  • Signs each request
AI provider
  • Receives only what was allowed
Your infrastructure
  • Your admin server and console
  • Keeps every signed record
Verillian
  • Never receives your key

When your policy redacts, the AI provider receives only a placeholder.

The record of an allowed request in the console. The text sent to the model shows [NAME_REDACTED], [PHONE_REDACTED] and [EMAIL_REDACTED] in place of a resident's name, phone number and email address.

Security, status and compliance

A woman in a teal blazer holds a tablet beside racks of servers.

Security overview

A key Verillian never receives, and a plain answer on SOC 2.

A man at an office desk types on a laptop beside stacks of papers.

Status

Enforcement and the audit chain live inside your network.

Two women in an office look through a blue binder together.

Compliance

CJIS Security Policy v6.1 and NIST 800-53, framework by framework.

Questions for your security review

A man in a blue suit reads through a set of papers.
What happens when Verillian cannot read a request?

On the services Verillian inspects, a request it cannot read is refused.

How quickly does a stop take effect?

A stop reaches an online device within about 30 seconds and refuses its next request.

What can an auditor show from the record?

Each captured record is signed and hash-chained, so its signed fields are tamper-evident. An auditor can show who used which AI tool and when, what was sent and what your policy decided. Your own server checks each record's signature as it arrives, and flags any that fails.

What can our security review get in writing?

The architecture walk-through and a completed security questionnaire. Control-by-control mappings, and a draft DPA for your counsel's review, on request.

Take the architecture into your security review.

Book a demo
The Verillian console home for the last 30 days: 10 devices, 684 requests, 613 allowed and 71 denied, the Enforce, Audit and Contain cards with the two active holds, and the latest refused requests.The Verillian console home for the last 30 days: 10 devices, 684 requests, 613 allowed and 71 denied, the Enforce card with two suggested policies waiting, and the top of the Audit card.