Maple Login

Your AI conversations stay private. Verify it yourself.

Type something. Watch the difference.

What traditional AI providers receive

Anything you type, in plain text.

Provider policies and account settings determine how it can be accessed and used.

May be used for model training unless you opt out.

What Maple receives

End-to-end encrypted before processing.

Decrypted only inside hardware-isolated infrastructure for AI inference.

Browser-side demo. AES-256-GCM with a session-only key.

Try in Maple

How Maple Protects Your Data

Layered hardware-enforced protection, from your device to the AI model.

Audit it yourself.

Step 1

Encrypted on Device

Messages encrypted locally before leaving your device.

Step 2

Secure Enclave

Decrypted only inside a hardware-isolated enclave.

Step 3

GPU TEE

AI inference inside a trusted execution environment.

Step 4

Open Source

Verifiable code with reproducible builds.

Both our client and server code are public. Reproducible builds and attestation let you confirm what's actually running.

Live Cryptographic Attestation

A signed enclave attestation. Verify it yourself.

attestation.cbor
DRAFT

Server PCR0 Fingerprint

b3afd87f5c3b7f5b8d2cf04a91e87a3d6c1f4090c8b39b2e6a1d4f8e3c5a7b9d4f2e1a8c6b5d9e4f3a2b1c0d9e8f7a6b5

PCR0 matches remotely attested value

For technical details, check out the AWS Nitro Enclaves documentation .

Show Full Attestation Details
Module ID:
i-06c79bf817127030a-enc019ddf7ee5826b2f
Timestamp:
May 3, 2026 at 09:53:40 AM CDT
Nonce:
371a7dc7-5bfe-4f55-91ee-4028c4555554
Digest:
SHA384
Public Key:
L42mFzvJ0QiHrNX3VBeE/mxI0Qx5JCWDA6SL4WTe8zg=

Document signature verified with this public key

Additional PCR Values
  • PCR1: bcdf7e6c91dca4a5d8b8b9f6e4f2c1a7d3e9f0b5c8a4d7e6f3b2c1a0d9e8f7a6b5c4d3e2f1a0b9c8d7e6f5a4b3c2d1e0
  • PCR2: 3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f
  • PCR8: 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Certificate Chain:

Root Certificate

Subject: C=US, O=Amazon, OU=AWS, CN=aws.nitro-enclaves

Valid From: 10/28/2019, 8:28:05 AM

Valid Until: 10/28/2049, 9:28:05 AM

Calculated SHA-256: 641a0321a3e244efe456463195d606317ed7cdcc3c1756e09893f3c68f79bb5b

Expected root cert hash: 641a0321a3e244efe456463195d606317ed7cdcc3c1756e09893f3c68f79bb5b

Root certificate hash matches AWS root certificate

Show PEM Certificate 
-----BEGIN CERTIFICATE-----
MIICETCCAZagAwIBAgIRAPkxdWgbkK/hHUbMtOTn+FYwCgYIKoZIzj0EAwMwSTEL
MAkGA1UEBhMCVVMxDzANBgNVBAoMBkFtYXpvbjEMMAoGA1UECwwDQVdTMRkwGQYD
VQQDDBJhd3Mubml0cm8tZW5jbGF2ZXMwHhcNMTkxMDI4MTMyODA1WhcNNDkxMDI4
MTQyODA1WjBJMQswCQYDVQQGEwJVUzEPMA0GA1UECgwGQW1hem9uMQwwCgYDVQQL
DANBV1MxGzAZBgNVBAMMEmF3cy5uaXRyby1lbmNsYXZlczMBMBAGByqGSM49AgEG
BSuBBAAiA2IABPwCV0umCMHzaHDimtqQvkY4MpJzbolL//Zy2YlES1BR5TSksfbb
48C8WBoyt7F2Bw7eEtaaP+ohG2bnUs990dJX28TcPQXCEPZ3BABIeTPYwEoCWZE
h8l5YoQwTcU/9KNCMEAwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUkCW1DdkF
R+eWw5b6cp3PmanfS5YwDgYDVR0PAQH/BAQDAgGGMAoGCCqGSM49BAMDA2kAMGYC
-----END CERTIFICATE-----

Certificate 2

Subject: C=US, O=Amazon, OU=AWS, CN=b68b812f20558bd7.us-east-2.aws.nitro-enclaves

Valid From: 4/29/2026, 7:48:07 AM

Valid Until: 5/19/2026, 8:48:07 AM

Signature verified with chain

Show PEM Certificate 
-----BEGIN CERTIFICATE-----
MIIChDCCAgmgAwIBAgIQBABCDEFGhaVBoSLK4WTe8zgwCgYIKoZIzj0EAwMwSTEL
... (truncated for sample)
-----END CERTIFICATE-----

Certificate 3

Subject: CN=41e1248bd847c447.zonal.us-east-2.aws.nitro-enclaves, OU=AWS, O=Amazon, C=US, ST=WA, L=Seattle

Valid From: 5/2/2026, 9:31:00 PM

Valid Until: 5/8/2026, 8:31:00 PM

Signature verified with chain

Show PEM Certificate 
-----BEGIN CERTIFICATE-----
MIIB5TCCAYqgAwIBAgIQABCDmxI0Qx5JCWDA6SL4WTe8zgwCgYIKoZIzj0EAwMw
... (truncated for sample)
-----END CERTIFICATE-----

