Every emailyour app sends,accounted for.
Point your SMTP config at Mailway and keep sending the way you always have. Behind it: automatic failover across your providers, a delivery timeline for every message, and an archive that can still prove what you sent years later, if it comes to that.
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, Gmail, and any SMTP provider.
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 a REST API.
Paste in the keys you already have
Add your provider API keys, assign them to projects, pick failover, free-first, round-robin, or random per project. All from the dashboard, with no deploy and no DNS archaeology.
Mailway takes it from here
Routing, retries, suppression, logging, archive. The next time someone asks about an email, you look it up instead of guessing. And switching providers never touches your code again.
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. The host is the only line that changed.
- 02 · Written down first
Nothing is acknowledged until it's on disk.
Mailway writes the message to its ingest queue, and only then answers 250 OK. 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: Amazon SES first, SendGrid behind it.
- 04 · The failure
Amazon SES rejects the credentials.
Someone rotated the SMTP password 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 Amazon, not your message, so there's no point waiting on it. The retry goes to the next provider in your chain, and SendGrid accepts in 142 ms. No deploy, no code change, nobody paged.
- 06 · The inbox
The invoice lands. Your customer never knew.
And the record doesn't claim more than it knows: SendGrid confirmed acceptance, so it says accepted. Delivered is a separate fact, recorded when a provider reports it.
- 07 · On the record
Every attempt, every answer, the bytes themselves.
Months from now, when someone asks whether that invoice went out, you look it up instead of guessing.
scroll to scrub · or press play
Not just sent.
Provable.
A delivered message can be minted into a certificate: the content's SHA-256, the sender's DKIM verdict, the provider's acceptance, the mailbox-side delivery event. All of it is sealed with Mailway's signature and countersigned by an independent timestamp authority, so not even we could back-date one. It verifies offline, with standard tools, and it names who attested each claim: Mailway for the stored bytes, your provider for the delivery.
And where proof runs out, the certificate says so: accepted and delivered are different claims, never blurred.
How the notary worksOne 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
Search the exact HTML, text, headers, recipients, and attachments your application handed off.
Explore the archiveFailover without a redeploy
Keep multiple providers behind one endpoint. Mailway routes around timeouts, outages, and billing failures.
See provider failoverOne inspectable timeline
Follow a message from SMTP receipt through rules, provider attempts, acceptance, and delivery events.
Inspect observabilityProof 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 demoNot 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 →Your email stays
on European soil
EU data residency
Your mail is ingested, routed, and archived inside the European Union, on Mailway's own servers in Germany. Not "EU region available". EU, full stop.
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, 865,000+ messages, 99.6% provider-accept rate. Not a weekend project.
one EU region today, with additional regions on the roadmap as we grow
Your mailer config has
one line 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.