Sending email for several brands means each one needs its own domain, reputation and audience, kept apart. We build white-label email platforms where many isolated workspaces share one deployment, and every campaign page becomes its own report after it sends.
In short
TheSaaSPeople builds white-label, multi-tenant bulk email platforms. Our own product, Dispatch, is live at ec.thesaaspeople.com: each workspace has its own contacts, campaigns, brand, sending domain, API keys and users, and every message leaves through one delivery path that handles rendering, tracking, throttling, per-workspace DKIM signing and provider failover. Each campaign report measures delivery, opens and clicks against published industry averages.
Teams that send newsletters and product updates either pay per-contact pricing on a hosted tool, or run a mail server with no reporting, no bounce handling and no answer when a send goes wrong. Anyone sending for several brands also needs each one isolated, with its own domain and reputation. And when bulk and transactional mail share one queue, a large newsletter can hold up a password reset.
We separate the console from delivery. The web console never sends mail itself: it writes rows and queues jobs, and a separate worker delivers through a self-hosted Postal server or SMTP. Bulk and transactional mail run on separate queues, and a send already in flight can be paused without dropping or double-sending a single recipient. Each workspace signs mail with its own DKIM key.
Not theory, systems we have shipped and that are running today.
Dispatch is our own email platform, built and run by TheSaaSPeople and live at ec.thesaaspeople.com. In August 2026 it was cut down from a nine-subsystem suite to one job done properly: write an email, choose who gets it, send it, see what happened.
Each workspace has its own contacts, campaigns, templates, brand, sending domain, API keys and users, and its mail is signed with that workspace's own DKIM key. One deployment hosts many workspaces without their audiences or sending identities mixing.
No. Bulk and transactional mail run on separate queues, so a large newsletter cannot delay a password reset. A send already in flight can also be paused without dropping or double-sending a single recipient.
The console never sends mail itself. It writes rows and queues jobs, and a separate worker delivers through a self-hosted Postal server or SMTP. Every message leaves through that one path, which handles rendering, tracking, throttling, DKIM signing and provider failover.
Dispatch runs 850 automated tests and exposes Prometheus metrics. After every send, the campaign page becomes its report, showing the funnel, mailbox providers, clicks and failure reasons.
Tell us what you are running. We will tell you exactly how we would approach it, within 48 hours, no pitch.
Not sure what it would cost? Scope it in a minute