Certificate 4

Subject: C=US, ST=Washington, L=Seattle, O=Amazon, OU=AWS, CN=i-06c79bf817127030a.us-east-2.aws.nitro-enclaves

Valid From: 5/3/2026, 7:02:31 AM

Valid Until: 5/4/2026, 7:02:31 AM

Signature verified with chain

Show PEM Certificate 
-----BEGIN CERTIFICATE-----
MIIBxDCCAWqgAwIBAgIQAaBcDeFgHiJ4WTe8zgwCgYIKoZIzj0EAwMwSTEL
... (truncated for sample)
-----END CERTIFICATE-----

Certificate 5

Subject: C=US, ST=Washington, L=Seattle, O=Amazon, OU=AWS, CN=i-06c79bf817127030a-enc019ddf7ee5826b2f.us-east-2.aws

Valid From: 5/3/2026, 9:50:30 AM

Valid Until: 5/3/2026, 12:50:33 PM

Signature verified with chain

Show PEM Certificate 
-----BEGIN CERTIFICATE-----
MIIBuTCCAV+gAwIBAgIRAPa1d2EFGhaVBoSLK4WTe8zgwCgYIKoZIzj0EAwMw
... (truncated for sample)
-----END CERTIFICATE-----

Our code is open source: Maple client and OpenSecret server .

The Spectrum of AI Privacy

Not all privacy claims are created equal. Here's how the approaches compare.

Standard AI

  • Your prompts processed in plaintext on provider servers.
  • Privacy depends on company policies, not technology.
  • Susceptible to provider-side access, subpoenas, and breaches.
  • May be used for model training unless you opt out.

Privacy Proxy

  • A middleman routes your request to strip identifying info.
  • Zero-data-retention is a policy promise, not a guarantee.
  • Your prompts are still processed in plaintext by the AI provider.
  • You must trust the proxy operator and the AI provider.
Maple's Approach

Hardware-Encrypted AI

  • Data encrypted on your device before it leaves.
  • Decrypted only inside a hardware-isolated enclave (TEE).
  • Your data is not used for model training, advertising, or tracking.
  • Open-source code and live attestation so you can verify.

For Your Security Team

Technical facts for evaluating Maple's security architecture.

How Maple Protects Your Data

Hardware Isolation. AWS Nitro Enclaves provide CPU and memory isolation, ephemeral storage, and no external network connectivity. External traffic must pass over vsock to a proxy on the parent instance.

Code Integrity. Enclave images are measured at boot. The PCR0 hash uniquely identifies the exact code running inside.

Remote Attestation. A cryptographic attestation document, signed by AWS Nitro hardware, proves the enclave's identity and integrity.

Reproducible Builds. Anyone can build our open-source code from GitHub and compare the resulting hash against the live attestation.

Minimal Trust Model. Trust is concentrated in AWS Nitro hardware and open-source code, with reproducible builds and attestation for independent verification.

Per-User Encryption. Data outside the enclave is stored as encrypted blobs per user. Decryption keys live inside the TEE and on user devices.

Questions? Reach us at [email protected]

Maple
Introduce Us to Your Security Team

For businesses and teams

Bring sovereign AI to your organization.

Maple Teams brings this end-to-end encrypted, verifiable architecture to company research, writing, coding, and analysis. Use Maple Proxy API to integrate Maple with existing apps and workflows, and MCP to connect thousands of compatible data sources.

Explore Maple Teams
For AI Agents

Point Your AI Agent at Maple

Our site is ready for AI agents with machine-readable documentation.

1

Copy this prompt into your agent

“Read https://www.trymaple.ai/llms-full.txt and give me a summary of Maple’s security architecture. How does its encryption work, what are the trust assumptions, and how does it compare with using ChatGPT or Claude directly?”
2

Works with any web-capable agent

Claude Code, OpenClaw, Codex, OpenCode, Devin, Cursor, Droid, or any agent that can fetch URLs.

Frequently Asked Questions

What is a Trusted Execution Environment (TEE)?

A TEE is a hardware-isolated area of a processor that runs code in a secure enclave. Maple uses AWS Nitro Enclaves to isolate AI processing from the parent EC2 instance. Nitro Enclaves have no external network connectivity; external traffic passes over vsock to a proxy on the parent instance. Cryptographic attestation reports measurements of the enclave image and code so they can be verified against the published build.

Is this the same technology Apple uses for iCloud?

Similar concept, different implementation. Apple's Private Cloud Compute uses custom silicon with Secure Enclave. Maple uses AWS Nitro Enclaves with attestation-verified code. Both approaches isolate data processing in hardware and use cryptographic verification of the software environment.

How does cross-device sync work if everything is encrypted?

Your account has its own private key derived from your credentials. Chat history is encrypted with this key before leaving your device and stored in encrypted form on our servers. When you log in on another device, your key is re-derived and used to decrypt your data locally.

Who do I actually have to trust?

Your trust assumptions are minimal and verifiable:

  • Hardware: AWS Nitro hardware performs as documented (independently audited).
  • Code: The open-source code running in the enclave does what it says (you can audit it).
  • Attestation: The cryptographic proof on this page confirms the running code matches the published source.
Can I verify all of this myself?

Yes. Our server code is open source . The attestation document on this page is fetched live from our enclave and verified against AWS's root certificate. You can independently reproduce the build, compare the PCR0 hash, and confirm that the code running in production matches the published source.