# 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 # How to Test Paywalls with Local Currency for a Specific Country Learn how to preview your paywall as a user in a specific country would see it, including local currency and audience matching. When you create a campaign that targets users in a specific country, you may want to preview the paywall as those users would see it, with their local currency instead of your default. This requires two changes on your test device: matching the audience filter and changing the displayed currency. ### Matching country-based audience filters If your campaign uses `device.storeFrontCountryCode` to filter by country, your test device must report that same country to match the audience. On iOS, change your App Store region: 1. Open **Settings** on your device. 2. Tap your **Apple ID** at the top. 3. Go to **Media & Purchases** and tap **View Account**. 4. Tap **Country/Region** and select the country you want to test. > **Warning:** Changing your App Store region may require you to update your payment method to one valid in that country. You can switch back after testing. If your campaign uses `device.deviceLocale` instead (e.g. `en_GB`, `fr_FR`), change the device locale in **Settings > General > Language & Region** to match the target locale. ### Displaying local currency The currency shown on your paywall is determined by the App Store storefront country, not the device locale. To see prices in the currency a user in that country would see, change your App Store region using the steps above. The App Store returns product prices in the currency of the storefront country. For example, if your App Store region is set to France, prices will appear in EUR. If set to Japan, prices will appear in JPY. > **Note:** The actual price amount is determined by what you have configured in App Store Connect for each territory. The storefront country controls which currency and price tier is used. ### Summary of required changes | What you want to test | What to change | Where to change it | | ----------------------------------------------- | ------------------------ | ----------------------------------------------------------------------- | | Match a `storeFrontCountryCode` audience filter | App Store country/region | Settings > Apple ID > Media & Purchases > View Account > Country/Region | | Match a `deviceLocale` audience filter | Device locale | Settings > General > Language & Region | | See prices in local currency | App Store country/region | Settings > Apple ID > Media & Purchases > View Account > Country/Region | > **Tip:** If your campaign uses `storeFrontCountryCode`, changing the App Store region handles both matching the audience filter and displaying the correct local currency in one step.