Answers, in plain language.

No one. Confidential-tier jobs run inside a hardware-attested confidential environment, sealed from the machine's owner, the operator, and AugmentEV itself. Inputs go in sealed; results come out sealed.

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.

The platform is fail-closed: unverified jobs are rejected, not run. You never get a silent "trust us" where a proof should be.

Not today — and we won't imply otherwise. What you get today is per-job evidence: hardware attestation and a signed receipt you verify yourself. Formal certifications are on the roadmap, and dated commitments land on the changelog.

The platform is built for teams in health, legal, and financial services handling sensitive data, and we sign DPAs (our standard one is published here). Confidential processing keeps inputs and outputs sealed from everyone, including us. Bring your specific obligations to a pilot conversation and we'll map them honestly.

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.

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.

The receipt every job returns: a post-quantum-signed, tamper-evident record of exactly what ran. Think of it as a black box on every job — when anyone asks what happened, you play the tape.

In your browser on the Verify page, or with a single curl call to the public verification endpoint. No account, nothing to install — anyone can check independently.

Bring your own containerized workload — any OCI image — or call a ready-made AugmentEV agent: Khanoor (security log triage), Resolve (customer-support resolution), or DocFlow (document processing). Interfaces: REST, MCP, or A2A. Nothing leaves the sealed boundary in the clear.

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.

Confidential includes everything in Standard, plus hardware-attested confidential execution, inputs and outputs isolated from host and operator, and fail-closed behavior. Standard already gets the signed receipt on every job.

Everything in Confidential, plus dedicated, sovereign-grade isolation under a design-partner agreement. When your auditor has an auditor — and the data can't leave the building — this is your tier.

Live today: the confidential runtime and the post-quantum-signed receipt on every job, including self-serve access on Paseo. Roadmap — and labeled as such: broader workloads, an open third-party marketplace, a sovereign mainframe tier (expected fall 2026), and, further out, a fleet of idle electric vehicles.

Standard from $0.50 per job, Confidential from $1.38 per job, Sovereign custom. The tier price covers the first 60 seconds of execution; longer jobs are billed in additional 60-second units, execution time only, itemized on every receipt. No seats, no minimums, no idle bill. Full details on the pricing page.

One request mints an API key — email or wallet, no contract. A $25 minimum loads your balance, and your first purchase is matched with $25 in credit. Pay per call in USDC via x402, or Stripe-billed usage.

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.

List an agent or tool, set your price (5¢–$25), and keep 90% of revenue — a flat 10% commission, paid out automatically with no invoicing. Your endpoint, your keys; we meter and settle. Third-party publishing is on the roadmap.