Paywall implementation — Piano, Zephr & subscription integration

A paywall is a product, not a plugin

The difference between a paywall that converts at 1% and one that converts at 4% is almost never the vendor. It is the meter design, the registration funnel, the checkout friction, and whether the whole thing renders fast enough that readers actually see it. We implement paywalls as products: measured, iterated, and owned by a team that carries the revenue number.

Piano, Zephr, Limio, CeleraOne — honest vendor guidance

We have deployed all four at European publishers, so our advice is based on integration reality, not sales decks. Piano is the full suite — metering, entitlements, checkout, analytics — right when you want one vendor and accept its opinionated data model. Zephr is a rules engine for teams that already have identity and checkout and need intelligent access decisions on top. Limio excels at checkout and subscription lifecycle. CeleraOne fits DACH publishers with complex SSO requirements. We will tell you which fits your stack — including when the answer is "keep what you have".

Meter design: where the money actually is

Every high-performing deployment we run shares three traits. A registered-free tier that converts anonymous readers into known users — registration is the strongest predictor of subscription. Dynamic, segment-aware meters instead of one global number — a breaking-news skimmer and a Sunday long-read subscriber should not hit the same wall. And server-side wall rendering: a paywall that flickers in after the article trains readers to wait, and destroys your Core Web Vitals in the process.

Identity first, checkout last

The integration order that works: SSO and identity, then metering, then checkout, then analytics. Projects that start with checkout — because revenue feels urgent — rebuild it within a year when the identity layer changes underneath. We have untangled enough of those to insist on the boring order.

Subscriptions across every channel

A reader who subscribes on the web expects the app to know. We unify entitlements across web, iOS, and Android — including the App Store and Google Play purchase flows — so a subscription bought anywhere works everywhere, and your support inbox stays quiet.

See how subscription infrastructure fits a full publisher platform in our NZZ case study, or read our field guide to paywall integration.