Your device checks a hardware attestation report against a public transparency log before it sends anything. If the code running isn't the published code, nothing is sent.
Encrypted before it leaves
Prompts are sealed on your device to the enclave's key and only decrypted inside the TEE. Our relay, the cloud and the model provider see ciphertext. Nothing is logged, nothing is trained on.
History only you hold
Conversations are encrypted with keys that never leave your devices. Link a phone or a laptop with a code; recover with a 24-word phrase. We can't read them, and we can't reset them.
Two models, one guarantee
FastEveryday chat, writing, questions. Quick answers, sees images.
DeepSlower and more thorough. Hard reasoning and agentic coding, 1M-token context.
How a message travels
Attest. Your app fetches the enclave's hardware report and the published measurement from Sigstore's log, and confirms they match and that the TLS key is bound to that report.
Seal. The request body is encrypted to the attested key. Our relay adds the upstream credential and meters tokens from headers only.
Answer. The model runs inside AMD SEV-SNP or Intel TDX with NVIDIA confidential GPUs. The reply streams back sealed the same way.
Store. Both messages are encrypted with a per-conversation key derived from your account key, then synced as ciphertext to every device you've linked.
Any coding tool, privately
The aea-ai CLI runs a local OpenAI-compatible endpoint that does the attestation and sealing for you. Point OpenCode, Cursor, Cline or aider at it. aea-code ships as a ready-made OpenCode distribution.
aea-ai login --api-key aea_sk_…
aea-ai serve # http://127.0.0.1:4321/v1
aea-code # OpenCode, routed through the enclave
Plans
Prices in US dollars or Canadian dollars, chosen at checkout by where you are. Cancel any time.
