SVO — software verification & operations

You choose where the audit of your code runs.

The two paths

In your environment

The audit is executed inside your infrastructure, with your access. The report is born and stays there. Everything stays with you.

On our infrastructure

You send the address of the code and grant read access — access that stays yours, and that you revoke whenever you decide. The report arrives in your inbox, with the data destruction certificate — and on your side there is nothing to install.

Which one is your case

Do you have a Claude Max, Team or Enterprise plan — or API credits — and want the execution to stay inside your environment? The audit is executed on your infrastructure, and consumes your plan or your credits. It is the most direct path.

Do you use Claude Pro, another plan or another AI — or would you rather keep your plan for other work? The audit is executed on ours, the report arrives in your inbox with the data destruction certificate, and the processing is included in the price.

How to install and how to pay for the AI →

The guarantees

The audit reads your code. What it writes is the report.

Any secret the audit finds goes into the report masked.

Each customer's report stays with the customer.

In your environment, the one reading your code is the Claude on your own account. On our infrastructure, the processing is our responsibility, and that is in the contract.

What reaches us

When the audit runs in your environment, we receive its progress, and that exists so the audit can continue from where it stopped if it needs to restart.

When it runs on our infrastructure, a dedicated area for your project is created on our server. At the end of the audit that area is erased, and the certificate records what was destroyed.

Check it yourself: while the audit runs in your environment, use a network monitoring program you already have installed and analyse the traffic — what goes out, what comes in and where it goes.

The certificate

The destruction certificate comes with the report and states three things: what was destroyed — the working area and the access key issued for your order —, that the destruction is verified by reading, and what it does not cover: the infrastructure provider's backups, the report already in your hands, and the processing by the language model provider. It is a contractual commitment and the record of what was carried out.

Product by product, each one states where its audit is executed.