Every emailyour app sends,accounted for.
Your app has no Sent folder: once SMTP takes a message, no copy is left on your side. Point your SMTP config at Mailway and every message is kept exactly as sent, searchable, and provable for as long as your plan keeps it, with automatic failover across your providers.
private beta · EU-hosted · bring your own providers · watch it fail over →
Bring your own keys, the providers you already pay for
Works with Amazon SES, SendGrid, Mailgun, Postmark, Mailtrap, Brevo, Mandrill, Resend, Mailjet, MailerSend, Nuntly, SMTP2GO, Gmail, and any SMTP server.
The whole migration
is a config change.
Point your app at Mailway
Swap host, port, and credentials in the mailer you already use: Nodemailer, Laravel, Rails, smtplib, whatever ships your mail today. 7 SMTP ports open, so it works even where your cloud blocks the usual ones. Prefer HTTP? There's an HTTP API.
Paste in the keys you already have
Add your provider API keys, assign them to projects, pick fallback, free-first, round-robin, or random per project. All from the console, with no deploy and no DNS changes.
Mailway takes it from here
Mailway handles routing, retries, suppression, and the archive. Switching providers never touches your code again. Here's one invoice's day through it.
One invoice.
One bad password.
- 01 · The handoff
Your app sends the way it always has.
Plain SMTP to smtp.mailway.net on port 587, over TLS. Same mailer, same library. Only the host and the SMTP credential changed.
- 02 · Written down first
Nothing is acknowledged until it's written down.
Mailway writes the message to its ingest queue, and only then answers 250 OK, the SMTP reply that means “received”. Your app moves on in milliseconds.
- 03 · The rules
Your rules read it before any provider does.
The subject contains “Invoice”, so it picks up the billing tag and takes the project's chain: SendGrid first, Amazon SES behind it.
- 04 · The failure
SendGrid rejects the credentials.
Someone rotated the SendGrid API key and one config missed it. A 535 during login is about your provider account, not the recipient, so Mailway files it as an auth failure and keeps the message queued.
- 05 · The retry
Five seconds later, the next provider takes it.
The problem is the SendGrid account, not your message, so there's no point waiting on it. The retry goes to the next provider in your chain, and Amazon SES accepts in 142 ms. No deploy, no code change, no alert for anyone to answer.
- 06 · The inbox
The invoice lands. Your customer never knew.
Gmail's server takes it within a second, and Amazon SES reports that back as a delivery event. Only then does the record say delivered: accepted and delivered are separate facts, each recorded when a provider reports it.
- 07 · On the record
Every attempt, every answer, the bytes themselves.
Kept exactly as sent, for as long as your plan keeps it. Nobody looks at it for months. Then someone does.
“What exactly did we send this customer?”
Your app kept no copy. Mailway did.
Every mail client keeps what you send; your app keeps none of it. Without Mailway, this is where someone greps logs and guesses. With it, legal searches the customer's address and opens every email your app sent them, exactly as sent, with what happened to each: invoice #2041, accepted by Amazon SES on 10 April at 09:41 and delivered to Gmail's server, the reminder before it, the terms change. For as long as your plan keeps them (30 days on Free, unlimited on Enterprise or with a retention add-on).
And it doesn't have to be a developer who looks. Give support or legal a member seat and they answer "what did we send?" themselves, only for the projects you give them.
Not just sent.
Provable.
So legal answers the complaint with a receipt, not a promise. Any message a provider accepted can be turned into a certificate: the content's SHA-256, the sender's DKIM verdict (SMTP mail), the provider's acceptance, and the recipient server's delivery event where the provider reports one. All of it is sealed with Mailway's signature and countersigned by an independent timestamp authority, so not even we could back-date one. The signature and timestamp verify offline, with standard tools, and it names the source of each claim: Mailway for the stored bytes, your provider's event for the delivery.
And where proof runs out, the certificate says so: accepted and delivered are different claims, never blurred. Certificates are included on Business and up.
How the notary worksNot another provider
Mailway doesn't replace SES, SendGrid, or Postmark. It sits in front of them and makes them interchangeable, which changes what they can do to you.
your providers · your keys · one gateway in front
the full comparison →One gateway.
Four pillars.
Mailway sits between your app and the providers you already pay for. Each handoff becomes resilient, observable, and provable.
Product overviewAn archive for every send
Open the exact HTML, text, headers, and attachments your application handed off, found by sender, recipient, subject, or state.
Explore the archiveFailover without a redeploy
Keep multiple providers behind one endpoint. Mailway routes around rejected keys, empty credit balances, and outages.
See provider failoverOne inspectable timeline
Follow a message from SMTP receipt through rules, provider attempts, acceptance, and delivery events.
See the timelineProof that survives the dispute
Create a signed, independently verifiable record of what was sent and when it left your system.
See delivery proofSend one email through the whole system.
Pick the route, fail a provider, hold the send for a person's approval, then watch the record write itself. Browser-only; nothing real is sent.
Open the demoWhat 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.