Renting a mail server costs you very little. The real cost shows up later. It's the staff hours, the blocklist delisting you're still chasing at 11pm, and the client whose open rates collapsed because a different client uploaded a five-year-old list. Weigh up a self hosted mail server vs third party delivery platform for client campaigns and the hosting fee turns out to be the smallest number in the sum.
Below we set four real setups side by side. They are a self-hosted server, a raw delivery relay, a separate marketing account for each client, and a white-label platform. We use SendTo as the white-label example because it's ours and we know how it works. Each option gets an overview, a strength, a weakness, who it suits and a verdict. After that we put all four in one table and cost them in staff hours for a 10-client agency.
Here's our argument in one sentence. The cheapest setup overall is the one where someone else owns deliverability and you own the client relationship and the price. We'll also say plainly when self-hosting still wins, because in a few cases it does.
Quick pick: most agencies should not run their own mail server for client campaigns
Here's the short answer on self hosted mail server vs third party delivery platform for agencies. Don't self host client marketing email unless you fit one of the narrow cases near the end of this piece. Here's the one-line fit for each option.
- Self-hosted server: a team with a full-time sysadmin sending for one large brand.
- Delivery relay: a developer-led agency that already builds and maintains its own software.
- Per-client marketing accounts: a freelancer or agency with two or three clients.
- White-label platform: an agency that wants to resell email marketing as its own product, at its own prices.
Option 1: A self-hosted mail server gives you total control and total responsibility
This is an open-source mail transfer agent running on a virtual server you rent or a dedicated box you own. A mail transfer agent (MTA) is the software that queues outgoing mail and hands it to the receiving servers. Your agency installs it, configures it, secures it and keeps it alive. Nobody else is involved.
You own every layer, from the IP address to the bounce handling
First comes authentication. Reverse DNS maps your server's IP address back to its hostname, and receivers distrust a server without it. SPF is a DNS record that lists the servers allowed to send for a domain. DKIM signs each message with a key so receivers can tell it wasn't altered on the way. DMARC tells receivers what to do when SPF or DKIM fails and where to send reports. TLS encrypts the connection between servers. You'll need all five set up for every client domain you send for.
Then comes the work that never ends.
- Bounce processing, so dead addresses get removed after the first hard bounce.
- Complaint processing through the feedback loops that mailbox providers offer.
- Unsubscribe handling, including the one-click unsubscribe header that large receivers now expect.
- Queue management when a receiver defers your mail and messages start piling up.
- Blocklist monitoring, because nobody emails you to say you've been listed.
- Patching the operating system and the MTA before someone turns your server into an open relay.
Strength: the marginal cost per email is close to zero
This advantage is real. Once the server is running, sending another 100,000 emails costs you no more than the monthly rent. There are no per-send fees and no contact tiers. You control every setting, from retry intervals to connection limits, and you know exactly where every message and every subscriber record is stored. For a business that has to keep its data in one country, that last point counts for a lot.
Weakness: a fresh IP has no reputation, and one bad client list can poison it for every client
A new IP address is cold. Receivers have no sending history for it, so they throttle it, defer it or send its mail to spam until weeks of steady, clean volume build up trust. That's why your mail lands in spam even though SPF and DKIM pass. Authentication proves who sent the message. Reputation decides whether the receiver wants it.
Next comes the shared-fate problem. Put ten clients on one server and they all share one IP reputation. If one client imports an old trade-show list full of dead addresses and spam traps, the bounce rate spikes and the IP gets blocklisted. Then every client's newsletter goes to spam the next morning, including the clients who did nothing wrong.
Finally, someone has to be on call. Delisting means finding the cause, fixing it, filling in each blocklist's removal form and waiting. If that someone is you, it happens on your evenings.
Suits a technical team sending for one brand at steady, high volume
This fits a business with a full-time systems administrator, one sending brand, one list it fully controls and a predictable daily volume that keeps the IP warm.
Verdict: defensible as infrastructure for one brand, a liability as a client service
For one brand with in-house ops, self-hosting is a fair choice and cheap per message. For an agency sending for many clients, it puts every client's inbox placement behind the worst list among them, and makes your team the help desk.
Option 2: A third-party delivery relay fixes sending but leaves you to build the product
A delivery relay is a hosted SMTP service or sending API. SMTP is the standard protocol for passing mail between servers. Your software hands each message to the relay, and the relay delivers it from infrastructure the provider runs. You then build your own campaign tool on top or bolt one on.
The relay handles IP reputation and the agency handles everything a client sees
The relay gives you managed IP addresses that are already warm, step-by-step help publishing SPF and DKIM records, automatic suppression of hard bounces, and webhooks that tell your system about every bounce, complaint and delivery. What it doesn't give you is everything a client touches. That means the email editor, list import, segments, signup forms, reports, the client login and billing.
Strength: established sending reputation without running hardware
You skip the cold-IP months, the port 25 fight and the patching. Relays handle millions of messages a day, publish uptime figures and keep their documentation thorough, so a competent developer has mail flowing within an afternoon.
Weakness: developer time becomes the hidden monthly bill
The relay invoice is small. Building and maintaining the front end is not. Every client request for a new segment rule or a nicer report turns into a development ticket. On cheaper tiers you share IPs with other senders you've never met, so their bad week becomes yours. And the relay's open tracking counts every pixel load, including automated link and image checks run by corporate security tools, unless you write the filtering yourself.
Suits an agency with in-house developers that already ships software
This fits a shop that already runs its own product, keeps developers on payroll and treats a custom campaign tool as an asset it wants to own.
Verdict: strong plumbing, but plumbing is not a product you can sell
A relay solves delivery properly. It still leaves you building and supporting a marketing product before you can charge a client for one.
Option 3: Separate marketing accounts for each client are simple to start and messy to scale
Here each client takes out their own subscription to an off-the-shelf email marketing app. The client pays, or you pay and pass it on, and your team logs in to build and send campaigns.
Deliverability is handled, but the brand on the login screen is not yours
Your work week runs like this. You keep a password manager full of logins and a spreadsheet of who's on which plan. You get a separate invoice per client, each with its own renewal date. The app handles sending, but every screen your client sees carries someone else's name.
Strength: no infrastructure work and a fast start for one or two clients
You can send a first campaign the same day. Templates, a drag-and-drop editor, unsubscribe links, bounce handling and consent tools for GDPR all come built in. For one or two clients, nothing starts faster.
Weakness: per-client fees stack up and the client can see what you are reselling
Each new client adds another subscription, and per-client usage fees rise as their lists grow, which eats your margin. The client can see exactly which tool you use, so they can cancel you and keep the account. And because every account reports in its own way, putting together a consistent monthly report across ten clients is manual work.
Suits a freelancer or small agency with a handful of clients
This fits a freelancer or a two-person agency running email for two or three clients who are fine knowing which tool sits underneath.
Verdict: fine as a stopgap, weak as a business model
It gets campaigns out quickly with no technical risk. It doesn't give you a product of your own, a margin you control or a reason for the client to stay.
Option 4: A white-label platform like SendTo turns delivery into a product the agency sells
SendTo is an email marketing platform that you launch under your own brand. You pay us one flat partner fee, you set the monthly price your clients pay you, and each client buys their own sending usage on top. We don't publish figures here because prices change, so check the pricing page for current plans.
SendTo runs the sending stack so the agency runs the client relationship
We check addresses before anything is sent, so dead mailboxes never reach the receiver. New sending domains get automated warmup, and dispatch speed is set per mailbox provider and per domain. Campaign volume goes out through multi-domain distribution across brand-matched sending domains, so no single domain carries the full load. Platform-wide suppression keeps known bad addresses out of every list.
Strength: deliverability, production and billing arrive already built
SendTo designs HTML emails in seconds from a campaign brief and your brand presets, with one-click remixes. An AI reviewer checks the subject line, structure, language, links, alignment and basic compliance before launch. Signup forms are protected against bots and come with optional double opt-in. Clients log in to a portal with your branding, and reports leave out security scanner opens, so both you and your client see opens, clicks and bookings from real people.
Weakness: you give up root-level control of the servers
You can't tune the MTA, choose retry intervals or SSH into anything. New features follow our roadmap, not yours. And the flat fee only pays off if you actually sell email to several clients.
Suits agencies that want recurring platform revenue from existing retainer clients
This fits an agency with a base of retainer clients that wants to turn its advice into a monthly platform subscription, sold under its own name.
Verdict: the lowest total cost for an agency whose product is client results, not servers
You give up server-level control. In return you stop paying for the hours, the delistings and the development that the other three options hand back to you.
Side by side, the options split on who carries deliverability risk
Put the four setups in one grid and one row decides the rest. Who owns the IP and domain reputation? Whoever owns it also owns the warmup, the list checks, the delistings and the late-night support calls. The table below sets the four out on the criteria an agency actually pays for.
| Criterion | Self-hosted server | Delivery relay | Per-client accounts | SendTo white-label |
|---|---|---|---|---|
| Setup time | Days to weeks, plus months of IP warming | An afternoon for mail flow, months to build a front end | Same day per client | Hours to launch your brand, minutes per new client |
| Ongoing staff hours | High, ops and support every week | High, mostly developer time | Medium, logins, invoices and manual reports | Low, campaigns and client work |
| Who owns IP and domain reputation | You, for every client on the server | The relay owns IPs, you own domains and list quality | The app vendor | SendTo, spread across brand-matched sending domains |
| Warmup | Manual, by you | Shared IPs come warm, dedicated IPs you warm yourself | Handled by the app | Automated on every new sending domain |
| List verification | Build or buy it yourself | Bounce suppression only, verification is yours | Varies by app | Addresses checked before sending, platform-wide suppression |
| Bot-filtered reporting | Only if you write the filter | Only if you write the filter | Varies by app and account | Security scanner opens excluded by default |
| Client-facing brand | Yours, if you build the interface | Yours, if you build the interface | The vendor's | Yours, in a branded client portal |
| Pricing control | Full, once you have a product | Full, once you have a product | Low, the client can see the vendor's price | Full, you set every client price |
| Fit with the February 2024 bulk-sender rules | You implement every requirement | Relay helps with authentication, you build unsubscribe and complaint handling | Built in | Built in |
| Best fit | One brand with in-house ops | Developer-led agency | Two or three clients | Agency reselling email to several clients |
Read the reputation row again. In the first two columns, one client's careless import lands on you. In the last two, someone else carries that risk, and only the last column also lets you put your own name and price on the service.
The real cost of a mail server is measured in hours, not hosting fees
So is it cheaper to run your own mail server than to pay a delivery platform? Only if your hours are free. The server rent is the smallest line in the sum, so we cost each option in staff hours per month for a 10-client agency. We use a sample rate of 60 an hour in whatever currency you bill in. Swap in your own figure.
The rules that came in last month raised the hours for anyone running their own stack
Since February 2024, the largest mailbox providers have enforced new requirements for bulk senders, meaning anyone sending around 5,000 or more messages a day to their users. Every message needs SPF and DKIM, and the sending domain needs a published DMARC record that aligns with them. Marketing mail needs a one-click unsubscribe header, with requests honoured within two days, and the full one-click requirement lands on 1 June 2024. Spam complaints have to stay below 0.3%, and you're wise to aim well under 0.1%.
For an agency, that counts per client domain. Ten clients means ten DMARC records to publish and monitor, ten complaint rates to watch and an unsubscribe flow that works for all of them. On a platform that's already done. On your own server or relay, it's your build and your monitoring.
A worked month for a 10-client agency
These are typical monthly hours, with one-off setup spread over 12 months. Monitoring covers blocklists, queues, DMARC reports and patching. Delistings is the average month, which hides the bad one where you lose two days.
| Hours per month | Self-hosted server | Delivery relay | Per-client accounts | SendTo white-label |
|---|---|---|---|---|
| Setup, spread over 12 months | 4 | 7 | 1 | 1 |
| Monitoring and maintenance | 8 | 4 | 2 | 1 |
| Delistings and incidents | 5 | 1 | 0 | 0 |
| Building and fixing features | 10 | 16 | 0 | 0 |
| Admin, reporting and support tickets | 6 | 5 | 12 | 3 |
| Total hours | 33 | 33 | 15 | 5 |
| Staff cost at 60 an hour | 1,980 | 1,980 | 900 | 300 |
| Plus software or hosting | Server rent | Relay usage | Ten subscriptions | One flat partner fee, see the pricing page |
The self-hosted server and the relay end up close, for different reasons. One spends the hours on ops, the other on development. Per-client accounts cut the hours but add ten subscriptions, and most of those 12 admin hours go on switching logins and stitching ten report formats into one monthly summary. The white-label row isn't zero. You still answer client questions and plan campaigns, but that's work you can bill for.
One hidden cost doesn't show in the hours. Every dead address you send to is a hard bounce against the reputation you share. That's why verifying lists before you send matters so much, and we've set out when automated email list cleaning is worth it in a separate piece.
Self-hosting still wins in three narrow cases, and agencies rarely fit them
We said we'd give self-hosting its due. Here are the three cases where it's the right call.
Strict data residency. Some public-sector, health and legal clients need every subscriber record and every message to stay on hardware in one country, under their direct control. If the contract demands it, your own server meets it.
One very high-volume sender with an in-house ops team. A single brand sending millions of messages a month, at steady daily volume, to a list it collected itself, keeps its IPs warm and its reputation in one set of hands. With a full-time sysadmin on payroll, the near-zero cost per message adds up to real savings.
Internal or transactional mail only. Password resets, system alerts and staff notifications go to people who expect them, at low complaint rates, with none of the marketing rules around unsubscribes. A small server handles that well.
Client marketing email misses all three. Your senders are several brands, not one. Their volume is lumpy, with a quiet June and a heavy November and December, so the IPs cool off and get throttled right when the peak arrives. Their lists come from clients you don't fully control. And it's marketing mail, so every February 2024 requirement applies. If a client truly needs data residency, treat that as a separate project for that one client, not a reason to put the other nine on your server.
Overall verdict: sell results, not server maintenance
Here's our ranking for agencies sending email for clients, in order.
- White-label platform first, for most agencies. SendTo carries the deliverability risk, the production and the billing, so your hours go on client results and you set the price.
- Delivery relay second, for developer-led shops that already ship software and want to own a custom campaign tool.
- Per-client accounts third, as a stopgap for two or three clients while you work out whether email is a product you want to sell.
- Self-hosted server last, kept for data residency, one very large in-house sender or internal mail.
Put the whole comparison in one sentence and it's this. The hosting fee is never the expensive part, the hours are, so hand the hours to whoever already owns deliverability and keep the client and the price for yourself. SendTo isn't the right pick if you need root access to your servers or sell email to only one client. For an agency with a base of retainer clients, it's the setup where the cost lands least on you.
If you advise agencies on this choice as a consultant, a blogger or a creator, you can turn that advice into commission. Our affiliate programme pays you 20% of the platform fee, the partner subscription, that each agency you refer pays SendTo, every month that agency pays it. You never get a share of what that agency's own customers pay the agency. Attribution lasts 90 days from the first click, and the first touch wins. We pay commission monthly, by PayPal.
Send agency owners this comparison and earn 20% of the partner subscription each agency you refer pays, every month it pays.
Join the SendTo affiliate programme


