One endpoint. Every provider you already pay for.
Point your application at one hostname and route intelligently across every provider you’ve attached — without changing a line of send code, and without a proprietary protocol in the middle.
Two providers. Two SDKs. Two sets of pager rules.
Marketing is on one platform, transactional is on another, and the in-house shim that decides which lane a message takes was written in a hurry two years ago by an engineer who has since left. Every provider change means a code change; every incident means a deploy; and switching away from either provider is a project nobody has budget for.
sendrules sits in front of the providers you already trust and moves the routing decision out of your application. Attach the accounts, define the rules, and every send from every service goes through one endpoint — you can add, remove, or reweight a provider without touching send code.
Your accounts. Your warmed IPs. Your pricing.
We don’t buy sending capacity and mark it up. You attach the provider credentials you already hold — Amazon SES, SendGrid, Postmark, Mailgun, SparkPost, Brevo, Resend, Mailjet, Elastic Email, SMTP2GO, Zoho, Google Workspace, Microsoft 365, Mailcrux, or any custom SMTP endpoint. Provider economics stay yours. IP warmth stays yours. If you leave sendrules, your sending relationships are untouched.
Compatible with the providers you already use — bring your own credentials, keep your reputation.
Real SMTP. Every client works, unchanged.
TLS on both submission ports with a real Let’s Encrypt certificate. Password authentication over TLS. Every SMTP client library in every language talks to us without modification — no vendor SDK, no proprietary wire format, and no rewrite the day you decide to leave.
One workspace never sees another’s traffic.
Providers, rules, suppression lists, domains, and audit logs are scoped by tenant at the database layer. Role-based access governs who inside a workspace can attach a provider or edit a Grid. There is no shared send queue across tenants; one workspace’s traffic can never be delivered on behalf of another.