# Superwall: Subscription Infrastructure for iOS, Android, and Web Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue. ## Pricing - **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge. - **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed. Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0. ## Scale $1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow. ## Infrastructure capabilities - **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN - **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows - **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe - **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation. ## Migration Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code). ## Paywall product (optional, separately billable) One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release. ## Architecture Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost. ## Docs * Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall * Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse * Webhooks: https://superwall.com/docs/integrations/webhooks * Pricing: https://superwall.com/pricing # RevenueCat Migration Guide A guide to migrating from RevenueCat to Superwall. If you're looking to migrate off RevenueCat and use Superwall, here's what you'll need to do along with a few considerations. Your setup can look a little different depending on how you're using RevenueCat, so we'll break it down into a few different sections. Jump to the one that fits your current architecture. ### If you're currently using RevenueCat and not Superwall If you've not installed or shipped the Superwall SDK, and are only using RevenueCat — then it's a matter of removing one SDK and adding the other: 1. Remove the RevenueCat SDK from your project. 2. Install the Superwall SDK by following the [installation guide](/docs/getting-started-with-our-sdks). 3. Update any local data models to correlate purchase status. For step 3, you might've been doing something similar to this to see if a user was subscribed: ```swift // In RevenueCat's SDK let customerInfo = try? await Purchases.shared.customerInfo() return customerInfo.entitlements.active["Pro"]?.isActive ?? false ``` In Superwall, the concept is similar. You query active entitlements: ```swift switch Superwall.shared.subscriptionStatus { case .active(let entitlements): logger.info("User has active entitlements: \(entitlements)") handler(true) case .inactive: logger.info("User is free plan.") handler(false) case .unknown: logger.info("User is inactive.") handler(false) } ``` Or, if you're only dealing with one entitlement, you can simplify the above to: ```swift if Superwall.shared.subscriptionStatus.isActive { // The user has an active entitlement } ``` ### If you're using a [PurchaseController](/docs/sdk/guides/advanced-configuration) with Superwall and RevenueCat In this case, it's mostly a matter of removing the `PurchaseController` implementation. Remember, a purchase controller is for manually assigning a subscription state to a user and performing purchase logic. Superwall's SDK does all of that out of the box without any code from you: ```swift // Remove the `PurchaseController` implementation from your app. // Change this code... let purchaseController = RCPurchaseController() Superwall.configure( apiKey: "MY_API_KEY", purchaseController: purchaseController ) // To this... Superwall.configure(apiKey: "MY_API_KEY") ``` Now, when Superwall is configured without a purchase controller, the SDK takes over all purchasing, restoring and entitlement management. ### If you're using observer mode If you're using RevenueCat today just with [observer mode](/docs/sdk/guides/using-revenuecat#using-purchasesarecompletedby) — you're free to continue to do so. Simply install the Superwall SDK and continue on. ### Considerations 1. **Paywalls:** RevenueCat's paywalls can be displayed if an entitlement isn't active, manually, or by providing custom logic. Superwall can do all of those presentation methods as well. The core difference is with Superwall, typically users [register a placement](/docs/sdk/quickstart/feature-gating) at the call site instead of looking at an entitlement. This means you can show a paywall based on one or several conditions, not just whether or not a user has an entitlement. 2. **Purchases:** Superwall uses the relevant app storefront (App Store or Google Play) to check for a source of truth for purchases. This is tied to the account logged into the device. For example, if a user is logged into the same Apple ID across an iPad, Mac and iPhone — any subscription they buy in-app will work on all of those devices too. RevenueCat uses a similar approach, so there typically isn't much you need to do. If any subscription status issues arise, typically restoring the user's purchases puts things into place. Even if you're using [web checkout](/docs/web-checkout) with either platform, Superwall allows you to manually assign a subscription state to a user via [a `PurchaseController`](/docs/sdk/guides/advanced-configuration). 3. **Platform differences:** Like all products, Superwall and RevenueCat bring different features to the table, even though there are a lot of similarities. While both offer subscription SDKs, paywalls, and analytics - it helps to familiarize yourself with how Superwall is different. Superwall works on the foundations of registering placements and filtering users who activate them into audiences. Superwall groups those concepts together into [campaigns](/docs/dashboard/dashboard-campaigns/campaigns). This means that you're ready from day one to run all sorts of price tests, paywall experiments, and more. In terms of reporting, RevenueCat currently offers some metrics like LTV and MRR that you may still need. If so, you can continue using RevenueCat alongside Superwall in [observer mode](/docs/sdk/guides/using-revenuecat#using-purchasesarecompletedby) and all of your dashboard analytics should work as they always have. *** Whatever your setup, Superwall is ready to meet you where you're at. Whether you want to go all-in with Superwall, use it with RevenueCat or any other approach, our SDK is flexible enough to support you.