Choose
Hosted vs self-hosted email software
What you gain and what you take on when you run your own mailing-list software instead of paying for a hosted service.
Updated 5 min read
Most people who send newsletters use a hosted service: you sign up, pay a monthly fee or use a free plan, and the provider runs everything. A smaller group runs their own mailing-list software on a server they control, and pays a separate service to deliver the messages. Both approaches work well. They suit different people.
The difference is not really about cost, although that is usually why people ask. It is about who does the work, who carries the risk when something goes wrong, and how much control you want over your data and your sending.
What “hosted” means
A hosted email service, sometimes called an ESP (email service provider), gives you the whole stack in one account:
- The software: editor, lists, forms, automations and reports.
- The database where your subscribers are stored.
- The sending infrastructure: mail servers, IP addresses, bounce handling and complaint processing.
- Security updates, backups and support.
Mailchimp, Brevo, MailerLite, Kit, EmailOctopus and the other hosted tools on this site all work this way. You pay for convenience, and the price usually rises with the size of your list.
What “self-hosted” means
With self-hosted software you install the mailing-list application yourself, on a web server or virtual private server you rent or own. The software manages your lists, campaigns and subscribers. It does not usually deliver the email itself; instead it hands messages to a sending service over SMTP or an API. Common sending services include Amazon SES, Mailgun, Postmark and similar providers.
listmonk, Sendy, Mautic and the self-hosted edition of Mailcoach work this way. You pay for the server, the sending service and, for some, a software licence. Sending services typically charge per message, which can work out much cheaper for a large list.
The trade-offs side by side
| Hosted | Self-hosted | |
|---|---|---|
| Setup | Minutes to an hour | Hours to days, depending on skills |
| Ongoing upkeep | None; the provider does it | Updates, security, backups, monitoring are yours |
| Cost pattern | Monthly fee that grows with your list | Server and per-message sending costs; sometimes a licence |
| Features | Usually richer editors, automations and integrations | Varies; often more basic, sometimes very powerful but complex |
| Deliverability | Provider manages shared reputation and bounce handling | You configure bounce and complaint handling with your sending service |
| Data location | Wherever the provider stores it | Wherever your server is (the sending service still processes messages) |
| Support | A helpdesk | Documentation, forums or a paid specialist |
| If it breaks at 9pm | The provider’s problem | Yours |
When hosted is the better choice
Hosted is the right default for most small organisations. Choose it if any of these apply:
- Nobody in your organisation is comfortable looking after a server, or the person who is might leave.
- Your list is small to medium, so the monthly fee is modest.
- You want a drag-and-drop editor, automations and integrations that just work.
- Several non-technical people will send emails.
- You would rather spend your time on what goes in the newsletter than on how it is delivered.
Clubs and charities run by volunteers should think hard about continuity. A hosted account can be handed over with a password change. A self-hosted install depends on whoever built it.
When self-hosted makes sense
- Your list is large and the cost of a hosted plan is significant, while your sending pattern is fairly simple.
- You or someone reliable already runs servers and is happy to keep one more application patched and backed up.
- You want your subscriber database on infrastructure you control, for policy or contractual reasons.
- You want to choose and switch sending providers without moving your list.
- You need to integrate deeply with your own systems through an API or database.
Example
A small web agency already manages a handful of Linux servers for clients. It sends a monthly newsletter to a large list of past customers and wants to keep costs predictable. Installing listmonk on an existing server and connecting it to a sending service is a modest job for them, and they already have backups and monitoring in place. For a three-person craft business with no technical help, the same setup would be a liability.
What you take on when you self-host
If you go the self-hosted route, plan for these jobs from the start rather than discovering them later.
- Security updates for the application, its language runtime, the database and the operating system. Mailing-list software holds personal data and has a public sign-up form, so it is a target.
- Backups of the database, tested by actually restoring them somewhere.
- Sending service setup: verifying your domain, getting out of any sandbox or trial limits, and setting sending rates.
- Bounce and complaint handling: connecting the sending service’s notifications back to your software so hard bounces and spam complaints are suppressed automatically. Skipping this is the fastest way to damage your reputation.
- Authentication: SPF, DKIM and DMARC on your domain, aligned with your sending service. See SPF, DKIM and DMARC explained.
- One-click unsubscribe headers, which the big mailbox providers expect from bulk senders. Check that your software adds them. See deliverability basics.
- Scheduled jobs (cron) for sending queues and automations, and monitoring so you notice when they stop.
- Documentation so someone else can take over.
Data protection either way
Self-hosting does not take you out of UK GDPR; it changes who your processors are. With hosted software, the email provider is your processor. With self-hosting, your server host and your sending service are processors instead. Either way you need a lawful basis for emailing people, a privacy notice that names who handles their data, appropriate security, and contracts with your processors. The guide to growing a list legally covers consent and records.
A middle way
Some tools blur the line. Mailcoach, for example, offers both a hosted service and a self-hosted edition, and is designed to work with a sending provider you choose. Some hosted services let you bring your own sending domain and dedicated IP addresses. If you like the idea of control but not the upkeep, look for a hosted tool that lets you export everything easily, so you can move later if you need to.
The short answer
If you are asking the question and nobody in your organisation already runs servers, choose a hosted service. If you do run servers, have a large list and simple needs, self-hosted software with a reputable sending service can be excellent value. Whichever you pick, authenticate your domain, keep consent records and make sure you can export your list.