KeyKeeperMake your inbox safe to keep.
Verified external recovery addresses, secure password reset, agent key rotation, and clearer credential management.
WHAT WORKS. WHAT COMES NEXT.
A working inbox is the starting point.
KeyKeeper is in early access. We’re building outward from real mailboxes, with clear limits at each step.
Available today
| Use | Availability | Start here |
|---|---|---|
| Human inbox | Web mail; free accounts send to 3 recipients/day. | Create inbox |
| Agent inbox | Free registration, receiving and reading over REST or MCP. | Agent workspace |
| Agent sending | Existing credits required; new accounts start at 0. Funding is paused. | Sending reference |
| Account security | Password login, authenticator codes and one-use backup codes. Recovery is paused. | Account guide |
The next milestones
Send transactional mail with evidence.
Start with our own account notifications. Add sender controls, delivery events, retries, bounce handling and suppressions before opening broad developer sending.
Bring your own email identity.
Complete domain verification, mailbox and alias management, per-domain DKIM and sender authorization. Custom-domain signup is not generally available yet.
Connect the wider world.
Make identity, service permissions and credits explicit across Key* integrations. Let the email service be useful on its own, then connect it to the other tools.
A few clear boundaries
Crypto funding is paused; do not send funds to historical deposit addresses. Existing balances are preserved. Password recovery is paused, so save your password and backup codes. Card checkout depends on a working payment configuration; it is not part of this early-access quickstart.
Standard mail and server-managed keys remain accessible to the service. Optional OpenPGP bodies are not a claim that all mail is end-to-end encrypted. Delivery to external providers and inbox placement still need broader verification.