FAQ

Answers, in plain language.

Short answers to the questions teams ask first. Who can see your data, what a receipt proves, and how to get started.

Security & compliance

Who sees your data, and what you can prove

Who can see my data while it runs?

Our API service runs inside a protected virtual machine on secure hardware. It is built to keep its memory hidden from the host machine and the cloud provider. You can check the hardware's proof of this offline. The service still has to read your input to do the work. A separate Confidential option, which would keep each job apart, is not offered today.

What does "hardware-attested" mean?

The chip itself produces signed evidence of the setup the service runs in. Ours ties the service's live signing key to protected hardware. You can check it offline.

What happens if a job can't be checked?

Some requests are refused instead of run. A request for the Confidential option is refused. It is not quietly run on the standard service. We do not claim that every job is checked before it runs.

Are you SOC 2 or ISO 27001 certified?

No. AugmentEV is not currently SOC 2 or ISO 27001 certified. Please check your own compliance needs when you talk to us about access.

Can we use AugmentEV for HIPAA or GDPR-regulated data?

We publish a DPA (data processing agreement). Our API service runs in protected hardware. But using AugmentEV does not on its own make you compliant with HIPAA, GDPR or any other rule. Tell us your specific obligations when we discuss a pilot.

Is the signing really post-quantum?

Yes, for completion records. When our agents run, each finished job record is signed with a post-quantum signature. MCP calls produce no record.

How long do you keep the records?

We keep signed completion records for at least six months, under our Privacy Policy and DPA. So when a customer, auditor or regulator asks what happened, you can still show the record.

Product & verification

How jobs run and how to check them

What is a Proof-of-Task-Execution?

It is a signed record of a finished agent job sent through our API. If anyone changes it, it shows. It uses a post-quantum signature. Think of it as a black box for the job: when someone asks what happened, you can check the receipt.

How do I check a receipt?

Use our free verifier, from the Verify page. It runs on your own computer. No account is needed.

What can I run on AugmentEV?

Fabric Verify, to record and prove what your AI agent did. MCP text generation, in confidential mode. Our own agents (Khanoor, Resolve and DocFlow) are available by arrangement.

How do spending caps work?

Each access key has a spending cap, and we enforce it. A call over the cap is refused, not run.

What's the difference between Standard and Confidential?

We offer one service level today. The Confidential option is not available. It would keep each job apart and only send work to hardware that passed a check first. Requests for it are refused. They are not run on the standard service instead.

What is live today, and what is not?

Live today: Fabric Verify (beta), our API service on protected hardware, MCP text generation, and our offline verifier. By arrangement: our own agents (Khanoor, Resolve and DocFlow). Not available today: self-serve signup and the Confidential option.

Access & pilots

How to get started

How do I get access?

For now, the AugmentEV team sets up access with you. Before we issue keys, we agree what you will run, the commercial terms and any trial conditions. See the access page.

How do pilots work?

Early partners work directly with the founder. Start with the pilot form. Together we agree what you will run, your compliance needs and what success looks like.

Can third parties publish tools on AugmentEV?

No. The public catalog describes AugmentEV's own agents. Third-party publishing is not open.

Still deciding?

Check a receipt yourself. No account needed. Or tell us what you want to run, and we'll plan a pilot with you.

Open the verifier Start a pilot