# 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 # Local Resources Use images, videos, and other media bundled in your app for faster paywall loading and offline support. Local resources let you reference media files (such as images and videos) that are bundled directly in your app rather than hosted on a remote server. This means faster load times, no network dependency for those assets, and a smoother experience for your users. > **Note:** Local resources require **iOS SDK v4.13.0+** or **Android SDK v2.7.7+**. They are not available on > other platforms at this time. ### How it works Instead of pointing an image or video to a URL, you can point it to a **local resource ID**. This ID maps to a file that the developer has registered in the native SDK. When the paywall loads, the SDK intercepts the request and serves the file directly from the device. No network call is required. Set up those resource IDs in your app first by following the [SDK Local Resources guide](/docs/sdk/guides/local-resources). The editor discovers which resource IDs are available by looking at device attribute events your app has reported in the last 7 days. This means at least one device running your app with the SDK configured must have reported its local resources before they appear in the editor. ### Setting a local resource on an image To use a local resource for an image component: 1. **Select** the image component in the Layout tab or on the canvas. 2. In the component editor, find the image source property. 3. **Click** the **+ Add Local Resource** button. 4. A dropdown will appear listing all resource IDs that devices have reported recently. **Select** the one you want. ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-local-resource.jpg) The image source will update to use the selected local resource. You can still provide a regular image URL as a **fallback**. If the local resource is unavailable (for example, in the web preview or on a device that hasn't registered that resource), the paywall will fall back to the remote URL automatically. ### Setting a local resource on a video The same flow applies to video components. Select a video, click **+ Add Local Resource**, and choose the resource ID from the dropdown. A fallback URL is recommended for the same reasons as images. ### Fallback behavior When a local resource is set, the paywall rendering follows this order: 1. **Try the local resource.** The SDK attempts to load the file from the device using the registered resource ID. 2. **Fall back to the remote URL.** If the local file isn't available (not registered, missing from the bundle, or running in the web preview), the regular image or video URL is used instead. This means you can safely set a local resource without breaking the paywall for users on older SDK versions or other platforms. ### Availability in the editor The resource ID dropdown is populated from device attribute events sent by your app. If you don't see any resource IDs: * Make sure at least one test device is running your app with the local resources configured in the SDK. For setup instructions, see the [SDK Local Resources guide](/docs/sdk/guides/local-resources). * The device must have opened a paywall or otherwise triggered a device attributes event within the **last 7 days**. * Only **iOS** and **Android** platforms support local resources. The dropdown will not appear for other platforms. > **Warning:** If a resource ID hasn't been reported by any device in the last 7 days, the editor will show a > warning. This usually means no active devices have that resource registered, so double-check your > SDK configuration. ### When to use local resources Local resources are a great fit for: * **Onboarding videos or hero images** that are critical to the first paywall experience and shouldn't depend on network conditions. * **Large media files** where you want to avoid CDN costs or ensure instant loading. * **Offline scenarios** where users may not have a reliable connection when the paywall is presented. For smaller or frequently changing images, remote URLs are still the simpler choice since they don't require an app update to change. ### Related * [SDK Local Resources Guide](/docs/sdk/guides/local-resources): How to register local resources in supported SDKs. * [Styling Elements](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements): General component styling and image editing. * [Liquid inside Image URLs](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-liquid#liquid-inside-image-urls): Using dynamic URLs for images.