Playbook
From Paywall Editor to RevenueCat Killer
Superwall now manages subscription status and entitlements out of the box — the same job you pay RevenueCat for, built around the testing that actually grows revenue.
The tool you already use to test paywalls can also own your subscription stack — which means it can replace RevenueCat.
Why it matters
Most teams run two tools: one to track entitlements and one to test paywalls. But knowing who is a paying user doesn't grow revenue — testing your paywalls, offers, and pricing does. Splitting those jobs across separate SDKs and dashboards adds code, fragments your data, and puts an engineering queue between your growth team and every change.
Superwall collapses that. It manages subscription status and entitlements out of the box — the same job you pay RevenueCat for — and it's built around the experimentation that actually moves ARPU and LTV. Migration from RevenueCat is a rising request from teams who want better testing and a better builder without losing confidence in their subscription foundation.
What you can do with Superwall
Own entitlements without a custom purchase controller. Superwall's SDK handles purchases out of the box. The RevenueCat migration guide walks you through removing the RevenueCat SDK and dropping your custom PurchaseController entirely.
Check one subscription status. Replace RevenueCat customer-info checks with Superwall's subscriptionStatus property — active, inactive, or unknown — or the isActive flag for single-entitlement apps.
Gate features from the dashboard. Instead of wrapping every feature in an entitlement if-statement, register a placement at the call site and remotely configure which features you gate — with no app update.
Build paywalls with no code. Bring virtually any design to life in the paywall editor, complete with advanced UX patterns, or start from a template.
Test anything, fast. A/B test paywall copy, design, offers, trials, and price points without shipping a build, and run win-back and offer flows to recover revenue leaking out of your funnel.
How it works
The migration is three concrete steps, per the migration guide:
- Swap the SDK. Remove the RevenueCat SDK and install the Superwall SDK.
- Drop the purchase controller. Per the docs, Superwall's SDK "does all of that out of the box without any code from you," so your custom PurchaseController can go. (You can still keep one for manual state assignment if you need it.)
- Check subscriptionStatus. Replace RevenueCat customer-info checks with Superwall's subscriptionStatus.
Access control then moves to feature gating: the SDK pulls campaign settings on launch, evaluates audiences on device, and runs your feature: closure based on each paywall's Gated / Non-Gated setting.
On safety: Superwall uses the App Store or Google Play as the source of truth for purchases, so existing subscribers keep their access and a restore typically resolves status. Want to de-risk the cutover? Keep RevenueCat in observer mode alongside Superwall during the transition.
Proof from customers
Migration from RevenueCat, Adapty, or other tools is a real and growing demand signal in customer conversations — and it's almost always tied to wanting better testing, more design control, and data parity. The consistent draw is the same: change paywalls, offers, pricing, and entitlement gating without waiting on an engineering queue or shipping a new build. The migration story works because the entitlement layer removes the last reason to keep a second subscription tool around.
Figma for growth designers.
Use cases
Consolidate your stack. Replace a paywall tool plus RevenueCat with one platform that handles building, experimentation, and entitlements.
Cut purchase-handling code. Remove your custom purchase controller and let Superwall handle purchases out of the box.
Gate features remotely. Register placements for analytics events today and decide what to monetize later — without an app update.
Grow revenue, not just plumbing. Pair entitlement management with paywall, offer, and price testing in the same tool.
Get started
Read the RevenueCat to Superwall migration guide.
Review tracking subscription state and entitlements and feature gating.
Explore the paywall editor.
Sign up at superwall.com.