Questions about AI governance, answered plainly.
Straight answers on where Verillian runs, what it records and what it covers.
Before you buy
What is Verillian?
Verillian is software on your staff devices. It applies your AI policy and keeps the record of each request on your agency's own servers.
Which AI tools and agents does it cover?
Tools on an enrolled device that reach a service Verillian inspects, with nothing to set up inside the tool. Each request is recorded, and what is checked or refused depends on the service. A tool that never reaches the checkpoint is out of scope.
Is our data used to train AI models?
No. Verillian never receives your prompts, responses or records, so there is nothing of yours for it to train on.
Does Verillian replace our email and document compliance suite?
No. It works alongside it. Your compliance suite keeps covering the email, documents and chat it already holds. Verillian adds the record of AI use on staff devices: who used which AI tool, what was sent, and what your policy decided, kept on your own servers.
What does Verillian cost?
Terms, licensing included, are agreed in the sales conversation.
How does a pilot work?
A pilot is a full deployment on your own devices and infrastructure, scoped to the rules you answer to. The pilot page walks through the stages.
How is the license enforced on our infrastructure?
Through a signed key. Verillian is proprietary software, licensed per deployment: the key sets your device count and term, and only we can sign a valid one.
Can we add devices mid-term?
Yes. Tell us the new count and we issue an updated key that runs through your existing renewal date.
What happens if we don't renew?
Sealed records stay in your environment either way, because your data was never with us.
Does Verillian need access to our data or our network?
No. The console and the record run on infrastructure you run, and content is encrypted to your organization's key. Verillian never receives your prompts, responses, records or that key.
How do we start buying it?
Most agencies start with a pilot: a full deployment on your own devices and infrastructure, scoped to the rules you answer to. Terms are agreed in the sales conversation. Run a pilot, or ask for a demo.
Running Verillian
How does setup work?
macOS, Windows and Linux are supported. The console runs on a server and database you choose, on premises or in a private cloud you run.
What happens when a request breaks the policy?
The checkpoint checks a request against your policy before the prompt leaves. On the services Verillian inspects, a tool call is checked before the tool runs. When a rule redacts, the AI provider receives only a placeholder, and the record keeps only the redacted text, encrypted to your organization's key.
Do we have a working kill switch for AI agents?
Yes. Stop AI use for one provider or everyone. A stop reaches an online device at its next check-in, within about 30 seconds, and refuses its next request. A device that is offline gets the stop when it reconnects. A request already under way finishes.
How do we manage policy across a whole fleet?
Policy is signed and delivered to every enrolled device, and tool rules can differ by group. Each device reports the policy version it enforces, and the console shows it.
Where does the record live, and who can read it?
On infrastructure you run. Content is encrypted to your organization's key, created in your administrator's browser. Verillian never receives that key. Reviewers you authorize open records in your console, and each open is recorded. The security page sets out the boundary.
Can we prove what an AI did in an audit?
Yes. Each request is recorded under the person assigned to the enrolled device, and you export the records for the dates the auditor asks about. Verillian checks the signature on each record as it arrives, for devices with a registered key.
How do we know the record was not altered?
Records are append only: they cannot be altered or deleted from the console or the record. The audit page shows how an entry is built.
How does the console sign in?
Through your own identity provider over OIDC, so there are no local passwords to manage. Roles are assigned in the console, and MFA stays whatever your identity provider enforces.
Who on our side runs Verillian day to day?
Your IT or security team runs the console on a server and database you choose. Your records staff and counsel open records when a request or audit needs them, as reviewers you authorize, and each open is recorded.
What happens to the record when an employee leaves?
It stays. Each request is recorded under the person assigned to the enrolled device, on your own servers, so the record outlasts the person's account and the device.
How do we answer a public records request about AI use?
Search the record for the people and dates the request names, and export what you find. The record is on your agency's own servers, so there is no vendor to ask and no personal account to search. How clerks use it.
See Verillian on a real device.
