Compare
Mail vs enterprise DLP / CASB / MCP gateways
Enterprise DLP, CASB, and MCP gateways exist for IT-led organizations that need org-wide policy, regulated data controls, SIEM hooks, and tool-call inspection across many servers. Mail is not that category. It is a trust wall for people and small teams adopting agents — phone taps, not policy packs.
When they win
Regulated environments. Central security teams. Org-wide data loss prevention. VPC gateways. Tool-call DLP across many MCP servers. Compliance reporting and SIEM. If you need enterprise CASB or an MCP gateway as part of an IT program, those products are the right hammer. They win on breadth of policy, deployment models, and institutional controls. We do not pretend otherwise.
When Mail wins
Everyday people and small teams adopting personal or work agents — no IT project required. You tell the agent “start using Mail.” It gets m-<botname>@mail.alix-services.com. You confirm ownership with a magic link to the owner email, then Allow or Block on your phone. Default deny. Trust wall states are clear: Unknown → Pending → Allowed / Blocked. The agent reads Allowed only through MCP/API and cannot escalate. Single-tenant: one owner on one VPS.
That is for anyone adopting AI who cares about trust, not only security engineers. Useful agents. Clear boundaries. No need to call security to try an agent safely.
Fair line
CASB and MCP gateways are the right hammer for enterprises. Mail is the trust wall for humans who just want an agent without calling security. Different buyers. Different jobs. Confusing them helps no one.
What we don’t claim in v1
Mail is not a CASB replacement. Not enterprise DLP. Not a multi-tenant MCP gateway product. Not fine-grained enterprise permission packs. Not SIEM or VPC gateway tooling. We claim a controlled agent address, progressive human authorization, and Allowed-only reads — nothing in the enterprise policy-platform lane.
Start here
Tell your agent: start using Mail
start using Mail
Made by Alix Sàrl, Switzerland. Hosted in the EU.