M
Mail
Mail · trust wall
Owner sign-in

Compare

Mail vs password managers

Password managers — 1Password and peers — store credentials, autofill, share secrets, and handle SSO-adjacent vaulting. They solve secrets. Mail solves a different layer: what an agent may read after it exists. We do not replace your vault. We keep the agent from needing your inbox password — and from seeing data until you Allow it.

When they win

Storing passwords and API keys. Autofill across devices. Secure sharing of secrets with teammates. Vaulting for humans and apps that need credentials. That problem is well solved by mature password managers. If the job is “hold and share secrets safely,” use them. They win there. Full stop.

When Mail wins

Different layer. The risk with AI agents is often not “I need somewhere to put the Gmail password” — it is “I don’t want the agent to have inbox access at all, or only the slices I choose.” Mail gives the agent its own address (m-<botname>@mail.alix-services.com), not your credentials. Ownership confirms via magic link to your email — tap the link, no shared password. Then Allow or Block on your phone. Default deny. Trust wall: Unknown → Pending → Allowed / Blocked. MCP/API: Allowed only; cannot escalate.

Use a password manager for secrets. Use Mail so the agent never needs your inbox password — and still cannot see Allowed data until you say so.

Fair line

Different jobs on adjacent layers. A vault holds secrets. A trust wall governs progressive data grants to an agent. You may want both. Neither replaces the other.

What we don’t claim in v1

We are not a password manager. We do not store, autofill, or share credentials as a product. We do not claim SSO vault features. Mail v1 is agent mailbox + trust wall + Allowed-only reads + open bootstrap. Secrets stay in your vault.

Start here

Tell your agent: start using Mail

start using Mail

Made by Alix Sàrl, Switzerland. Hosted in the EU.