MG Software B.V. (eigen product)2025 - heden
MG Mailserver - Transactional email on Amazon SES
About this project
A self-built transactional email platform: a Resend-compatible API, Amazon SES as the delivery engine, and a dark-themed web app to manage sent mail, domains, API keys, and delivery status. Includes OTP login via Supabase, domain verification with BYODKIM, per-domain SMTP credentials, and Kubernetes-ready deployment.
The challenge
For our own products and clients we needed reliable outbound email without being locked into a single SaaS pricing model. Integration had to stay simple for developers (familiar API shape), and the team needed visibility into bounces, delivery, and per-domain configuration, without exposing sensitive production data in marketing assets.
The approach
MG Mailserver runs on Next.js 15 with PostgreSQL (Supabase), Supabase Auth with OTP, and the AWS SDK for SES including webhook handling for delivery events. Scheduled sends and bulk campaign delivery run through Trigger.dev background tasks. The UI includes an email log with search filters and export, campaigns, domains (verification, DNS checks, SMTP credentials), API keys, and metrics. The stack is containerised and deployable on Kubernetes with HPA.
Outcome
- Resend-compatible API for fast adoption in existing apps
- Central visibility into sent mail and delivery status
- Per-domain SMTP and API key management with SES verification
- Passwordless OTP login and role-based admin flows
- Production-ready containerised deployment with Kubernetes scalability
What is in it
Resend-compatible send API
Drop-in style replacement for common transactional mail SDK patterns so existing integrations can point at your own SES-backed endpoint.
Delivery log & webhooks
Processed SES/SNS events for statuses such as delivered and bounced, searchable log, filters, and export, suited for support and debugging.
Domains, DKIM & SMTP credentials
Add domains, check DNS, verify in SES, BYODKIM where applicable, and generate or revoke IAM-based SMTP credentials per domain.
Images
Need a system like this?
In a one-hour conversation you know whether it is a portal, an integration or a rebuild. No sales deck. An honest yes or no.