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. It manages subscription status and entitlements out of the box — the same job you pay RevenueCat for — and it's built around the paywall, offer, and price testing that actually grows revenue. Under the OpenRevenue initiative, that entire core — subscription status, webhooks, integrations, and the data plumbing — is 100% free at any scale, the client SDKs are open source, and the migration path is documented.

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 into one platform, and it's priced the other way around from the tools that charge you before they've earned you much. Under the OpenRevenue initiative, everything RevenueCat's core product does is 100% free at any scale: subscription status and entitlement management, standardized webhooks, integrations, and all the JSON transforms and plumbing that move your revenue data around. The growth platform on top — the paywall editor, campaigns, A/B testing, and analytics — is free up to $10k in monthly attributed revenue, then just 1% after, so you can build paywalls, run experiments, and read the results before you pay anything. And "the open RevenueCat alternative" isn't a slogan — the client SDKs are open source on GitHub and the migration path is documented.

What you can do with Superwall

• Own entitlements without a custom purchase controller. Configured without one, the SDK handles purchasing, restoring, and entitlement management out of the box — no extra purchase code to maintain.

• Check one subscription status. Replace RevenueCat customer-info checks with subscriptionStatus — 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.

• Run paywall experiments from day one. Campaigns group placements, audiences, and paywalls, so you can A/B test copy, design, offers, trials, and price points — and even configure holdouts — without shipping a build.

• See the data in one place. Charts cover proceeds, sales, trial conversion, paywall conversion, MRR/ARR, retention, and LTV, so you can judge what's actually working.

• Ship across platforms. Open-source client SDKs cover iOS, Android, Flutter, Expo, Unity, and React Native — and the no-code paywall editor comes with an AI Chat Builder and an editor MCP for your coding agents.

How the migration works

Per the RevenueCat migration guide, switching is lighter than most teams expect — three concrete steps:

Swap the SDK. Remove the RevenueCat SDK and install the Superwall SDK; configuring it is typically just Superwall.configure(apiKey:).

Drop the purchase controller. Superwall's SDK "does all of that out of the box without any code from you," so your custom PurchaseController can usually go. (You can keep one for manual state assignment if you need it.)

Check subscriptionStatus. Replace RevenueCat customer-info checks with Superwall.shared.subscriptionStatus — the same concept your logic already maps to.

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. And the cutover is low-risk: 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.

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, so your existing LTV and MRR reporting keeps working.

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 — customers compare the builder to "Figma for growth designers."

Migration from RevenueCat, Adapty, and other tools is a real and growing demand signal, and it's almost always tied to wanting better testing, more design control, and data parity. The migration story works because the entitlement layer removes the last reason to keep a second subscription tool around.

Use cases

• Consolidate your stack: replace a paywall tool plus RevenueCat with one platform for building, experimentation, and entitlements — moving at your own pace with observer mode.

• Cut your monetization tooling cost: the OpenRevenue core — entitlements, webhooks, integrations — is free at any scale; paywalls, experiments, and analytics are free up to $10k MAR, then 1%.

• Price and offer testing to raise conversion and ARPU — trials, intro offers, annual vs monthly framing, and discounted paths, measured with holdouts.

• Gate features remotely: register placements for events today and decide what to monetize later — without an app update.

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

Get started

Superwall is free to start. Install an open-source client SDK with the getting started guide, or, if you're coming from RevenueCat, follow the RevenueCat migration guide and review the tracking subscription state docs. Just want the free subscription layer? See using Superwall without paywalls. Create an account at superwall.com.