In short
  • Choose for your business model first: sponsorships, paid subscriptions, commerce or B2B leads. Features come second.
  • Check who owns the Stripe account, the subscriber export and the sending domain.
  • Compare how each platform charges: a share of revenue, a plan that grows with your list, or a fee per sale.
  • Test the export before you commit, not when you want to leave.
  • Often the answer is to stay and build what is missing around your platform.

Start with how you make money

There is no best newsletter platform. There is only the best fit for how your newsletter earns.

A paid newsletter lives on its checkout, its paywall and how easily a lapsed reader can come back. A sponsored newsletter lives on ad slots, click reporting and getting sponsor copy into the issue on time. A commerce newsletter needs every send tied to an order.

Most platforms are excellent at one of these and adequate at the rest. Pick for the money first.

The best fit by business model

Six common models, and what each one should weigh most.

Sponsorship-led newsletters

If sponsors pay the bills, the platform matters less than most people think. Direct-sold sponsorships run on outreach, booking, contracts, sponsor copy and reporting. No newsletter platform handles all of that.

What you need from the platform is narrower: flexible ad slots in the template, reliable click tracking and an API, so placements flow in without copy and paste. Beehiiv adds a built-in ad network that can fill unsold inventory. Substack now runs a curated native sponsorship program, with less control over selling and reporting your own placements.

Picture send day at 6 a.m. The sponsor's final copy is buried in an email thread, the link is untracked and the report is due Friday. A new platform does not fix that. A system around the platform does.

Paid subscriptions

For a paid newsletter, look hard at three things: how the platform charges, whose payment account it is, and how the paywall works.

Substack is the fastest way to start charging, and it takes a percentage of paid subscription revenue. Beehiiv and Ghost take no cut of subscription revenue. You pay for the plan or the hosting instead.

Substack and Ghost both run payments through your own connected Stripe account. That detail decides whether paying members can move with you later, and it matters more than any feature on a pricing page.

Commerce-led newsletters

If the newsletter sells products, the email platform should know what readers buy. Klaviyo is built for this, with deep store data, a Shopify integration and revenue attributed to each send.

Kit suits creators selling digital products and paid newsletters through its built-in commerce. It charges a fee per sale, which includes card processing, rather than a monthly revenue share.

The trade-off is editorial. Commerce tools think in flows and campaigns, not issues. Expect to build templates and content feeds so editors are not fighting a store's tools every week.

B2B lead generation

A B2B newsletter is often worth more for who reads it than for how many. Job title, company and industry are what sponsors pay for and what sales teams want.

So weight custom fields, profile capture after signup and an API that syncs readers to your CRM. Check that the platform stores the fields you need and lets you read them back out. Our guide to B2B audience data goes deeper.

This is the model we know best from our own work. A B2B trade newsletter we built for started on Beehiiv, then moved to its own sending infrastructure on Resend once reader profiles and custom workflows mattered more than built-in features.

Multi-title media companies

With several titles, the questions change. Who can see which list? Can one reader subscribe to three newsletters without becoming three billed contacts? Can editors build an issue without touching template code?

Sailthru, now part of Zeta Global, and Iterable are built for scale, personalization and data teams. Both are powerful, and both need technical people to run them well.

Mailchimp is familiar, but it bills contacts per audience, so a reader on three lists can cost you three times. Unsubscribed contacts also count until you archive them. Check billing at the reader level, then check how much engineering time the setup assumes.

Owner-operators just starting

If you are one person with an idea and no list, do not over-engineer it. Pick something you can set up in an afternoon, then write and grow.

Substack and Beehiiv both get you live fast. Ghost asks more on setup and gives you more ownership. Kit fits if you plan to sell a course or product early.

Make two decisions on day one anyway: send from your own domain, and run an export. Both are cheap now and expensive later.

Questions to ask before you choose

Who owns the list and the data?

You should be able to export subscribers, custom fields, engagement history and the archive at any time, without a support ticket. Ask what the export contains. Engagement history is often missing.

Is there an API, and on which plan?

