Proof you can hand to the other side.
Turn a mail a provider accepted into a signed certificate covering the content hash, DKIM, the provider handoff, and the delivery events the provider reported. Its signature and timestamp verify in anyone's browser without contacting us.
When a recipient insists an email never arrived, or arrived saying something else, the argument is usually memory against memory. A proof-of-delivery certificate ends it: Mailway binds the message's SHA-256 content hash, its original DKIM signature, the provider handoff, and the provider's delivery events into one Ed25519-signed document with an RFC 3161 timestamp.
A certificate also says where its evidence stops. Acceptance is Mailway's own record of the provider handoff; delivery is the provider's event; and a mail with no delivery event is certified as accepted, never more. It can't show whether a person opened the mail, because Mailway adds no tracking to your message (how verification works).
of delivery
“I never got that email.”
Here’s the receipt.
Every SMTP-relayed message is archived with its raw MIME and original DKIM signature. Any mail a provider accepted can be turned into an Ed25519-signed proof-of-delivery certificate, countersigned by an independent time authority so it can't be back-dated, and the certificate says whether it proves acceptance or delivery. The signature and the timestamp verify in anyone's browser, with no call to our database; compare the certificate's key with Mailway's to know it came from us. Share the rendered email itself with a private mailway.to link, and settle the dispute instead of having it.
Certificates are included on Business and up, and share links on Pro and up. Free has 1 limited share link a month.
30 days on Free, 90 days on Pro, 6 months on Team, 1 year on Business, custom on Enterprise, with retention add-ons (+1 year, +3 years, +7 years, or unlimited) for SOX, HIPAA, and FINRA record-keeping. All of it EU-hosted.
What Mailway stores
stays on European soil
EU data residency
Your mail is received, routed, and archived inside the European Union, all in Germany: the servers in Falkenstein, the archived messages in Frankfurt (AWS S3). Not an optional EU region: the only one.
Encrypted in transit & at rest
TLS on every SMTP connection, both STARTTLS and implicit TLS. Stored payloads compressed and encrypted at rest.
Your keys only
Pure BYOK. Your mail rides your own provider accounts, never pooled with other Mailway customers. Your reputation stays yours.
Proven in production
5+ years of real customer volume, 889,000+ messages, 99.9% accepted by a provider after failover.
one EU region today, with additional regions on the roadmap as we grow
Your mailer config has
one block to change
Mailway is in private beta, and we onboard teams one at a time. Leave your email and we'll send your invite when it's your turn.