Boundaries
What we do not claim
A page that only lists what a product does is half a page. These are the things a buyer will otherwise assume, and each one is a no with a reason attached.
This page exists because the most expensive thing a product can do is let someone discover a limit after they have committed to it. Everything below is cheaper to read now.
Eight refusals
Each one is a no, and each one has a reason
No inbox-placement promise Deliberately not built
Nobody gets to decide what another company's spam filter does. Records can be correct and a signature can be real and a receiving server may still route a message somewhere you did not want. We describe what the mechanisms do and stop there.
Not a bulk-mail platform Deliberately not built
There is no list manager, no campaign builder, no segmentation, and no open-rate dashboard. You write and send from an inbox, one message at a time. For some buyers that is disqualifying, and it is better to find out on this page.
The domain is not yours Deliberately not built
This is an address at mitto.email, which we run. You choose the name in front of the @, not the part after it. If the part after the @ has to be your own domain, tell us when you write and we will answer honestly rather than sell around the question.
Sending is not live today Built, latched off
The owned mail server's accept latch is off. A send today becomes a durable queued row and is recorded as queued. Nothing reports a delivery that did not happen.
Messages go out unsigned today Built, latched off
The DKIM keystore is empty by default, so the resolver returns no key and the message is sent unsigned and flagged unsigned. A fabricated signature would be worse than none.
No archive migration Deliberately not built
There is no automated import from an old account. Forwarding from the old address plus a note on the way out is the honest first move, and we would rather say that than sell a migration we have not built.
Not a shared team inbox Deliberately not built
This is a sending identity, not a ticketing system. There are no queues, no assignment, and no SLA clock. A role address can be shared by the people who cover it; that is a different and much smaller thing.
No delivery-rate figure Deliberately not built
You will not find a percentage on this site. Any number of that shape would be either measured on someone else's traffic or invented, and we do not have traffic of our own to measure yet.
Money
Catalog prices, not a charge
We show figures so you can plan a budget, not because you can buy right now. There is no buy button anywhere on this site and no signup that bills. Turning a mailbox on is a founder-confirmed step and it is currently off.
- Prices shown are catalog estimates, not a charge -- checkout is not open yet.
- Mailbox provisioning is a founder-confirmed step and is currently off; no mailbox is created and no card is billed.
- A branded address is a professional mailbox, not a claim that any specific school or studio uses it.
Nothing on this site creates a mailbox or moves a cent. When that changes, this page will say so in the same plain words it uses now.
Where AI is, and is not
No AI writes anything you send from here
There is no drafting assistant on this surface, no subject-line suggester, and no rewriting pass over a message you composed. Nothing here reads your outbox to improve anything.
The wider codebase does contain a message-personalization pass. It is honest to say it exists and dishonest to let you infer more than it does, so: it may touch a subject line and an opening line and nothing else, it is structurally forbidden from touching a receipt or an authentication link, and it only runs at all when a caller injects a provider that runs inside our own network. No provider is wired into this surface. Every error or guard trip in it returns the original message unchanged.
So the state today is: no AI writes a message on this product, no AI drafts one, and no AI rewrites one. If that ever changes it will be stated on this page before it ships, not discovered afterwards.
packages/notifications/src/ai/personalize.ts:83 (the excluded kinds) · :109 (the in-network-or-skip check)
Questions
What people ask before they ask about price
Can I send today?
No. The owned mail server's accept latch is off until the endpoint is provisioned in our own network. A send becomes a durable queued row and the system records it as queued, not sent.
Will my messages be signed?
Not today. The signing path is built and the keystore is empty, so a message goes out unsigned and is recorded as unsigned. When a key is provisioned the same path signs for real.
Can I use my own domain instead of mitto.email?
Not through this page. You choose the name in front of the @ here. Ask us if the part after the @ has to be yours and we will tell you honestly whether we can do it for you today.
Do you promise my mail lands in the inbox?
No, and neither can anyone else. What we can be held to is whether the records are correct, whether a signature is real or absent, and whether a failure is reported honestly.
Is there a dashboard showing who opened what?
No. There is no open tracking and no campaign reporting on this product. If that is what you need, this is the wrong tool.
What happens to the addresses of people who reply to me?
They stay inside our own private system rather than being handed to an outside marketing company, and they are not sold. We do not call the mail untouchable or claim it can never leave; we run the system ourselves and keep the handling tight, and that is the honest version.
Can several people share one address?
A role address can be covered by more than one person, so a reply still goes out under the same name when someone is away. That is sharing, not a ticketing system with queues and assignment.
Are the prices on the pricing page what I will pay?
We do not know, and neither does anyone else yet. Those are catalog figures for planning. Checkout is not open, nothing is billed, and the numbers exist so a budget conversation can happen.
Elsewhere on this site
The rest of it
Overview
What a sending address is, and why the from-line is the whole product.
Read it →The wire
The eight-step SMTP session our own transport runs, and what each reply lets us conclude.
Read it →Authentication
DKIM, SPF, DMARC, the return path and BIMI -- what each does and which are live today.
Read it →Pricing
Catalog figures for planning a budget. Checkout is not open and nothing here bills.
Read it →