# 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

Bundle images, videos, and other assets in your app so paywalls can load them instantly from the device.

Local resources let your paywalls load bundled assets directly from the device instead of fetching them over the network. This is useful for hero images, onboarding videos, and other media that should appear immediately even when the connection is slow.

:::expo
> **Info:** Local resources require **Expo SDK v1.1.3+**.

:::

## Registering local resources

Choose a stable resource ID for each asset you want to serve locally. That same ID is what you'll select in the [paywall editor](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-local-resources) when configuring image or video components.

:::expo
On Expo, pass `localResources` in the `options` prop on `SuperwallProvider`. Entries are resolved during configuration — Metro `require()` results are downloaded via `expo-asset` so the webview can read them from a `file://` URI.

```tsx Expo
import * as FileSystem from "expo-file-system"
import { SuperwallProvider } from "expo-superwall"

export function App() {
  return (
    <SuperwallProvider
      apiKeys={{ ios: "pk_your_ios_api_key", android: "pk_your_android_api_key" }}
      options={{
        localResources: {
          "hero-image": require("./assets/hero.png"),
          "logo": { uri: FileSystem.documentDirectory + "logo.png" },
          "onboarding-video": "file:///path/to/welcome.mp4",
        },
      }}
    >
      {/* your app */}
    </SuperwallProvider>
  )
}
```

> **Warning:** `localResources` is resolved when `SuperwallProvider` configures the SDK. Resources added later
> will not be available to paywalls that already loaded.

:::

## Supported source types

:::expo
Each entry in `localResources` accepts one of:

| Type                         | Use for                                                            |
| ---------------------------- | ------------------------------------------------------------------ |
| `number` (Metro `require()`) | Bundled assets in your Expo project; resolved through `expo-asset` |
| `string`                     | A `file://`, `content://`, or absolute path URI                    |
| `{ uri: string }`            | The same shape used by React Native `Image` sources                |
:::

## Choosing resource IDs

Resource IDs are the contract between your app and the paywall editor. A few guidelines:

* Use stable, descriptive names like `"hero-image"` and `"onboarding-video"`.
* Keep the casing consistent. `"Hero-Image"` and `"hero-image"` are different IDs.
* If you rename an ID, update any paywalls that reference it.

## Referencing local resources in a paywall

In the paywall editor, set a local resource on an image or video component and select the resource ID you registered in the SDK. You can still provide a remote URL as a fallback.

Under the hood, paywalls load these resources through `swlocal://` URLs. For example:

```html
<video src="swlocal://onboarding-video" autoplay muted playsinline></video>
```

If the SDK cannot resolve a local resource, the paywall can fall back to the remote URL configured in the editor.

## Debugging

If a resource ID does not appear in the editor or fails to load:

* Make sure the app is running a compatible SDK version.
* Confirm the resource ID in your paywall exactly matches the key you registered in the SDK.
* Open a paywall on a test device after configuring local resources so the editor can discover recently used IDs.
* Keep a remote fallback URL on critical media so older builds still render correctly.

## Related

:::expo
* [Configuring the SDK](/docs/expo/guides/configuring): Where `localResources` lives in the Expo options surface.
:::

* [Paywall Editor: Local Resources](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-local-resources): How to assign local resource IDs in the dashboard.