Shared inbox agents
Add an agent to support@, ops@, editor@, or your personal inbox. Same mailbox, same workflows, better coverage.
Read the shared inbox page →BYO email for agents
Envelope connects to the mailbox you already use — same address, same folders, same habits. Your agent reads OTPs, handles replies, runs rules, and drafts for your approval. Nothing moves until you say so.
Use cases
Add an agent to support@, ops@, editor@, or your personal inbox. Same mailbox, same workflows, better coverage.
Read the shared inbox page →Stop paying for a simple SMTP/API layer your own server can run. Keep app email close to the product and under your control.
Read the Mailgun alternative page →Claude Code, Codex, Hermes, and OpenHands need mailboxes for OTPs, replies, confirmations, and long-running workflows.
Read the agent infrastructure page →Named workflows
Your agent calls envelope code --wait 60 and blocks. When the OTP arrives, the CLI returns it. No polling loop, no parser, no race condition against your own inbox.
Agent proposes rules based on what it found in your inbox. You see exactly which messages each rule would touch before anything moves. Confirm, edit, or reject. Rules export to Sieve if your server supports it.
A local dashboard that is both a full mail client and an agent control plane. Read, search, star, archive, and triage with Gmail-style keyboard shortcuts (j/k, r, e, ?), while the cockpit strip surfaces drafts queued for approval, rule-run history, watch state, failed auth, and an event timeline. Approve, edit, or discard agent work from one place.
Export a thread as raw RFC822 files with a manifest and checksums. Useful when you need a verifiable record — for legal holds, compliance review, or a paper trail your agent assembled during an investigation.
Human control
By default, every draft goes into a review queue. Rule runs preview affected messages before anything moves. The cockpit shows the full history. You can pause, override, or stop any workflow.
This isn't a safety flag bolted on at the end. Agent contexts default to draft-only mode. Autonomous send is an option, but you have to opt in explicitly — and every action is logged either way.
Every send decision produces a policy audit event. No secrets in the logs.
Works with your existing stack
If it can run a CLI command or speak MCP, it works with Envelope. The same JSON surface works from a shell script, a Hermes pipeline, a Claude Code tool call, or a Codex exec loop.
Drop in via MCP. Full inbox access as a tool call.
CLI + JSON surface for terminal-native autonomous loops.
First-class skill for Hermes profiles and multi-agent pipelines.
OTP handling, watch events, and thread-aware follow-up.
Long-running loops that wait on email before continuing.
Why not the alternatives?
These provision a new mailbox on their infrastructure. New address. DNS changes. Your mail in someone else's system. If your agent needs to operate on the inbox your contacts already use, you're at the wrong starting point.
Envelope connects to the mailbox you already have. Nothing migrates.
If all you need is authenticated SMTP and a small API for product email, paying a third-party relay can be pure duplicate infrastructure. Envelope gives your own server a simple mail runtime without surrendering the mailbox or adding another vendor bill.
For huge marketing sends, use a bulk sender. For ordinary app email and agent workflows, BYO email is saner.
Solid tools built for humans reading their own mail. Envelope is built for the case where an agent is the primary consumer: IMAP IDLE watch, OTP extraction, JSON everywhere, reviewable rules, and a control plane for the human sharing the inbox with the agent.
Annual licensing
Annual bands sized by mailbox users on your domain. No per-message metering, no seat trickery.
Personal
For individuals running their own mailbox
Team
Up to 10 mailbox users on one domain
Growth
Up to 25 mailbox users, one domain
Enterprise
26+ users, multi-domain, or embedded/OEM
Licenses are billed annually. Quotes and invoices on request; payment by card or bank transfer. Email ty@tmrtn.com for anything not covered above.