# 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 # Why does the "SDK releases behind" warning still appear after updating? The Superwall dashboard displays an alert when it detects that your app is running an outdated SDK version. This alert appears in the **SDK Alerts & News** section of the Overview page and typically reads something like "You're X SDK releases behind." ## Why the warning persists after updating The SDK version warning is based on the SDK versions reported by **all active users** of your app, not just the version you are currently developing with. When you release a new app update with the latest Superwall SDK, users who have not yet updated their app will continue reporting the older SDK version to Superwall. Because the warning is calculated from this aggregate data, it will remain visible as long as a meaningful portion of your user base is still running an older version of your app. ## When will it go away? The warning resolves on its own as your users update to the latest version of your app. Once a sufficient percentage of your active users are running the newer SDK version, the alert will disappear from your dashboard automatically. The speed at which this happens depends on your app's update adoption rate, which is influenced by factors such as: * Whether automatic app updates are enabled on users' devices * How quickly your user base tends to adopt new versions * The size of your active user base ## What you should do If you have already updated to the latest Superwall SDK in your app and published the update to the relevant app store, no further action is required. The warning is informational and does not affect SDK functionality or paywall behavior for users on any version. > **Note:** This behavior applies to all Superwall SDKs, including iOS, Android, Flutter, Expo, and React Native. The dashboard aggregates version data across all active users regardless of platform.