The free, open RevenueCat alternative.

Most teams start with a subscription SDK and quickly hit a wall: every change to a paywall means an engineering ticket and another app release. Superwall flips that around. Paywalls, offers, and pricing are configured remotely with open SDKs and a documented migration path, so growth teams can keep iterating on monetization without waiting on the engineering queue.

Why it matters

The single loudest thing customers ask for is the ability to test anything, fast — without waiting on the engineering queue. Superwall is designed around that job. It remotely configures and A/B tests mobile app paywalls with no app update required, and it's free to start with open-source SDKs you can read on GitHub. So "the open RevenueCat alternative" isn't a slogan — the SDKs are public and the migration path is documented.

What you can do with Superwall

• Run paywall experiments from day one. Superwall groups placements, audiences, and paywalls into campaigns, so you can A/B test paywall copy, design, and offers — and even configure holdouts — without shipping a build.

• Test pricing and offers. Because paywalls are remote, you can test trials, intro offers, annual vs monthly framing, and discounted paths against each other instead of hard-coding them.

• Let purchasing run out of the box. When you configure Superwall without a purchase controller, the SDK takes over purchasing, restoring, and entitlement management for you — no extra purchase code to maintain.

• See the data in one place. Superwall's charts cover proceeds, sales, trial conversion, paywall conversion, and realized LTP per user, so you can judge what's actually working.

• Ship across platforms. Open-source SDKs cover iOS, Android, Flutter, Expo, Unity, and React Native.

How it works

• Install an open SDK and configure with your API key. Follow the installation guide; configuring Superwall is typically just Superwall.configure(apiKey:).

• Register placements at the call site. Instead of checking an entitlement everywhere, you register a placement (like addedEntry) where a paywall might appear. Superwall evaluates your campaign filters and decides which paywall — if any — to show.

• Build and test paywalls remotely. Design in the paywall editor, then start experiments and adjust traffic splits without an app release.

• Read subscription state simply. Query Superwall.shared.subscriptionStatus for active entitlements — the same concept you used with RevenueCat's customerInfo.

Proof from customers

Across customer and prospect calls, the strongest, most repeated signal is the ability to run paywall A/B tests and price tests quickly — without shipping a build. Teams describe wanting faster iteration, all variants visible at a glance, and growth/marketing being able to move without waiting on engineering. Superwall's campaign model is built to deliver exactly that, and switching is low-risk: in many setups migrating from RevenueCat is "remove one SDK, add the other," and you can even keep RevenueCat in observer mode while you transition.

In many setups, migrating from RevenueCat is "remove one SDK, add the other" — and you can even keep RevenueCat in observer mode while you transition.

Use cases

• Moving off RevenueCat without rewriting your purchasing pipeline.

• Paywall A/B testing to find your best-converting screen.

• Price and offer testing to raise conversion and ARPU.

• Onboarding and full-funnel flows built and tested in the same editor.

• Subscription analytics in one dashboard, from proceeds to LTV.

Get started

Superwall is free to start. Install an open-source SDK with the getting started guide, or, if you're coming from RevenueCat, follow the RevenueCat migration guide. Create an account at superwall.com.