Playbook
Superwall vs RevenueCat: The Core Platform Free Up to $10k MAR
Superwall gives away the paywall editor, IAP SDK, campaigns, A/B testing, and analytics free up to $10k in monthly attributed revenue, then just 1% — and switching from RevenueCat is easier than you think.
The core is free. Get the paywall editor, IAP SDK, campaigns, A/B testing, and analytics free up to $10k in monthly attributed revenue, then just 1% after. Build paywalls, run A/B tests, and read the results before you pay anything — and if you're on RevenueCat today, moving over is lighter than you'd guess.
Why it matters
Most teams ship a paywall and then wait weeks to change it. New copy, a new price, a new offer — each one ends up behind an app release and an engineering queue. The tools meant to help you monetize often charge you before they've earned you much, too.
Superwall is built the other way around. Growth teams get a visual paywall editor and built-in experimentation, and the core platform is free up to $10k in monthly attributed revenue, then 1% after. You can test anything, fast — no app release, no engineering queue — without paying for the privilege of running the experiments.
What you can do with Superwall
Build paywalls visually, no code. The paywall editor brings virtually any design to life with advanced UX patterns, or you can start from a template and customize it. You can even build and refine with the AI Chat Builder or connect an agent via the editor MCP.
A/B test without an app release. Run a paywall experiment by adding two or more paywalls to an audience and setting presentation percentages. Change copy, design, pricing, and offers and ship them remotely.
Target the right users. Campaigns group placements, audiences, and paywalls so you decide which users see which paywall, and even hold some users out to measure lift.
Keep your data in one place. Charts cover conversions, trials, ARR/MRR, LTV, retention, and more — analytics, tracking, and integrations are free by default.
How it works
Instead of checking whether an entitlement is active, you register a placement at the call site. When that placement is registered, Superwall evaluates your campaign audiences and decides which paywall — if any — to show. That's what lets you present a paywall based on one or several conditions, not just subscription state.
To run an experiment, you add multiple paywalls to an audience and set presentation percentages. Assignments are sticky per user, and you can create a holdout by keeping the total below 100% to measure the effect of showing a paywall at all.
For purchases, Superwall uses the relevant app storefront (App Store or Google Play) as the source of truth, so subscriptions follow the account logged into the device across iPhone, iPad, and Mac. Configured without a purchase controller, the SDK handles purchasing, restoring, and entitlement management out of the box.
Coming from RevenueCat
Per the RevenueCat migration guide, switching is lighter than most teams expect:
- Only on RevenueCat today? Remove the RevenueCat SDK, install the Superwall SDK, and update where you check subscription status. Superwall exposes the same idea — query active entitlements via
Superwall.shared.subscriptionStatus— so your logic maps over cleanly. - Using a purchase controller? In many cases you can remove it. Configured without one, Superwall handles purchasing, restoring, and entitlement management itself.
- Want to keep RevenueCat's LTV and MRR reporting? Run RevenueCat alongside Superwall in observer mode and your existing analytics keep working.
The upgrade isn't just the SDK swap — it's that from day one you're set up to run price tests and paywall experiments.
Proof from customers
Across customer and prospect conversations, paywall A/B testing and experimentation is the single most-requested job, raised in roughly three out of four calls. Teams consistently describe the same pain: paywalls hard-coded into the app, slow release cycles, and changes stuck in an engineering queue. The repeated ask is to test anything quickly, see all variants at a glance, and keep iterating after the core paywall hits a ceiling — exactly what a free, no-release editor plus built-in experiments is built to do.
Paywall A/B testing and experimentation is the single most-requested job, raised in roughly three out of four calls.
Use cases
Cut your monetization tooling cost. Build paywalls, run experiments, and read analytics for free up to $10k MAR, then 1%.
Ship paywall changes without engineering. Edit and publish remotely instead of waiting on an app release.
Run price and offer tests. Add paywalls to an audience, set percentages, and measure lift with holdouts.
Migrate from RevenueCat at your own pace. Go all-in, or run both in observer mode while you test.
Get started
Create an account and start free at superwall.com.
Install the SDK with our Getting Started guide.
Moving over? Follow the RevenueCat Migration Guide.
Build your first paywall with Getting Started with the Paywall Editor.