# 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 # Tracking Subscription State Monitor user subscription status in your iOS app Superwall tracks the subscription state of a user for you. So, you don't need to add in extra logic for this. However, there are times in your app where you simply want to know if a user is on a paid plan or not. In your app's models, you might wish to set a flag representing whether or not a user is on a paid subscription: ```swift @Observable class UserData { var isPaidUser: Bool = false } ``` ### Using subscription status You can do this by observing the `subscriptionStatus` property on `Superwall.shared`. This property is an enum that represents the user's subscription status: ```swift switch Superwall.shared.subscriptionStatus { case .active(let entitlements): logger.info("User has active entitlements: \(entitlements)") userData.isPaidUser = true case .inactive: logger.info("User is free plan.") userData.isPaidUser = false case .unknown: logger.info("User is inactive.") userData.isPaidUser = false } ``` One natural way to tie the logic of your model together with Superwall's subscription status is by having your own model conform to the [Superwall Delegate](/docs/sdk/guides/using-superwall-delegate): ```swift @Observable class UserData { var isPaidUser: Bool = false } extension UserData: SuperwallDelegate { // MARK: Superwall Delegate func subscriptionStatusDidChange(from oldValue: SubscriptionStatus, to newValue: SubscriptionStatus) { switch newValue { case .active(_): // If you're using more than one entitlement, you can check which one is active here. // This example just assumes one is being used. logger.info("User is pro plan.") self.isPaidUser = true case .inactive: logger.info("User is free plan.") self.isPaidUser = false case .unknown: logger.info("User is free plan.") self.isPaidUser = false } } } ``` Another shorthand way to check? The `isActive` flag, which returns true if any entitlement is active: ```swift if Superwall.shared.subscriptionStatus.isActive { userData.isPaidUser = true } ``` :::ios ### Listening for entitlement changes in SwiftUI For Swift based apps, you can also create a flexible custom modifier which would fire if any changes to a subscription state occur. Here's how: ```swift import Foundation import SuperwallKit import SwiftUI // MARK: - Notification Handling extension NSNotification.Name { static let entitlementDidChange = NSNotification.Name("entitlementDidChange") } extension NotificationCenter { func entitlementChangedPublisher() -> NotificationCenter.Publisher { return self.publisher(for: .entitlementDidChange) } } // MARK: View Modifier private struct EntitlementChangedModifier: ViewModifier { // Or, change the `Bool` to `Set` if you want to know which entitlements are active. // This example assumes you're only using one. let handler: (Bool) -> () func body(content: Content) -> some View { content .onReceive(NotificationCenter.default.entitlementChangedPublisher(), perform: { _ in switch Superwall.shared.subscriptionStatus { case .active(_): handler(true) case .inactive: handler(false) case .unknown: handler(false) } }) } } // MARK: View Extensions extension View { func onEntitlementChanged(_ handler: @escaping (Bool) -> ()) -> some View { self.modifier(EntitlementChangedModifier(handler: handler)) } } // Then, in any view, this modifier will fire when the subscription status changes struct SomeView: View { @State private var isPro: Bool = false var body: some View { VStack { Text("User is pro: \(isPro ? "Yes" : "No")") } .onEntitlementChanged { isPro in self.isPro = isPro } } } ``` ::: ### Superwall checks subscription status for you Remember that the Superwall SDK uses its [audience filters](/docs/dashboard/dashboard-campaigns/campaigns-audience#matching-to-entitlements) for a similar purpose. You generally don't need to wrap your calls registering placements around `if` statements checking if a user is on a paid plan, like this: ```swift // Unnecessary if !Superwall.shared.subscriptionStatus.isActive { Superwall.shared.register(placement: "campaign_trigger") } ``` In your audience filters, you can specify whether or not the subscription state should be considered... ![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/entitlementCheck.png) ...which eliminates the needs for code like the above. This keeps you code base cleaner, and the responsibility of "Should this paywall show" within the Superwall campaign platform as it was designed.