An API is what lets you automate drafts, sync readers to a CRM and feed sponsor placements into issues. Substack has no general-purpose public API. Beehiiv has one, but creating posts through it requires a higher-tier plan.

Ghost, Kit, Mailchimp, Klaviyo, Iterable, Sailthru and Resend all offer APIs of different depth. Confirm the exact endpoints you need on the plan you will actually buy.

Revenue share or plan pricing?

Platforms charge in three broad ways. Some take a percentage of paid subscription revenue. Some sell plans that grow with your list. Some take a fee on each sale.

A revenue share is cheap when you are small and expensive when you are large. Plan pricing works the other way round. Model both at the size you expect in two years.

Then read what counts as a billable contact. Mailchimp counts unsubscribed contacts until you archive them. Klaviyo bills on the profiles you can email, so suppressed profiles do not count.

How much deliverability control do you get?

Can you send from your own domain with SPF, DKIM and DMARC set up properly? Can you see bounces and complaints, and act on them? On a newsletter platform, much of this is handled for you. On your own infrastructure, it is entirely yours, which is both the point and the job. Our deliverability checklist covers the setup.

How much design control do you need?

Substack keeps a consistent look across every publication. Beehiiv and Ghost give you more control over site and email design. Enterprise tools and custom stacks give you full control, and need someone who can write templates.

What will it cost to leave?

Every platform is easier to join than to leave. Leaving can mean broken archive links, automations rebuilt from scratch, paid members asked to re-enter cards and a new sender that has to warm up. Ask about each one before you sign up.

The major platforms at a glance

PlatformFits bestHow it chargesWatch out for
SubstackWriters starting out who want simplicity and a built-in reader networkFree to start; takes a percentage of paid subscription revenueNo general-purpose public API, and a consistent look you cannot change much
BeehiivPublishers growing with referrals, ads and an APIPlans by list size and features; no cut of subscription revenueCreating posts through the API requires a higher-tier plan
GhostPublishers who want an open-source site, memberships and full ownershipManaged hosting plans, or self-host; no cut of subscription revenueMore setup, and self-hosting means owning updates and backups
KitCreators selling products and running automation-heavy funnelsPlans by subscriber count, plus a per-sale fee on CommerceBuilt for creator marketing more than editorial publishing
MailchimpSmall teams that already use it for general email marketingPlans by contact count, including unsubscribed contactsDuplicate contacts across audiences add to the bill
KlaviyoPublishers whose newsletter drives commercePlans by the number of profiles you can emailCommerce-first, so editorial workflows take extra work
Sailthru and IterableMedia companies with data teams and personalization needsEnterprise contractsNeed technical support and specialist template skills to run well
Your own stack (for example Resend)Publishers who want full control of templates, data and pipelinePay for sending, plus the software you build around itNo signup forms, archive or website until someone builds them

Pricing changes often, so check each platform's current plans against your list size and revenue model before you decide. For head-to-head detail, read Beehiiv vs Substack, Ghost vs Substack, Substack alternatives and Beehiiv alternatives.

When a custom stack makes sense

A custom stack means you own the pieces: a sending service, your own templates, your own archive and signup pages, and software that ties them together.

It tends to make sense when:

  • Your production workflow is specific enough that no platform editor fits it.
  • Reader data, such as job title or company, is central to how you make money.
  • You want to own templates, data and sending reputation outright.
  • Platform costs have grown past what software built for you would cost to run.

It does not make sense while you are still finding your audience, or when nobody will maintain it. Resend, for example, gives you broadcasts, segments, topics and a broadcast editor. It does not give you signup forms, an archive or a newsletter website. Someone has to build those.

That is what we did for the B2B newsletter above. Its full archive moved to a static site on its own domain. Signup, profile capture and reporting were rebuilt. Bounced and complaining contacts are now removed automatically.

Most publishers land in between: a platform for sending and a few custom tools around it. That is often the best of both.

A migration-risk checklist

