Skip to content
VIREX
Log inGet started
// FAQ · Safety and data

Where does my code and data run?

Your code runs on your own machines and never enters Virex infrastructure. Virex is a hosted control plane that holds coordination data only: session activity and decision records, the memories your agents write, and account and entitlement state. Credentials and execution stay with you.

// The detail

Two sides of one boundary.

It is worth separating these, because the honest answer is different on each side and a vendor blurring them is telling you something.

01

Your side: execution and credentials

Coding agents run on your hardware under your own model subscriptions. Your repository, your environment, your keys. Virex has no execution rights and no copy of your code.

02

Our side: coordination

Session activity and decisions, organization-scoped memories, and account state. This is real data about your work and we are not going to pretend we hold nothing.

03

Why the split exists

Remote oversight needs session structure to travel, and memory retrieval needs a store outside the session. Neither requires your code, so neither gets it.

// What that means practically

Three consequences worth knowing.

Including one that cuts against us.

No code exfiltration surface

There is no Virex build environment holding your repository, because there is no Virex build environment.

Coordination data is isolated

What we do hold is scoped per organization and enforced at the database layer with row-level security.

We are not in your critical path

If the control plane is unavailable, your local agent keeps running while you lose oversight and memory retrieval. That is a real trade-off of not sitting in the execution path.

// Stated precisely

Precisely what is stored where.

The full inventory rather than a reassuring sentence.

On your machinesYour repository, your working state, your model credentials, and the agent process itself.
In the control planeSession activity records, pending decisions and their outcomes, organization-scoped memories, account, seat, and entitlement state.
Never in the control planeYour source repositories, your model provider credentials, and build artefacts.
IsolationPer-organization isolation enforced at the database layer with row-level security, applied identically to web, CLI, SDK, and MCP access.
In transit and at restEncrypted in transit between your machines and the control plane, and encrypted at rest by the managed data services holding it.
Deployment optionsHosted only. There is no self-hosted or customer-cloud deployment.
// FAQ

Related questions

Does Virex ever have a copy of my repository?

No. There is no Virex-operated environment that clones, builds, or runs your repository. The agent works against your files on your machine.

What about the memories my agents write?

Those are stored in the control plane, because retrieval across sessions and machines is the entire point. They are organization-scoped and isolated at the database layer.

Where is that data physically hosted?

On the hosted control plane operated by Virex. Regional residency requirements are handled case by case at this stage rather than through a published region selector, so ask before buying if you have a hard requirement.

Can we run Virex in our own cloud?

No. There is no self-hosted or bring-your-own-cloud deployment, and we will not describe one as available. The relevant property is that execution and credentials never leave your machines.

What happens to our data if we stop using Virex?

Tenant-scoped data held for the organization is removed when the organization is removed. Memories and session records belong to the organization rather than individual members.

Take it to your security team.

The security page has the mechanisms. If your review needs something else, ask and we will answer specifically.

Get startedSee pricing