Security
Seven rules we hold even when a customer asks us not to.
Enforced in code, checked at review. A change that breaks one does not ship, and we have turned down requests that would have.
The agent never holds your knowledge base
It receives a handful of relevant facts per question. No copy of your company sits in a model's context window.
One gate for every write
Nothing edits company memory directly, our own maintenance included. Every change goes through the same recorded door.
The model never decides its own clearance
Permission comes from a verified identity, never from anything an agent claims about itself. A manipulated agent gains nothing.
Clearance is settled before retrieval
Unauthorized facts are never fetched in the first place, so they cannot be talked out of the system afterwards.
Nothing is silently deleted
A correction supersedes the earlier fact and keeps it. Your history stays intact, and stays answerable.
No shared master keys
Each deployment holds short-lived, scoped credentials, never shared between customers, never built into an image.
Your company runs alone
Every customer gets their own deployment. Not a partition, not a row filter, not a tenant id in a shared table. There is no other company in your system, so there is no query that could reach one.
Where it runs
One company, one brain. We keep none of it.
Varrolabs is not a place your company’s memory goes. It is a system that runs inside your own boundary and belongs to you.
A deployment of your own
Your cloud account, or ours in a partnered data center, running only your company. No shared database, no shared index, no neighbours.
We hold nothing
We do not keep a copy of your documents, your memory or your answers. If you leave, there is nothing of yours on our side to delete.
The brain is yours
The memory your company builds up is your asset, not a hostage. What we sell is the system that grows and maintains it.
Destructive actions are approval-gated
Sending mail, deleting files, touching production. Every critical action goes through plan, then inspect, then execute, and every reversible action registers a way to undo it so a person can roll it back cleanly.
Built on
Boring infrastructure. Opinionated boundaries.
A small, deliberately dull stack at the edge, a graph underneath, and not one line of code that assumes a particular model vendor.
- Go services
- Model Context Protocol
- Graph store
- Relational store
- Containers
- Kubernetes
- Signed identity
- Hosted or self-hosted models
- Versioned snapshots
- Streaming to the browser
Model-agnostic by contract
Every model call goes through one interface. Moving from a hosted frontier model to a self-hosted open one is a line of configuration, not a migration.
Runs where your data already lives
Your own cloud account, or ours in a partnered data center, or fully disconnected against local inference. Your keys, your memory, your egress rules.
Diligence
We will tell you exactly where the line is.
We are in private beta. You should learn what is production ready and what is still being built before a trial, not during one.
We will not oversell it
We are in private beta and parts of this are still being built. We will not tell you a feature is finished when it is not. What is working, what is half-built and what is still a decision gets walked through with you directly, under NDA, with the engineer who wrote it. We do not publish a roadmap our competitors can read.
You get the engineer, not a slide
Technical diligence happens with the people who built the system, against your own material, in your own vocabulary.
Answers in writing
Security questionnaires, architecture review, residency specifics, answered formally once we are under NDA.