The overlay
Keep your ESP. Add the layer that makes it reliable.
You don't have to rip anything out. Egressif sits on top of the email provider you already pay for, watches every send, recovers when a path fails, and gives you the evidence your provider never did.
How the overlay works
Your ESP becomes one path. We become the layer above it.
What the layer adds
What you gain on top of moving mail.
Monitoring on the wire
We watch the actual responses your sends get from receivers, in real time, across every path. Blocklistings, reputation signals, deferral waves, and auth failures get caught as they happen, not in a weekly export.
Ordered failover
Your providers and our network become ordered paths. When one is blocked or throttled, traffic moves to the next automatically. A single provider having a bad day stops being your outage.
Route engineering
Decide how mail leaves: which path per destination, priority for time-sensitive messages, per-receiver throttles, separate lanes per stream. Routing becomes something you configure, not something a single vendor decides for you.
Suppression at the gate
Bounces, complaints, and do-not-contact requests are enforced beneath every application and every path, so an upstream mistake cannot send to someone who already opted out.
Evidence per message
For every message: which server accepted it, when, over what TLS, with the verbatim response, retained on your terms rather than expiring in a provider’s short window.
One provider for the whole stack
DNS, mailboxes, and sending under one operator instead of a different vendor for each layer. Fewer seams, and one team accountable when something breaks instead of a finger-pointing call.
Consolidated view
Every stream and every path in one place: what sent, what landed, what is at risk. Stop stitching together a separate dashboard per vendor to answer one question.
One vendor, one bill, one API
A single relationship, a single invoice, and one API for provisioning and delivery events, instead of integrating, reconciling, and paying several.
No migration
You keep your provider, your templates, and your code. Point your sending at us and your current setup keeps carrying traffic until you are satisfied.
Stream separation
Transactional and marketing stop sharing a reputation. Each stream earns its own, so a campaign can never sink a password reset.
Works with what you run
Bring your provider. We set it up.
The overlay connects to your sending over SMTP, and usually your provider's API too: we generally need API access to provision the path, route through it, and keep everything in sync. Because we host your DNS, the authentication that makes mail land (SPF, DKIM, DMARC) is configured and maintained on our side. So there is no rigid list of "supported providers" to check against, but it is a guided setup, not a paste-in-your-SMTP-and-go switch. The major ESPs and your own infrastructure all fit. Here is where teams usually start.
Two ways to work with us
Overlay today, whole stack later. Both work.
Start as a layer above your current provider. If you ever want us to own DNS, mailboxes, and the network too, the path is already there.
Managed
We run it for you.
Routing, suppression, warming, reputation, and incident response are ours. You get plain-language reporting on what happened and what we did. The email part of your week goes quiet.
Self-serve
You drive it.
Provision domains and mailboxes, set routing and fallbacks, and pull delivery data through the console and API. The same engine, operated by your team, at your pace.
FAQ
Overlay questions, answered.
Do we have to leave SendGrid, SES, or Postmark?
No. That is the whole point. Your provider stays and becomes one routed path under our operating layer. We add the monitoring, failover, suppression, and evidence around it.
How long does switching the sending side take?
Usually an afternoon. You point your application at our relay or API, your templates stay untouched, and your current provider keeps carrying traffic until you are confident.
What does the layer actually do that our provider does not?
It watches the responses your mail gets, reroutes around blocked or throttled paths, enforces suppression beneath every app, and keeps per-message delivery evidence. Providers move mail; they do not operate your deliverability for you.
Do you support our provider?
Most major providers, yes. We connect over SMTP and usually the provider’s API, and because we host your DNS we set up and maintain the authentication (SPF, DKIM, DMARC) that makes mail land. So it is a guided setup rather than a paste-in-credentials switch: SendGrid, Amazon SES, Postmark, Mailgun, the Google Workspace relay, and your own infrastructure all fit. Tell us what you run and we will confirm.
Can you also just be the whole stack?
Yes. Many clients start as an overlay and later hand us DNS, mailboxes, and sending on our own network. You choose the pace.
Related reading
Go deeper in the reference library
Put the layer on top of what you already run.
Tell us your provider and your volume. We will show you exactly what the operating layer would add, and what it costs.