One SMTP endpoint, many tenants
Point every campaign tool at smtp.sendrules.net. The AUTH credential picks the tenant; the tenant's routing rule picks the provider. No per-client SMTP re-setup.
Read moreManage sending for thirty clients on their own provider accounts — one endpoint, per-client rules, no shared credentials.
Four sendrules capabilities mapped to the pain that defines this segment. Every one of them is on the free plan.
You run email for many clients. Each client has their own SES, their own SendGrid, their own domains and DMARC posture. You do not want to hold their passwords, mix their traffic, or ask them to migrate to your ESP. But every campaign tool you attach makes you set that up again.
sendrules is designed multi-tenant. Each client is a tenant with its own routing rules, its own provider credentials (encrypted per-tenant), its own send limits, its own DMARC domain. Your campaign tool points at one SMTP endpoint; the tenant is chosen by the SMTP AUTH credential you supply.
Point every campaign tool at smtp.sendrules.net. The AUTH credential picks the tenant; the tenant's routing rule picks the provider. No per-client SMTP re-setup.
Read moreAttach your client's own SES / SendGrid / Postmark account. Credentials sealed with AES-256-GCM per-tenant. You never see the plaintext, they never leave their own vendor relationship.
Read moreOne tenant, one DMARC dashboard. Aggregate reports arrive at a hosted rua= address per client — no shared inbox, no manual sorting.
Read moreAny filtered activity view generates a read-only public URL. Send it to a client mid-campaign; when the campaign ends, expire the link.
Read moreFive thousand messages a month. Every feature above included. Attach your existing provider and see whether the numbers move.