# 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 # App Store Privacy Labels When submitting your app for review, you'll need to fill out an App Store Privacy label. When using the Superwall SDK, there are a few choices you may need to consider. ### App Store Privacy Labels Privacy disclosures in regards to how data is processed or otherwise used are required when submitting an app for review on the App Store. When using the Superwall SDK, there are a few options you'll need to select to comply with this requirement. **At a minimum, you'll need to select "Purchases":** ![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/app-privacy-purchases.png) When you select "Purchases", you'll need to scroll down finish setup. When you do, there are two options you'll need to select: 1. Analytics 2. App Functionality ![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/app-privacy-purchase-history.png) ### Identifying Users How you proceed with the next prompt depends on how you are identifying users. If you *are* identifying users via their email or any other means, disclose that here. Note that the Superwall SDK does not do this. Finally, Superwall does not track purchase history of users for advertising purposes — so you can choose "No" here (unless you're using other SDKs which do this, or you're performing any purchase history tracking for advertising purposes on your own ): ![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/app-privacy-tagging-users.png) In terms of the Superwall SDK, that's all you need to choose. But again, remember that your privacy label could look different depending on how you process data, how other SDKs are used and more. ### Collected Data Here is a detailed list of anything that might be collected in the Superwall SDK: | Property | Description | | ----------------------------- | --------------------------------------------------------------- | | `publicApiKey` | The API key for accessing the public API. | | `platform` | The operating system of the device (e.g., iOS, Android). | | `appUserId` | A unique identifier for the app user. | | `aliases` | List of aliases associated with the app user. | | `vendorId` | The vendor ID of the device. | | `appVersion` | The version of the app. | | `osVersion` | The operating system version running on the device. | | `deviceModel` | The model of the device (e.g., iPhone or Android device model). | | `deviceLocale` | The current locale set on the device. | | `preferredLocale` | The preferred locale of the user. | | `deviceLanguageCode` | The language code of the device's system language. | | `preferredLanguageCode` | The preferred language code set by the user. | | `regionCode` | The region code set on the device. | | `preferredRegionCode` | The preferred region code of the user. | | `deviceCurrencyCode` | The currency code for transactions on the device. | | `deviceCurrencySymbol` | The currency symbol based on the device’s settings. | | `interfaceType` | The type of user interface (e.g., vision, ipad, etc). | | `timezoneOffset` | The device’s current timezone offset in minutes. | | `radioType` | The network radio type (e.g., WiFi, Cellular). | | `interfaceStyle` | The interface style (e.g., light or dark mode). | | `isLowPowerModeEnabled` | Indicates whether low power mode is enabled. | | `bundleId` | The bundle identifier of the app. | | `appInstallDate` | The date the app was installed. | | `isMac` | A boolean indicating if the device is a Mac. | | `daysSinceInstall` | The number of days since the app was installed. | | `minutesSinceInstall` | The number of minutes since the app was installed. | | `daysSinceLastPaywallView` | The number of days since the last paywall view. | | `minutesSinceLastPaywallView` | The number of minutes since the last paywall view. | | `totalPaywallViews` | The total number of paywall views. | | `utcDate` | The current UTC date. | | `localDate` | The local date of the device. | | `utcTime` | The current UTC time. | | `localTime` | The local time on the device. | | `utcDateTime` | The UTC date and time combined. | | `localDateTime` | The local date and time combined. | | `isSandbox` | Indicates if the app is running in a sandbox environment. | | `subscriptionStatus` | The subscription status of the app user. | | `isFirstAppOpen` | Boolean indicating if it is the user’s first app open. | | `sdkVersion` | The current version of the SDK. | | `sdkVersionPadded` | The padded version of the SDK (e.g. 001.002.003-beta.001). | | `appBuildString` | The app’s build string identifier. | | `appBuildStringNumber` | The numeric value of the app’s build number. | | `interfaceStyleMode` | The current interface style mode (e.g., dark, light). | | `ipRegion` | The region derived from the device's IP address. | | `ipRegionCode` | The region code derived from the device's IP. | | `ipCountry` | The country derived from the device's IP address. | | `ipCity` | The city derived from the device's IP address. | | `ipContinent` | The continent derived from the device's IP address. | | `ipTimezone` | The timezone derived from the device's IP address. | | `capabilities` | A string indicating any Superwall-SDK specific capabilities. | | `capabilitiesConfig` | A JSON configuration of the above capabilities. | | `platformWrapper` | The platform wrapper (e.g., React Native). | | `platformWrapperVersion` | The version of the platform wrapper. |