Compare
Zephr’s default is a reverse proxy you point your live domain at. EdgeKit is a Worker in front of your site, with your reader record in a database you can name. They differ on where that record lives, whether your data team gets the raw rows, and whether a price exists before a sales call.
9 questions · checked 4 September 2026
Side by side
Rows are ranked by how much each one moves a decision. EdgeKit wins four, Zephr wins one, four are even.
| The question | Zephr | EdgeKit |
|---|---|---|
| Can we run our own SQL against our reader data?Favours EdgeKit | A signed export endpoint for readers and events, plus optional near-real-time event streaming into your own BigQuery project. | Your reader record is a database of your own. Ask for managed deployment and that database is a project in your own cloud account. |
| Do we get the raw behavioural rows, or a dashboard?Favours EdgeKit | Zephr system events streamed to BigQuery tables you nominate. Zuora states the full range of its events is not yet supported. | Every event, unsampled, written as Parquet to object storage in the atomic layout, with your own schemas beside it. Forwarded to any destination you need, such as Snowflake or BigQuery. |
| Can we get a price before we talk to anyone?Favours EdgeKit | Packaging is published and rates are not. Zuora’s Zephr pages carry no figure; the actions are tour the product and speak to an expert. | The whole rate card is on the site: eight meters, an included amount and a rate on each, and a $99 monthly floor. |
| Where does the software run, and who holds our certificate?Favours EdgeKit | Their default is a reverse proxy: you point your live domain at Zephr and Zephr requests the certificate for it. A non-proxy pattern is documented. | Two deployments, one product. Your own cloud account with EdgeKit operating it, or EdgeKit’s edge with your database in a region you name. |
| Do our subscribers keep access on cutover day?Neither | Yes. A claim in a token you sign auto-assigns a product, and their Admin API writes an access record directly. | Yes, from the same token. EdgeKit verifies a token you sign and reads its claims on every decision, so nobody signs in again. |
| Can readers keep the login they already have?Neither | Three ways: their own identity module, a token you sign, or packaged Auth0 and Cognito extensions. In token mode their own registration and payment forms stop applying. | Two ways: a token you sign, algorithm pinned, or a check against your identity service on every request. Redirect sign-in is specified, not built. |
| How do we undo a rule change that cost money?Neither | Draft, staged and live versions of every rule. Restore an earlier one by staging it and publishing it, with version tags and a preview debugger. | Put the rule back and deploy again, which takes minutes. Every deploy is a numbered, append-only entry naming who shipped it, so the record of what was live and when cannot be edited afterwards. |
| Can we keep the billing vendor we already run?Favours Zephr | Braintree, Chargify, Stripe and Zuora Billing have built-in payment forms, and their Admin API writes access from any other biller. | Recurly and Stripe, each with a full mirror of your billing state kept current by webhook. Any other biller is wired at no charge if you need it. |
| Can we sell corporate and campus subscriptions?Neither | Company accounts with seat counts, soft over-limits and allowlisted IP ranges that admit a reader with no sign-in at all. A separately priced module. | Corporate accounts, invitations and automatic joining from an email domain you list. Seats, over-limits and who is admitted are rules your revenue team writes, and there is no separately priced module. |
What decides it
EdgeKit provisions one database per media group at signup, and if you ask for managed deployment it is a project in your own cloud account with EdgeKit operating it on your infrastructure. Neither is an upgrade tier. Where the reader record lives is your decision.
Every event EdgeKit collects lands unsampled in object storage as Parquet, in the atomic layout, with your own authored schemas nested beside the typed core, and none of it is capped per day or sold as an add-on. The comparison is against an event feed whose vendor states its own coverage is incomplete.
Eight meters, an included amount and a rate on each, a $99 monthly floor, a calculator that asks for no email, and the point at which the published list stops and a quote begins. Zuora publishes none of that for Zephr, and no product release closes that gap.
Switching
Switching cost is the objection we expect, so here is what a switch involves. EdgeKit runs the migration itself rather than handing you a toolkit.
Questions
Zuora lists Zephr as one of five top-level products and markets it actively, with documentation updated during 2026 and Zephr components tracked as first-class services on Zuora’s own status page. Two things are also true and public: Zuora’s press releases through 2026 do not mention Zephr, and the team behind Zephr launched a separate paywall company, MonetizationOS, in February 2026, and the launch announcement says so. Absence of a public roadmap statement is not a statement of de-investment, and we will not characterise it as one. Ask Zuora directly for the Zephr roadmap and the release cadence, in writing. It is a fair question to ask us too.
Not with EdgeKit. Both EdgeKit deployments leave your domain and certificate where they are. Zephr’s primary integration method is a network in front of your site: you point your live domain at Zephr and Zephr requests the certificate for it. Zuora also documents an alternative for anyone with an incumbent network, where you call the decision engine from your own edge and forward two paths, and your DNS never moves.
We can only answer half of it. EdgeKit publishes every rate: eight meters, an included amount and a per-unit rate on each, and a $99 monthly floor, with a calculator you drive with your own volumes. Zuora publishes what a Zephr agreement contains and no figure for any line of it. The figures circulating for a Zephr contract come from third-party comparison sites with no primary source, and we do not repeat them. Note the two are not measured the same way: Zuora meters registered readers and data volume in terabytes, EdgeKit meters monthly active readers, paid readers, anonymous visitors, newsletter subscribers and four machine units. Zuora also prices its corporate module separately from the base agreement; EdgeKit does not.
The data is yours and there is no export fee, here or in the contract. Today there is no export button and no export endpoint, so an export is us running a query for you. Where EdgeKit is deployed into your own cloud account, the database and the event archive already sit in infrastructure you control and you do not need us to reach them. Zephr publishes a signed export endpoint your own team can schedule, which is an advantage over us on this point.
Open the paywall for an existing subscriber base without an onboarding project. A subscription arriving into EdgeKit from a billing sync writes no access record of its own; EdgeKit’s own checkout is what creates one. Zephr reads a claim in the token you already sign, or takes the record over its API. Second place is getting your own data out without asking us: Zephr publishes a signed export endpoint your team can schedule, and EdgeKit ships none.
How we checked
If a claim here is wrong or out of date, write toinfo@edgekit.cloud and we will correct the page and say what changed. That includes anybody at Zephr, a Zuora product.
Zephr and Zuora are trademarks of Zuora, Inc. EdgeKit is not affiliated with, endorsed by or sponsored by Zuora. Product names are used here only to identify the products being compared.
Next step
A walkthrough against your actual setup, run by somebody who has run a subscription media business, including the parts of this page where Zephr wins.
Book a demo