Inboxes

An inbox for each agent or each job, on a domain you own or on one of ours. An agent that files receipts gets its own address; so does the one that answers support, and so does the nightly job that only ever reports. Each inbox has its own history, its own keys and its own rules, and an inbox can be moved between the people and projects of an account without changing its address or losing a thread.

The API

Everything an inbox does is reachable through an API: read what arrived, send a reply or a fresh message, search by sender, subject, label or date, and file mail with labels so the next reader finds it where it belongs. Replies stay with the message they answer; a conversation is a thread, not a pile of loose messages, whichever side started it.

SMTP submission

Software that already speaks SMTP can hand mail to us on the submission port with its inbox credentials, over an encrypted connection. The same sending class, the same metering and the same signing apply whichever door the message comes in by.

Forwarding

An inbox can forward what it receives to an address you have proven you own. Proof means a confirmation message to that address and a click on the link in it; the step cannot be skipped, by you or by an agent acting for you, and a forwarding rule stays off until it is done.

Webhooks

When a message arrives, when a message you sent is delivered, and when one bounces, we call the URL you gave us. Every call is signed so your side can tell our notices from anyone else's, and a call that fails is retried before it is given up on.

People

A few people can share a few inboxes: the person who checks on an agent, the one who answers when a human needs to, the one who holds the keys. Each has their own login and their own access, and none of them is a seat you pay for. Pricing follows what the account sends and stores, not how many people look at it.

Sending, metered

Sending is metered as it happens, per inbox and per domain. A loop that starts sending the same message a thousand times is slowed on the first few, not discovered the next morning: the sender is told to wait and the message is never silently dropped. The limits are the ones on the acceptable-use page, and they rise on request when a sender has shown it behaves.

Delivery

Mail to the large providers is watched and tended every day: what they accept, what they defer, what they put somewhere other than the inbox, and what the blocklists say about our addresses and yours. Every sending domain carries SPF, DKIM and DMARC records, and a problem on our side is treated as an outage and worked until it is fixed.

Kept until you delete it

Mail stays in the inbox until the account deletes it. There is no retention clock quietly removing last year's correspondence, and nothing that expires because a plan changed. Delete a message, a thread or an inbox and it is gone; keep it and it stays.

Opening an account

Accounts are opened by request. There is no signup button on this site; tell us what you want to send, from where and to whom, through the contact page, and a person writes back. Every account is admitted to one sending class under the acceptable-use policy and agrees to the terms.