Apex Relay
In progress
Your systems speak to your people through one rail, so the record of what was sent lives in one place.
See it
Cloud infrastructure engineered for the systems above. There is no public website to open; it is delivered inside a commission.
Functional scope
A single send API that every product calls. Email and text go out the same way, with the same template layer and the same audit trail.
Templates that render correctly in the mail clients people actually use, including the ones that ignore background colours on buttons.
A delivery log per message: queued, sent, delivered, opened where the client reports it, with the reason attached when a message does not land.
Domain setup handled once per brand, so mail from your systems arrives authenticated under your own name.
Users and roles
Your operations lead reads the delivery log. Everyone else just gets their mail.
Workflow in practice
Messages go out on schedule. A weekly summary shows volume, delivery rate, and anything that bounced, with the fix beside it.
In production
- One call sends either email or text
- Every message carries a readable delivery record
- Templates hold their shape in the strict mail clients
Build status
In the shop now, with a date we will name.
Included in every system we build
This is foundation, not a product. It ships inside the systems it belongs to, and its cost is already in their figures.
If a system you are commissioning does not already carry this piece, adding it is a line in your quote, not a second purchase.
It is here so you can see what you are getting rather than take our word for it.
Rails used
Stack
- Next.js
- Postgres
- Resend
- Webhooks
Handover includes
- Source for the send service and the template layer
- Your authenticated sending domain
- The delivery log schema and its policies
- Template set with previews
Ask about Apex Relay
Tell us how your business runs today and we will show you which systems carry this piece and what they would cost you.