THE SECURITY LAYER FOR AI AGENTS

Your Inbox, safely shared with agents.

Clam sits between your Gmail inbox and your AI agents. Agents see only the email you allow. You see everything they do.

Get early accessHow it works
how it works

Share your inbox in three steps.

Write plain-English rules for what each agent can read, draft and send. No agent gets your whole Gmail inbox.

1

Connect Gmail to Clam

You connect Gmail to Clam, not to the agent, so the agent never reaches your mailbox directly. Clam doesn't store your emails.

2

Create a Shell with rules

A Shell is one agent's slice of your inbox. Clam sorts your email into categories with AI, and you write plain-English rules for what the agent can see and do.

3

Point your agent at it

Connect the agent to Clam's hosted MCP server in one click. It uses the usual email tools but only sees the part of your inbox you allowed.

use cases

Share your inbox with your agent without putting it at risk.

Each Shell starts as plain-English rules. Clam compiles them into Cedar policies and checks every request to your inbox against them.

Personal Assistant

Read work email and draft replies from my files for me to review. Never send.

Family Organizer

Read email from family, school and events. Forward the urgent ones as soon as they arrive. Never write new messages.

Project Manager

Watch work email and newsletters for competitor moves, then draft notes I can drop into the project. Do not send.

Investing Assistant

Read investment alerts and price moves and summarise them for me. Never send or forward.

Shopping Assistant

Read shopping, promotions and receipts, and pick out the real discounts. Never send.

Expense Tracker

Read receipts, utility bills and work bills. Draft a note when a charge looks wrong. Never send.

Governance

Your rules, enforced on every call.

Allowed actions pass through and everything else is blocked. Clam logs every read, draft and blocked attempt, with the exact policy rule that decided it.

Least privilege

An agent gets only what its Shell's rules allow.

No email stored

Clam proxies requests. Gmail stays the source of truth.

Full audit trail

Every action an agent takes or attempts, with the decision and the rule behind it.

Live decision log

Instinct read Inbox

Mar 28, 2024, 2:30 PM

Allowed

ChatGPT search "invoice 1043"

Mar 28, 2024, 2:30 PM

Allowed

Claude read verification codes

Mar 28, 2024, 2:30 PM

Denied

Gemini send draft → vendor@newco.io

Mar 28, 2024, 2:30 PM

Needs approval

Hermes delete conversation

Mar 28, 2024, 2:30 PM

Needs approval

Muse read calendar invite

Mar 28, 2024, 2:30 PM

Allowed

Grok Bot read label:Payroll

Mar 28, 2024, 2:30 PM

Denied
Security

Secure at every layer.

Clam runs on Railway. Inbound traffic uses TLS 1.2 and TLS 1.3, with Let's Encrypt SSL certificates. Data is encrypted in transit and at rest with AES-256, and private networking uses WireGuard. Railway is SOC 2 Type II and SOC 3 certified. Inspect their reports on the Railway Trust Center, or read our security manifesto.

AICPA SOC report: Expected in Q4 2026
AICPA SOC 2 report: Expected in Q4 2026

Expected in Q4 2026

What's next

Where Clam is going

Clam opens as a capped beta on Gmail in mid October. These are the milestones after it.

MVP

Mid October 2026

Capped Beta Launch

Early adopters get access by invitation and tell us what to fix.

GA

Mid November 2026

General Availability and Clam for Business

Clam opens to everyone. Clam for Business brings company-wide rules, approvals and audit trails to Google Workspace and Microsoft 365.

V2.0

December 2026

Outlook support

Connect an Outlook mailbox to Clam as well as Gmail.

FAQ

Frequently asked questions

Still have questions?

Email us at support@useclam.ai

Give your agents an inbox you control

Share your inbox with your first agent in minutes and see every action it takes.

Get early access