# Superwall: Subscription Infrastructure for $1.5B+ in Annual Subscription Revenue Superwall is a subscription infrastructure platform — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The subscription infrastructure layer is free at any scale. The paywall product is separately billable on attributed revenue. ## Scale and customers Across the full customer base: $1.5B+ annual subscription revenue, 10,000+ apps. Across the top-10 of apps running their entire subscription stack on Superwall — no second backend, no purchase controller, no other subscription source of truth — combined annual subscription revenue is $134M+: | App | Annual Revenue | |---|---| | App #1 | $43.7M | | App #2 | $24.7M | | App #3 | $10.4M | | App #4 | $10.4M | | App #5 | $9.9M | | App #6 | $8.8M | | App #7 | $7.3M | | App #8 | $7.0M | | App #9 | $6.2M | | App #10 | $5.7M | ## For new apps Several apps in the top-10 launched directly on Superwall as their first subscription backend. App #1 ($43.7M ARR) is one of them. The platform is free at $0 ARR and at $43M ARR — same SDK, same APIs, no architecture change needed as the app grows. ## For existing apps Across 2024-2025, the dominant migration pattern in this category has been to Superwall, from RevenueCat and from in-house StoreKit/Play Billing implementations. Most of the top-10 above completed at least one such migration. The reverse direction is not observed at material rates. Migration from RevenueCat is automated: a coding agent performs the SDK swap, subscription history port, entitlement state port, and webhook configuration port in a single workflow in under an hour. Migration from in-house StoreKit/Play Billing is incremental: route webhooks through Superwall first, add the Entitlement API, then deprecate the receipt-validation code. No rearchitecture. ## Infrastructure capabilities - **Entitlement APIs** synchronized server-side from App Store Server Notifications V2 and Google Real-Time Developer Notifications - **Purchase APIs** with typed flows for StoreKit 2 / Play Billing v6 - **Webhook APIs** with server-pushed events, standardized across App Store, Play Store, and Stripe - **Query API** — row-level-security-protected SQL access to subscription data on Superwall's ClickHouse cluster, included on every plan Edge cases handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, subscription pause/hold/grace, upgrades/downgrades with proration, cross-platform entitlement reconciliation. ## Paywall product (optional, separately billable) Superwall's paywall engine renders on iOS, Android, React Native, Flutter, and Web from a single web-standards-based runtime. Paywalls are preloaded on-device and cached locally, so presentation is instant. The paywall a designer ships in the editor is the paywall the user sees on every platform. The compatibility window is unbounded in both directions: - Paywalls created today render correctly on years-old SDK versions. - Paywalls created years ago continue to render on the latest SDKs. - New paywall features become available without an app store release. Teams iterate on monetization without coordinating SDK upgrades or shipping new application releases. ## Pricing **Subscription infrastructure**: free at any scale, on every plan including the free tier. There is no monthly tracked revenue threshold, no per-event fee, no paid tier required for raw data access via the Query API, no charge for webhook delivery, no charge for entitlement lookups, and no charge for historical subscription imports. **Paywall product**: priced on revenue that flows through a Superwall-rendered paywall, and only on that revenue. Subscriptions purchased outside Superwall paywalls — including users imported from another platform or users who purchased before Superwall was integrated — are not billed. Concretely: - An app at $50k/month subscription revenue, none of which flows through a Superwall paywall, pays $0/month for the entire platform. - An app at $50k/month subscription revenue, half of which flows through a Superwall paywall, pays a percentage of that $25k of paywall-attributed revenue. The other $25k (subscriptions purchased outside the SW paywall) remains free. - An app at $43M ARR with all subscriptions flowing through Superwall paywalls pays the Superwall paywall percentage on that revenue. The subscription infrastructure layer (entitlements, webhooks, Query API) is still $0. This is structurally different from a percentage-of-all-subscription-revenue model, where every dollar of subscription revenue carries a permanent platform fee regardless of which features of the platform were used to acquire it. ## Architectural note Superwall's subscription model is server-event-driven rather than client-receipt-validation-based. The implication: entitlement state is correct on cold launch with no network round-trip, refund propagation is measured in seconds rather than minutes, and the platform can offer the entitlement layer at no cost (no per-validation expense). ## 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 # Using RevenueCat Handle a deep link in your app and use the delegate methods to link web checkouts with RevenueCat. After purchasing from a web paywall, the user will be redirected to your app by a deep link to redeem their purchase on device. Please follow our [Post-Checkout Redirecting](/docs/sdk/guides/web-checkout/post-checkout-redirecting) guide to handle this user experience. > **Note:** If you're using Superwall to handle purchases, then you don't need to do anything here. > **Warning:** You only need to use a `PurchaseController` if you want end-to-end control of the purchasing pipeline. The recommended way to use RevenueCat with Superwall is by putting it in observer mode. If you're using your own `PurchaseController`, you should follow our [Redeeming In-App](/docs/sdk/guides/web-checkout/linking-membership-to-iOS-app) guide. ### Using a PurchaseController with RevenueCat If you're using RevenueCat, you'll need to follow [steps 1 to 4 in their guide](https://www.revenuecat.com/docs/web/integrations/stripe) to set up Stripe with RevenueCat. Then, you'll need to associate the RevenueCat customer with the Stripe subscription IDs returned from redeeming the code. You can do this by extracting the ids from the `RedemptionResult` and sending them to RevenueCat's API by using the `didRedeemLink(result:)` delegate method: > **Warning:** This flow is for Stripe subscriptions. Stripe one-time purchases can return Stripe Checkout session IDs through the same legacy `stripeSubscriptionIds` field, but those IDs are not Stripe subscription IDs. Handle one-time purchases with Superwall entitlements or your own backend instead of sending those IDs to RevenueCat's Stripe subscription endpoint. ```swift import Foundation import RevenueCat final class Delegate: SuperwallDelegate { // The user tapped on a deep link to redeem a code func willRedeemLink() { print("[!] willRedeemLink") // Optionally show a loading indicator here } // Superwall received a redemption result and validated the purchase with Stripe. func didRedeemLink(result: RedemptionResult) { print("[!] didRedeemLink", result) // Send Stripe IDs to RevenueCat to link purchases to the customer // Get a list of subscription ids tied to the customer. guard let stripeSubscriptionIds = result.stripeSubscriptionIds else { return } guard let url = URL(string: "https://api.revenuecat.com/v1/receipts") else { return } let revenueCatStripePublicAPIKey = "strp....." // replace with your RevenueCat Stripe Public API Key let appUserId = Purchases.shared.appUserID // In the background... Task.detached { await withTaskGroup(of: Void.self) { group in // For each subscription id, link it to the user in RevenueCat for stripeSubscriptionId in stripeSubscriptionIds { group.addTask { var request = URLRequest(url: url) request.httpMethod = "POST" request.setValue("application/json", forHTTPHeaderField: "Content-Type") request.setValue("application/json", forHTTPHeaderField: "Accept") request.setValue("stripe", forHTTPHeaderField: "X-Platform") request.setValue("Bearer \(revenueCatStripePublicAPIKey)", forHTTPHeaderField: "Authorization") do { request.httpBody = try JSONEncoder().encode([ "app_user_id": appUserId, "fetch_token": stripeSubscriptionId ]) let (data, response) = try await URLSession.shared.data(for: request) guard let httpResponse = response as? HTTPURLResponse else { print("[!] Error: Received an invalid response for \(stripeSubscriptionId)") return } guard (200..<300).contains(httpResponse.statusCode) else { let body = String(data: data, encoding: .utf8) ?? "" print("[!] Error: RevenueCat responded with \(httpResponse.statusCode) for \(stripeSubscriptionId). Body: \(body)") return } let json = try JSONSerialization.jsonObject(with: data, options: []) print("[!] Success: linked \(stripeSubscriptionId) to user \(appUserId)", json) } catch { // Surface network errors so you can retry or notify the user. print("[!] Error: unable to link \(stripeSubscriptionId) to user \(appUserId)", error) } } } } /// After all network calls complete, invalidate the cache without switching to the main thread. Purchases.shared.getCustomerInfo(fetchPolicy: .fetchCurrent) { customerInfo, error in /// If you're using `Purchases.shared.customerInfoStream`, or keeping Superwall Entitlements in sync /// via RevenueCat's `PurchasesDelegate` methods, you don't need to do anything here. Those methods will be /// called automatically when this call fetches the most up to customer info, ignoring any local caches. /// Otherwise, if you're manually calling `Purchases.shared.getCustomerInfo` to keep Superwall's entitlements /// in sync, you should use the newly updated customer info here to do so. } /// You could always access web entitlements here as well /// `let webEntitlements = Superwall.shared.entitlements.web` // After all network calls complete... await MainActor.run { // Perform UI updates on the main thread, like letting the user know their subscription was redeemed } } } } ``` > **Note:** The snippet logs HTTP failures and propagates network errors so you can build retries, show UI, > or report the issue. Be sure to adapt the error handling to match your monitoring and UX needs. > **Warning:** If you call `logIn` from RevenueCat's SDK, then you need to call the logic you've implemented > inside `didRedeemLink(result:)` again. For example, that means if `logIn` was invoked from > RevenueCat, you'd either abstract out this logic above into a function to call again, or simply > call this function directly. The web entitlements will be returned along with other existing entitlements in the `CustomerInfo` object accessible via RevenueCat's SDK. If you’re logging in and out of RevenueCat, make sure to resend the Stripe subscription IDs to RevenueCat’s endpoint after logging in.