A newsletter you run on your own server

Mailpiece

A newsletter you run on your own server, with no monthly bill and no one watching your readers. And you get the code, too.

If you've written on Substack or Mailchimp, you already know how to write with Mailpiece. The difference is where it lives: your server, your domain, your list. Your agent can take the chores, from the draft to the test send to the schedule.

Install Mailpiece

> This week's issue: why we left the cloud, from notes.md.
  Keep it spicy, send me a test, schedule it for Tuesday 9:00.

● Read notes.md
  ⎿  two years of server bills, one conclusion
● post create We left the cloud
  ⎿  draft
● post test
  ⎿  sent to [email protected]
● post schedule
  ⎿  Tue 21 Oct, 09:00

The draft is in your inbox. It goes to 1,204 people
on Tuesday at 9:00 unless you tell me to change it.

> 

Make writing newsletters fun again.

Name it, write, send. That's the whole job.

  1. Name it

    Give your newsletter a name and say what it's about. It lives at your own domain.

  2. Write a post

    It saves as a draft until you say otherwise.

  3. Send yourself a test

    Then publish it, or schedule it for a morning you pick.

  4. Let readers in

    They subscribe on your own pages and leave in one click. Bring the list you already have.

  5. See how it did

    How many liked the issue, how many said it wasn't for them, and how many subscribed from it.

Let's be honest: the newsletter tools we loved grew into marketing software, keeping your list in their databases and watching which reader opened what.

Mailchimp became a marketing suite whose bill grows as your list grows.

Kit became a shop for selling to your list, one tag and funnel at a time.

beehiiv brought ads and referrals, and a bill past 2,500 readers.

Substack grew its own network, and keeps a cut when readers pay.

Our friends at HEY World, Pagecord and Keila stayed kind. But name one of the big ones that got simpler last year. Exactly.

It's time to put the letter back in newsletter.

Introducing Mailpiece — a newsletter you run yourself and write with your agent.

It lives on your server and your domain, and the list is yours. Each issue leaves from your own mail provider, under your name, with no tracking pixel. Anything you can click, your agent can do: draft the post, send you a test, schedule it.

It's free and open source. Install it, send your first issue, and write back. I'm glad you're here, and I'd love to hear what you think after an issue or two.

Your list belongs on your server

Your posts and your readers sit on a server you rent or own, where no newsletter company's staff, support panel or analytics vendor can open them.

Where mailing lists leaked

Coming from Mailchimp?

Newsletter tools grew into marketing software. Mailpiece went the other way.

Mailchimp is built to grow your bill as your list grows. In Mailpiece, every new reader is good news, and never a bigger Mailpiece bill. Substack is built to grow its network, and keeps a cut when readers pay. In Mailpiece, your readers know your name, not a platform's. Kit is built for selling to your list, one tag and funnel at a time. In Mailpiece, you feel like a writer again, not someone running a funnel. Ghost is built for paid memberships, and its own hosting bills as members come. In Mailpiece, you just write, with no members, tiers or themes to look after. Buttondown is built to be quiet, and its bill grows with your list. In Mailpiece, you keep that calm, and the list is yours, on your server. beehiiv is built to grow your list fast, then bill you past 2,500 readers. In Mailpiece, each issue is about what you wanted to say, not a sponsor.

Read the full comparison →

Nothing to outgrow, nothing to escape

What you write comes back out as you wrote it, wherever you take it next.

Your name on every issue, never ours

Each issue leaves from the mail provider you choose, so the trust your readers give you stays yours: connect yours.

Ask your agent about Mailpiece

Don't take our word for it: paste this into Claude or ChatGPT.

I write a newsletter and I'm on Mailchimp. Read mailpiece.dev and tell me what I would gain and lose by running Mailpiece on my own server.

Mailpiece next to the others

One page each, with who should pick them instead.

Your newsletter, on your server, today

Install it, open it, and write your first issue.

Read the install guide

Then hand it to your agent.