Pricing that names the limits.
Four planned paid plans. Monthly is the default. Annual billing shows the total commitment first, then its calculated monthly equivalent.
Approved planned pricing: USD per workspace; self-service plans cover one human owner.
Compare capacity and boundaries.
Planned capacities follow the approved catalog. Enterprise capacity and commercial terms require a quote.
| Allowance | Plus | Pro | Agentic | Enterprise |
|---|---|---|---|---|
| Monthly | $9/month | $19/month | $49/month | Custom |
| Annual commitment | $90/year | $190/year | $490/year | Custom |
| Annual monthly equivalent | $7.50/month equivalent | $15.83/month equivalent | $40.83/month equivalent | Not displayed |
| Active inboxes, including Personal/root | 15 | 50 | 200 | Negotiated |
| Active addresses | 100 | 500 | 2,000 | Negotiated |
| Pooled storage | 5 GiB | 25 GiB | 50 GiB | Negotiated |
| Agent API/MCP operations per month | 50,000 | 250,000 | 1,000,000 | Negotiated |
| Agent API/MCP operations per minute | 60 | 180 | 600 | Negotiated |
| Outbound envelope recipients per month | 1,000 | 5,000 | 20,000 | Negotiated |
| Outbound envelope recipients per UTC day | 100 | 500 | 1,000 | Negotiated |
| Already-owned domain connections | 0 · planned | 1 · planned | 3 · planned | Negotiated |
| Sending eligibility | Human-approved | Human-approved | Explicit opt-in · planned | Negotiated, explicit opt-in |
| LLM inference | Not included | Not included | Not included | Not included |
Counting rules in plain language.
Minute limits use a rolling 60-second window. No overage invoices or add-on SKUs are activated here.
- Active inboxes
- Personal counts; collections and All Mail do not.
- Retained bytes
- Archives continue counting toward storage.
- API operations
- REST and MCP share one monthly allowance.
- Envelope recipients
- Unique normalized To, CC, and BCC recipients count.
Prototype boundary. Quota enforcement, checkout, exports, and domain connection are not activated by this pricing surface.
Pricing questions.
Straight answers on trial state, capacity, sending, domains, and the product boundary.
An agent receives the inboxes named in its grant, with the actions you select: read, search, organize, or draft. Send permission is separate, and the demonstrated send path stays behind human approval.
OtterMailGive your agent one inbox to start.
Review the design previews, then contact us about future alpha access. Access is not guaranteed; public signup is unavailable.