SMTP proxy
One endpoint across every provider you attach.
Learn moreEvery send routed, verified, warmed and observed — through the providers you already trust.
Nine capabilities that work together — routing, verification, ramp-up, shaping, monitoring, and inbound — behind one endpoint and one dashboard, without changing a line of send code.
Sound familiar?
Six tabs open before you’ve found the problem.
It’s Tuesday. Support tells you a customer’s onboarding email didn’t land. Your ESP dashboard shows a delivery, your bounce ledger lives in a spreadsheet, your DMARC report reader is a separate tool, and your blocklist checker sits on someone’s laptop. Twenty minutes in, you still can’t say which provider sent it, which check ran, or why the recipient never saw it.
sendrules puts all nine of those tools in the same product, on the same tenant, over the same route log. When something goes wrong, the answer is one screen away — with the rule that matched, the provider that handled it, and the reason it deferred.
Everything on one platform
Nine capabilities, one platform, one dashboard.
Every capability writes to the same route log and reads from the same tenant boundary. There is no second product to buy, no plugin to enable, no separate contract for the parts that used to live elsewhere.
Grid & Rules
Six routing strategies with coverage warnings.
Learn moreQuality Gate
Every recipient verified before the send.
Learn moreISP-aware routing
The recipient's real mailbox provider decides the lane.
Learn moreRamp-up
Auto-warmup that pauses itself on bounce or complaint.
Learn moreLimits and queue
Four limit tiers, and we queue instead of dropping.
Learn moreWebhooks
Signed, retried, replayable from the UI.
Learn moreActivity
Seven filtered inboxes with share links and sparklines.
Learn moreInbound
Replies, bounces, and out-of-office turned into contact lists.
Learn moreWhat happens on a single send
One send. Every capability, in order, on the same route log.
Your application hands us a message. Every recipient is verified before the send — rejected addresses never reach a provider and never spend your quota. Surviving recipients enter a Grid, which resolves the mailbox provider, picks a sending path under the strategy you chose, and enforces the four limit tiers before dispatch. The chosen provider sends. Provider events feed the Activity view, DMARC monitoring, Postmaster views, and any signed webhook you’ve registered — all on the same tenant, in the same product.