Choosing subscription and paywall tech: the honest comparison

Subscription technology for publishers sorts into three tiers: full paywall and subscription-management suites built for newsrooms (Piano, Zephr and peers), all-in-one newsletter platforms with payment rails (Substack, beehiiv, Ghost), and the assemble-yourself stack of a membership plugin on a standard CMS. Published pricing differs by an order of magnitude across tiers — Substack charges a percentage of revenue, beehiiv prices by scale with its own ad network attached, Ghost licenses by monthly tier, and enterprise suites are quoted individually and typically run to five figures a year — and the honest comparison is less about features than about what your business cannot afford to lose when it outgrows the choice.

Licht Journal publishes information, not procurement advice; all terms cited are from vendors' published pricing pages and documentation, which change — verify before deciding.

What does each tier give you?

Newsletter platforms bundle the whole loop: publishing, email delivery, payments, subscriber management and basic analytics. The trade is structural: your data lives in their system, export exists but integrations are limited, and advanced paywall logic — dynamic gating, A/B testing by segment, complex bundling — is either absent or constrained to what the platform supports. Substack's published terms take 10 percent of paid revenue plus processing; beehiiv's published pricing is tiered flat-fee with monetization add-ons; Ghost is flat-fee with Stripe passed through — the revenue-share question alone can exceed the entire cost difference at scale.

Enterprise suites (Piano, Zephr and comparable vendors) sell exactly what platforms don't: fine-grained gating rules, experimentation infrastructure, identity and consent management, integrations with CRM and analytics stacks, and support contracts. They cost real money — five-figure annual contracts are the norm at published enterprise pricing — and they assume a team to operate them. Buying a suite without an operator is buying a gym without a trainer and never going.

The DIY stack — WordPress plus a membership plugin ( WooCommerce/Memberful-class tooling) plus an email vendor — keeps fees near zero and control total, at the price of assembling, updating and debugging the plumbing yourself. It fails quietly: a broken renewal webhook bleeds subscribers while the team is busy publishing.

How should a publisher actually choose?

Decide by exit cost, not feature checklist. Every tier does payments and email; the differences that matter appear when you leave. Can you export subscribers, content and — critically — subscription billing relationships? Substack and Ghost let you export the list; whether Stripe customer objects port cleanly determines whether a migration preserves recurring billing, and that detail, documented in each platform's own migration guides, is worth more than any feature matrix. Second decision variable: revenue share versus flat fee. At $10,000 monthly subscription revenue, a 10 percent platform take exceeds $12,000 a year — more than most enterprise tools once you are large enough to need them. The crossover math, run on your own projections, usually makes the tier decision for you.

What generalizes?

Start simple, plan the exit, and re-run the fee math every quarter — the pattern across every published migration story (newsletters leaving Substack for Ghost or beehiiv, publishers leaving DIY for suites, enterprises simplifying back down) is that the first choice is cheap to make and expensive to undo, and the second choice is driven by revenue scale, not feature envy. What does not generalize is any specific vendor's current pricing — published terms change frequently in this market, and the durable evaluation criteria are exit cost, revenue-share structure and whether the tier's weaknesses are weaknesses your business model actually touches.