Who sees what — and what you can prove.
Who can see my data while it runs?
On Confidential, the hardware-attested environment is designed to isolate inputs and outputs from the host and operator during execution. Standard does not provide this isolation boundary, and the workload itself necessarily processes the submitted data.
What does "hardware-attested" actually mean?
The hardware itself produces cryptographic proof of the environment your job ran in. You get evidence of the seal, not a policy promise about it.
What happens if a job can't be verified?
The platform is fail-closed: unverified jobs are rejected, not run. You never get a silent "trust us" where a proof should be.
Are you SOC 2 or ISO 27001 certified?
AugmentEV is not currently SOC 2 or ISO 27001 certified. Customers should assess their own compliance requirements during an access discussion.
Can we use AugmentEV for HIPAA or GDPR-regulated data?
We publish a DPA and offer Confidential-tier isolation, but using AugmentEV does not by itself establish HIPAA, GDPR, or other compliance. Bring your specific obligations to a pilot conversation.
Is the signing really post-quantum?
Yes. Every receipt is signed with ML-DSA-65, the NIST FIPS 204 post-quantum digital-signature standard. FIPS 140-3 validated cryptographic modules for the signing path are on our roadmap.
How long do you keep the evidence?
Tamper-evident receipts are retained for at least six months — so when a customer, auditor, or regulator asks what happened, the proof is still there to produce.
How jobs run, and how you check them.
What is a Proof-of-Task-Execution?
A post-quantum-signed, tamper-evident record returned for supported completed jobs. Think of it as a black box for the recorded execution — when anyone asks what happened, you can check the receipt.
How do I verify a receipt?
In your browser on the Verify page, or with a single API call to the AugmentEV-operated public verification endpoint. No account is required.
What can I run on AugmentEV?
Call a supported first-party AugmentEV agent: Khanoor (security log triage), Resolve (customer-support resolution), or DocFlow (document processing), or discuss a supported container workload. Interfaces include REST and MCP. Confidential adds an attested isolation boundary; Standard does not.
How do the cost and runtime caps work?
On every job you set a maximum runtime and a maximum spend. They are hard caps, enforced by the platform — not estimates we reconcile later.
What's the difference between Standard and Confidential?
Confidential includes everything in Standard, plus hardware-attested confidential execution, inputs and outputs isolated from host and operator, and fail-closed behavior. Standard supports signed receipts for completed jobs without the Confidential-tier isolation boundary.
What's live today versus roadmap?
Live today: Standard general-purpose verifiable execution, Confidential Intel TDX isolation, signed receipts for supported completed jobs, and an AugmentEV-operated public verifier. Roadmap capabilities are not represented as live.
What it costs, and how to start.
How do I obtain access?
Access is currently arranged with the AugmentEV team. We confirm the supported workload, commercial terms, and any evaluation conditions before credentials are issued. See the access page.
How do pilots work?
Design partners work directly with the founding team and shape the roadmap. Start with the pilot form and we'll scope your workload, your compliance obligations, and your success criteria together.
Can third parties publish tools on AugmentEV?
No. The public catalog currently describes AugmentEV's first-party agents. Third-party publishing is not open.
Still deciding?
Verify a receipt yourself — no account. Or tell us about your workload and we'll scope a pilot.
Open the verifier Start a pilot