Email infrastructure, without the bullshit
Provision the domain.
Keep sending.
Receipts, password resets, shipping notices — the mail your site has to get out shouldn't ride on a shared web host's SMTP server. RelayForge stands up a locked-down AWS SES sending identity for each site: DKIM, MAIL FROM, isolated SMTP credentials, and bounce monitoring, with the exact DNS records ready to hand off.
Why this exists
Shared hosting can't be trusted with email that has to arrive.
Retail and SaaS sites on shared hosting send their operational mail through whatever SMTP server the host hands them — shared IPs with no reputation, aggressive rate limits, no DKIM alignment. Order confirmations land in spam. Password resets never arrive.
AWS SES fixes deliverability, but doing it properly is a project: a domain identity, EasyDKIM keys, a custom MAIL FROM subdomain, a configuration set wired to bounce and complaint events, and an IAM user scoped so tightly a leaked SMTP credential can't touch anything else.
Do that by hand for every site and it's slow and easy to get subtly wrong. Skip a step and deliverability quietly rots months later.
RelayForge does the whole sequence the same way every time, then keeps an eye on how each site is sending.
How it works
Three steps, then it's just sending.
Add the site's domain
RelayForge provisions the SES identity, EasyDKIM (RSA 2048), a custom MAIL FROM subdomain, a dedicated least-privilege SMTP user, and a configuration set wired for event tracking.
Hand over the DNS records
Give the site owner the exact records to publish, copy-paste ready. RelayForge polls every ten minutes and notifies you once — when the domain verifies. No console babysitting.
Send, and keep watching
Drop the per-domain SMTP credentials into the app, fire a one-click test email, and monitor bounce and complaint activity per site and across every site you run.
What you get
The whole setup, done consistently.
Per-site SES identities
Each site gets its own EasyDKIM identity (RSA 2048) and custom MAIL FROM subdomain. No shared configuration, no noisy-neighbor reputation.
Isolated SMTP credentials
A dedicated IAM user and permissions boundary per domain. A leaked credential has a blast radius of exactly one site.
Copy-paste DNS, automatic verification
The exact records the site owner needs, ready to hand off. RelayForge polls SES and tells you once, when it verifies.
Ongoing feedback monitoring
Configuration sets and SES event destinations are wired for you. Watch bounce and complaint activity per site and account-wide.
Multi-tenant by design
Group sites into workspaces, keep every tenant's sending isolated with SES tenant separation, and invite the people who need access.
Sign-in that holds up
Google sign-in, multi-factor auth with recovery codes, and an audit log of who changed what.
Who it's for
Technologists who need operational email to just work.
Developers, sysadmins, and consultants running sites — often retail — on infrastructure that was never meant to send mail. If you own the AWS account and set up sending for each property, RelayForge turns a repetitive, error-prone setup into one short, consistent onboarding.