If you are choosing a platform because you are leaving another one, check these before you commit.

  • Subscribers export with custom fields, tags and consent status intact.
  • Paid members can move without re-entering cards, because the Stripe account is yours.
  • Old archive URLs redirect to the new home, so links and search rankings survive.
  • Welcome and re-engagement automations are rebuilt and tested before cutover.
  • SPF, DKIM and DMARC are live on the new sender before the first send.
  • The warm-up starts with your most engaged readers.
  • Signup forms on your site, partner sites and social profiles point to the new platform.
  • Sponsor commitments and reporting are covered for the weeks around cutover.

Our migration guide walks through each step.

Two worked examples

Both publishers are fictional. They show how the questions above play out, not real results.

A solo analyst launching a paid briefing

An analyst wants to write a weekly paid briefing on energy policy. She has no list yet. Revenue will come from subscriptions, with no sponsors planned.

Run the framework. Paid-led, owner-operator, little need for an API. Substack gets her live fastest and puts her inside a reader network. Ghost takes no cut of her revenue and keeps readers on her own site, for more setup.

The deciding question is two years out. If she expects a large paid base, the revenue share becomes her biggest cost, and Ghost looks stronger. If discovery matters more than margin, Substack wins. Either way, she uses her own Stripe account and her own domain from day one.

A trade publisher with three titles

A publisher runs three B2B newsletters in one industry. Revenue is direct-sold sponsorships plus qualified leads for sponsors. The team is small, and many readers subscribe to more than one title.

Run the framework. Sponsorship-led, B2B, multi-title. Reader data and sponsor operations matter most, and billing per reader across titles matters too.

A platform with a solid API, such as Beehiiv, works if the team builds sponsor operations and CRM sync around it. A custom stack makes sense if they want one reader record across titles and production tools they own. Either way, the system around the platform decides whether three titles feel like one business or three jobs.

Signs you have outgrown your platform

  • You are copying data between tools every week.
  • The revenue share costs more than a platform that does not take one.
  • You cannot automate the parts of production that eat your time.
  • Sponsors want reporting or placements your platform cannot provide.
  • Your sales team cannot see who reads what.

You do not always have to move

Often the right answer is to stay put and build the missing pieces around your platform: an outreach system, a sponsor portal, a production pipeline.

A migration puts your list and sender reputation at risk for weeks. Building one missing tool is usually smaller. When moving is right, plan it carefully, or see how we handle platform migrations.

What most guides miss

Lessons from systems we have built and run, not the usual checklist.

Run an exit test before you sign up

Export a test list, your archive and payment data in the first week. If any of it is hard to get out now, it will be harder in three years.

Find out whose Stripe account it is

Some platforms process payments through your own connected Stripe account, others do not. It decides how easily paying members can move later.

Check what is plan-gated in the API

Many platforms advertise an API but limit key endpoints, such as creating posts, to higher plans. Confirm the exact endpoints you need on the plan you will actually buy.

Revenue share compounds

A percentage cut feels small at launch and large at scale. Model it at the subscriber count you expect in two years, not today.

Sponsorships do not depend on the platform

Direct-sold sponsorships can run on any of these platforms. What decides how well they run is the outreach, booking, approval and reporting system around the send.

Your archive is a search asset

Years of issues bring in readers from search. If the archive lives on a platform subdomain, plan where it goes before you choose. Moving it to your own domain, with redirects, keeps those links working.

How we can help

We work across all of these platforms, with help, custom builds, integrations and migrations. Browse our platform pages, or start with a process audit for an honest recommendation.

Sources

  1. Beehiiv Help: Ad Network FAQ
  2. Substack Help: How much does Substack cost?
  3. Substack Help: How do I set up my Stripe account on Substack?
  4. Ghost Help: Connecting Stripe
  5. Kit Help Center: Sell digital products with Kit, overview and FAQs
  6. Mailchimp Help: About Mailchimp pricing plans
  7. Beehiiv Developer Documentation: Create post
  8. Klaviyo Help Center: How Klaviyo billing works
  9. Resend Docs: Sending broadcasts
  10. Resend Docs: Managing segments
  11. Resend Docs: Topics
  12. Substack Help Center: How do I set up a Creator Kit on Substack?
  13. Substack: Terms of Service for the Substack API
  14. Zeta Global: Zeta Global to Acquire Marigold's Enterprise Business

Facts checked against these sources in October 2026.