Zephr is in maintenance mode at Zuora. The entire founding team left in February 2026 to launch MonetizationOS, and Zuora’s recent release notes show zero new investment in the platform.
Meanwhile, 70% of publishers grew subscription revenue in the past year even as traffic declined. The winners stopped optimizing the paywall and started optimizing the reader journey.
If you’re a Zephr customer trying to decide whether to renew, here’s what the situation actually looks like and what switching to a WordPress-native paywall would mean for your business.
What’s actually happening at Zephr right now
Zephr is in maintenance mode.
The timeline tells the story. Zuora acquired Zephr for $44 million in September 2022. Zuora itself went private with Silver Lake and GIC in a $1.7 billion deal in February 2025. Then in February 2026, the entire Zephr founding team (James Henderson, Ben Kennedy, Jamie Walker, Courtney Jarret, James Leach) walked out to start MonetizationOS, with Google and Cloudflare backing.
Zuora’s Q2 release notes mention Zephr zero times.
That’s the picture. A subscription experience platform sitting inside a billing company, with no founders, no new investment, and customers locked into the stack.
If you’re running Zephr today, you already feel this. Support takes longer. Roadmap calls dried up. The feature requests you logged 18 months ago haven’t moved.
This is the article publishers on Zephr need to read before they renew.
What “maintenance mode” costs a publisher
You’re paying enterprise prices for a frozen product.
Looking to grow your publication?
Sign up for expert advice straight to your inbox.The obvious cost is the renewal fee on a platform that isn’t shipping. The hidden costs are bigger.
- No roadmap. Henderson, Kennedy, Walker, Jarret, and Leach are at MonetizationOS now. The product vision lives at a different company.
- A bot problem your vendor isn’t visibly addressing. Per the 2025 Imperva Bad Bot Report, 51% of web traffic is now bots, the first time machines crossed the human line in a decade. Most of that growth is AI-driven scraping. Whether Zephr ships new defenses against it is a question, not a given.
- Pricing locked to your last contract. Enterprise contracts don’t get cheaper because the product stopped improving.
- Support queued behind a bigger book of business. Zuora’s strategic focus has been manufacturing and media. Where publisher tickets land in that queue is Zuora’s call, not yours.
- Subscriber data on third-party servers. Zephr is a SaaS paywall. When you eventually move (and you will), getting that data out is a project.
That’s what staying costs.
The MonetizationOS distraction
The MonetizationOS launch is interesting. It’s also not your alternative.
The Zephr founders launched MOS in February 2026 with backing from Google and Cloudflare. The product is pitched at edge-native infrastructure for monetizing bot and AI agent traffic.
That’s a real problem. It’s not the same problem as converting human readers into paid subscribers.
If you’re running a publisher subscription business, the question in front of you is: how do you turn casual visitors into paying readers? That’s a paywall and reader-journey question, not an edge infrastructure question.
Don’t get pulled into the bot-monetization framing. It’s interesting work. It’s not your subscription strategy.
While Zephr stood still, the playbook changed
Here’s the stat that should change how you think about this:
70% of publishers grew subscription revenue in the past year even as traffic declined.
That’s from Piano’s April 2026 benchmark data. Same report: engaged readers generated 110 times more revenue than casual ones.
Why? Because the publishers who grew stopped optimizing the paywall and started optimizing the reader journey.
The shift looks like this:
- Free registration captures readers who weren’t ready to pay yet. Their email is worth more than their first paywall view, because email lets you keep the conversation going.
- Email becomes the conversion channel. Not the paywall popup. Casual visitors convert at about 1%. Engaged email subscribers convert at 10 times that or more.
- Targeted offers replace generic discount blasts. The reader who’s been on your site three times this week gets a different pitch than the one who came in cold from Google.
- Retention gets treated as a separate discipline. Acquisition is one team’s job. Keeping the subscribers you already have is another. Both run on the same data stack.
That’s the Publisher Flywheel. It’s what the Bloomberg-sized publishers run inside Zephr by stitching together identity, decisioning, and entitlements. It’s also what a WordPress publisher can run inside Leaky Paywall without the enterprise contract.
Small Boats Magazine added a free registration wall with List Builder and grew their email list 20% per month. That list converts at 10 times cold traffic. Mexico News Daily streamlined the entire reader journey on WordPress and grew paid subscriptions alongside it.
Alternatives to Zephr worth evaluating
Four options that come up consistently in switching conversations:
Leaky Paywall is the WordPress-native option. Free to start, with List Builder, AI scraper protection, and Stripe Connect billing in the free tier. Powers 800+ publishers including Mexico News Daily and Small Boats Magazine. Best fit if you’re running WordPress and want subscriber data inside your own CMS.
Piano is the closest direct enterprise alternative. The company named Nick Worth CEO in April 2026 and continues to ship product updates. Best fit for very large publishers with dedicated subscription engineering teams and the budget that comes with that.
Pelcro is the mid-market headless SaaS option. The team has been actively shipping recently, including OAuth2 and Braintree integrations. Best fit for publishers running custom front-ends who want a paywall API rather than a CMS plugin.
Memberful is the simpler option, now owned by Patreon. Less news-publisher-specific than the others. Best fit if you’re a smaller publication that doesn’t need the full enterprise feature set.
The case for going WordPress-native
This is a structural argument.
Your subscriber data lives in your CMS. Same database as your articles, your authors, and your content categories.
Your payment gateway is your choice. Stripe, PayPal, Authorize.net, Xendit, or 100s of others via WooCommerce.
Your editorial team and your subscription team share one admin. Marketing schedules a campaign in the same WordPress backend where the editors publish the article. That cuts an entire layer of coordination.
Vendor existential risk drops to near zero. WordPress isn’t getting acquired out from under you. A plugin company isn’t getting absorbed into a billing platform that doesn’t care about media.
Leaky Paywall is free to start. The free tier includes List Builder, metered content control, AI scraper protection, and Stripe Connect billing. Upgrade to Pro for hands-on support, 50+ extensions, and migration included. Enterprise tier adds iOS and Android apps, Flowletter, and dedicated account management. See the full pricing.
Compare that to a Zephr contract priced for News Corp. If you’re a publisher who fits in the “below News Corp” category, the math is different.
AI agents, scrapers, and the new traffic reality
The new traffic mix is real, and you do need defenses against it.
You don’t need a separate edge infrastructure product to get them.
Leaky Paywall includes AI scraper blocking and incognito blocking in the same product that runs your subscriptions. Your registration wall doubles as a bot wall. Readers who won’t authenticate don’t get past the front door. Bots that won’t authenticate don’t either.
That’s one stack handling both problems instead of two.
What switching from Zephr to Leaky Paywall actually looks like
Switching to Leaky Paywall takes a day to a week for most publishers.
That’s the ballpark. Not the months-long enterprise replatform you might be bracing for. Leaky Paywall is a WordPress plugin. Installing it on your site, configuring your paywall rules, and connecting your payment gateway is a fast project.
Here’s what Leaky Paywall handles on your side:
- Subscriber import into WordPress. Your subscribers become WordPress users inside your own database. You keep the data. No vendor sits between you and your reader records.
- Payment gateways you already use. Leaky Paywall integrates directly with Stripe (as a Verified Partner), PayPal, Authorize.net, and Xendit. Need a different gateway? The WooCommerce add-on unlocks 100s more. Your existing billing relationships come with you.
- Flexible content gating. Metered, soft, hard, registration wall, hybrid setups by category, tag, or post type. Configured inside the WordPress admin, not behind a rule engine you need a developer to interpret.
- Print circulation integrations. Leaky Paywall connects to simplecirc, Omeda, Darwin CX, MagHub, SFS, and others. If you’re running print plus digital, the handoff is built in.
We’ve helped countless publishers launch on WordPress. You control the pace and we’ll help you get there.
Bottom line for Zephr publishers
The cost of staying on Zephr compounds quarter over quarter. The cost of moving is one project.
If your contract is up for renewal this year, this is the question to put in front of your team: are we paying for innovation, or are we paying for inertia?Want to talk through what switching would look like for your site? Get in touch with us.
