Is it sealed? Check the proof yourself.

A TEE, a trusted execution environment, is a virtual machine whose memory the CPU encrypts with a key only the hardware holds. The host, the hypervisor and the operator see ciphertext. Our key broker runs this way, and TEE agents such as Perp Bot launch this way on AMA Hub. What was missing was proof you could check without taking our word for it.

That is what shipped. Our key broker now publishes a verdict for every TEE deployment, and the verify page checks it in your browser: the hardware-signed report, AMD's certificates and the code measurement. The deployment's wallet is made inside the VM. Nobody, not even its owner, can read it.

Open the verify page with the deployment's address in the link, or paste the address into "Check a deployment".

https://kbsv2.ama.one/verify/<ipv6 or deployment id>

A green verdict shows which checks passed, which agent image booted, the author's key and the owner's key. Press "Verify KBS1" on the same page to check the key broker itself: a fresh hardware report, AMD's certificates, checked locally.

The raw verdict is public JSON at kbsv2.ama.one/v1/tee/attestation/<ipv6>, for anyone who would rather script it.

At launch the AMD Secure Processor signs an attestation report carrying the VM's launch measurement. Its signature chains through the chip's VCEK certificate to AMD's published root key, so the hardware, not us, vouches for what booted. A simulator cannot forge that chain.

Our key broker, the KBS, checks the chain and the measurement against the agent image before a deployment counts as running, and only then hands the VM its secrets over an encrypted channel. The KBS runs in a TEE itself, with no upgrade path by design, and its own proof sits on the same verify page.

Source: github.com/amadeusprotocol/kbs

Hand one file to Claude Code or Codex. It derives your keys locally from your Amadeus Wallet recovery phrase, deploys the agent into a TEE, waits for the attestation and prints the verify link. Nothing to clone.

https://amahub.ama.one/deploy-tee/DEPLOY.md

Or open the CLI page on AMA Hub, which has the link, the MCP command and a blank machine to build on.

Most TEE platforms run containers on Intel TDX behind the platform's own key service. Ours runs whole VMs on AMD SEV-SNP with a Rust virtual machine monitor, a small Rust boot firmware and nobody between your agent and the chip. Less code to trust, and no third party in the trust path.

The full comparison is on Confidential Compute.

If you operate AMD EPYC 4th or 5th generation servers, you can become a trusted operator and run TEEs for the network. If you need dedicated TEEs for your own workloads, tell us what you run and we come back with capacity and pricing.

Book a meeting or write to [email protected].