We built Relayly because we got tired of fighting Gmail.

A team that's spent the last decade running send infrastructure for SaaS companies. We've shipped enough postmortems to know exactly which corners ESPs cut, and which ones we couldn't live with.

Where we run

Two regions today: EU (OVH Gravelines, France) and Canada (OVH BHS, Quebec). Both regions are dedicated bare-metal — not shared hypervisors. We chose OVH for cost-per-IP and the operational latitude they give us on rDNS, port-25 access, and PTR records. The trade-off is we spend more time on infra than a pure-cloud team would.

US region is on the roadmap for late 2026, contingent on a port-25 path with a provider that won't sandbox new tenants for 90 days.

2
Sending regions
9+
Dedicated IPs
99.95%
Uptime, 30d trailing
<1s
API to MTA, p99

What we believe

How we're different (in one paragraph)

The competitors with our feature breadth (SendGrid, Mailgun) are 2x our price at moderate volume and run shared multi-tenant pools that punish you when a co-tenant misbehaves. The competitors with our deliverability craft (Postmark, Resend) don't have marketing automation in-product. We try to be the answer when neither side of that trade is the answer.

The honest pitch

We won't pretend deliverability is solved. We will tell you exactly which IP × domain pair sent your message, how that pair has performed at Gmail / O365 / Yahoo over the last 24 hours, and what we'd change if we were running your sending pattern.

— On the homepage, also true here.

Who we are

Aabhyasa Pte. Ltd., trading as Relayly. Small team. Most of us in Asia-Pacific timezones; on-call follows the sun. No VC pressure to grow at any cost — we want to build something we'd ourselves use for the next decade.

If you want to chat — hello@relayly.io reaches a human, usually within the day.

Working with us

We're not currently hiring publicly, but we're always interested in hearing from infrastructure engineers with deliverability scars. Send a note about the worst inbox-placement bug you ever debugged.