# 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 # Paywall Settings Sidebar The settings sidebar is split into 3 sections: Products; Design; and Advanced. > **Warning:** The legacy editor is deprecated. Please visit the docs covering our new > [editor](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-overview). ### Products In this section, you choose your products to display on your paywall. You'll need to set up your products via Settings as detailed [here](/docs/dashboard/products). ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/8cf8e67-Screenshot_2023-06-14_at_16.53.22.png) ### Settings These settings determine how the paywall displays and how it behaves. ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/93599d2-Screenshot_2023-06-14_at_17.25.08.png) #### Presentation Style Here, you can set the presentation style to one of the following: * Modal: Presents the paywall modally that can be swiped away. * Full Screen: Presents the paywall over the entire screen. * Push: Presents the paywall as if it's being pushed on to a navigation stack. This requires v2.4+ of the SDK. * No Animation: Presents the paywall without animation. This requires v2.4+ of the SDK. * Drawer: Presents the paywall as a drawer, taking up 70% of the screen. This is an iOS 16 only feature that works with SDK v3+. #### Presentation Targeting The default behavior of the SDK presents a paywall only to users who aren't subscribed. However, you can override this to always present regardless of subscription status by setting *Present Paywall* to *Always*. #### Feature Gating Feature gating allows your team to retroactively decide if the paywall is *Gated* or *Non Gated*. | Type | Behavior | Example | | ----------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------ | | **Non Gated** (default) | Show Paywall → Execute Feature | When "Sign Up" button is pressed, show a paywall, but continue onboarding after it closes. | | **Gated** | Show Paywall → Is user paying?If Yes → Execute FeatureIf No → Do Nothing | When "Start Workout" button is pressed, show a paywall. Only continue if paying. | Remember, the [register feature block](/docs/sdk/quickstart/feature-gating) is always executed if: 1. No campaign is configured for the event 2. The user is already paying #### Cache on device Caching is enabled by default on paywalls. This means that after the first load of a paywall, it will be cached on disk for use next time the app is opened unless you make a change to it on the editor. This greatly reduces network load and the time taken to load paywalls. It does of course increase memory usage of your app so you can turn caching off if you wish by setting *Cache on device* to *Disabled*. ### Fonts You can set the font and font size and font weight used for your paywall, including custom fonts. ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/c514eb7-Screenshot_2023-06-14_at_17.46.28.png) ### Sizing, Spacing, and Colors Set the global design for your paywall. ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/bc61385-Screenshot_2023-06-14_at_17.55.16.png) #### Free Trial Reminder You can add a local notification that fires after a number of days, when a free trial has been purchased. After the user starts a free trial, it will ask them to enable notifications if they haven't already done so. ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/free-trial-reminder.png)
> **Note:** **In sandbox mode, the free trial reminder will fire after x minutes, instead > of x days.** ![local-notifications](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/local-notification.jpg) This is how the title, subtitle, and body appears in a notification: ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/notificationExample.png) If you use local notifications within your app, you'll want to use the following functions to clear your app's pending and delivered notifications without affecting Superwall: * `UNUserNotificationCenter.current().removeAllPendingNonSuperwallNotificationRequests()` * `UNUserNotificationCenter.current().removeAllDeliveredNonSuperwallNotifications()` You can use the following to remove notifications specific to Superwall: * `UNUserNotificationCenter.current().removeAllDeliveredSuperwallNotifications()` * `UNUserNotificationCenter.current().removeAllPendingSuperwallNotificationRequests()` ### Advanced Here you can apply custom CSS and JS to your paywall. ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/88811cb-Screenshot_2023-06-14_at_17.57.21.png)