If you want to send a newsletter, you will quickly hit a fork in the road that nobody explains well. A tool like Mailchimp or Brevo or Mailjet offers to do “everything,” and it is tempting to just sign up and be done. Before you do, it helps to understand that a newsletter is really two jobs, not one. When you let a single company do both, you hand them something you did not need to.

The two jobs

Job one is holding your list and writing the email. Your subscribers’ names and addresses, the proof that each one agreed to hear from you, the signup form on your site, the drafts you are still working on. This is the valuable, personal part. It is also the part that is genuinely yours.

Job two is delivery. Taking a finished email and actually getting it into a few hundred inboxes without landing in spam. This is a real technical job. It needs a trusted sending reputation, bounce handling, and one-click unsubscribe built in. It is the kind of plumbing that is hard to do well yourself, so it is reasonable to pay someone for it.

Here is the thing most newsletter companies will not say out loud: these two jobs do not have to live in the same place. When they do, the delivery company also ends up holding your list.

Why keeping them separate matters

Think about what each job actually needs to see.

The delivery service only needs to see an email in transit. It takes the message, sends it, and is done. It never needs to keep a copy of your whole subscriber list sitting in its cloud.

But when you use an all-in-one platform, that is exactly what happens. Your list, your consent records, and your signup forms all live on their servers. That creates two quiet problems:

• Lock-in. The day you want to leave, your list is on their side of the fence. Moving means exporting, importing, rebuilding your forms, and hoping nothing breaks. Companies know this, and it is part of why prices drift up over time. You are not really free to walk.
• Exposure. Your subscribers trusted you with their address, not a vendor you picked. The more companies that hold that list, the more places it can leak, be sold, or be handed over.

Our first plan, and the problem we hit

Our first plan was the sensible middle path: keep the list on our own site with a WordPress plugin, and hand only the delivery job to an outside service connected as a plain pipe. The list stays home, a vendor just carries the envelope. That is a genuinely good setup, and for a lot of small orgs it is the right one.

Then we went looking for the pipe, and ran into something we did not expect. We care about not depending on Big Tech, so we wanted a sending service that was not built on Amazon, Google, or Microsoft. We checked the popular “EU-friendly” options by reading their actual infrastructure documents, not their marketing. What we found:

• Mailjet runs entirely on Google Cloud. There is no “own servers” version of it.
• Brevo runs mostly on a French host (OVH), but still uses Google Cloud for backups and overflow. Better, but not clean.
• Several services that advertise “secure EU servers” turned out to run on Amazon underneath once we read the fine print.

So “EU-based” was proving geography, not independence. Amazon, Google, and Microsoft all run data centers inside Europe. And there was a second issue underneath the first: even a clean pipe still means a vendor does your sending. We would have moved one dependency (the list) home while leaving another (delivery) in someone else’s hands.

The setup we chose: host the whole thing ourselves

So we went further than our first plan. Instead of a list at home and sending rented out, we now run both jobs on a server we control:

• The list, the signup forms, and the campaign tool run on Listmonk, an open-source newsletter app, on our own rented server in Germany. Nobody else holds the list.
• Sending will run from that same server, so the email leaves our machine directly rather than passing through a third party’s cloud.

The plain-English version: the list is yours and stays home, and you also own the mail truck, not just the envelope.

Being honest: this is the harder path

We are not going to pretend self-hosting is free or effortless. It is the most independent option and the most demanding one. Two real costs:

• You own deliverability. A brand-new sending server has no reputation with Gmail and Outlook, so you have to warm it up: send slowly at first, to your most engaged subscribers, and build trust over about three to four weeks before mailing the whole list. A managed service does this for you.
• You own the plumbing. Setting up the sending software and the security records (the DNS entries called SPF, DKIM, and DMARC, which prove an email really came from you) is a one-time job, but it is your job.

We took this on because independence from Big Tech is the whole point of Desk Ready, and because running it ourselves means we can teach it. It is not the right answer for everyone, and that is fine. There is an honest spectrum here:

• Easiest sovereign path: a managed newsletter service that runs its own non-Big-Tech infrastructure and handles deliverability for you, such as Rapidmail (Germany) or Mailpro (Switzerland). You pay a monthly fee and give up a little control. For most small orgs this is the right answer.
• Middle path: keep the list on your own site (a WordPress plugin like MailPoet) and connect a delivery pipe. Just check where that pipe actually runs before you trust it.
• Full control: host it all yourself, the way we did. Most independent, most work.

What to look for if you do this yourself

• Keep your list on infrastructure you control, your own site or your own server, so no vendor becomes its owner.
• Check whose servers your delivery actually runs on, not what country the company is in. “EU data center” can still mean Amazon or Google. The only proof is the provider’s own sub-processor list or a quick technical lookup, never the homepage.
• Set up the trust records (SPF, DKIM, DMARC) for your domain. This keeps you out of spam folders and stops anyone forging your address.
• One-click unsubscribe and clear consent at signup. This is not just good manners, it is the law in much of the world.

None of this requires you to be technical to understand. It just requires knowing the fork in the road is there, and choosing how far down the independent path you want to walk.