# 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 Preloading and Caching

Make Superwall paywalls open instantly. Learn how the SDK preloads paywalls at launch, how to prioritize or preload specific placements, and how Cache on Device keeps paywalls on the device.

A paywall that has to load when the user taps a button shows a loading state first. Superwall avoids that in two ways: the SDK **preloads** paywalls in the background when your app launches, and it **caches** them, so a paywall that loaded once opens again without waiting on the network.

## How preloading works

Preloading is on by default. When your app launches from a cold start, the SDK fetches your configuration, works out which paywalls the user could see from your campaigns' placements and audiences, and loads those paywalls in the background. Paywalls in audiences the user can't match aren't loaded.

After a paywall loads, the SDK keeps it, and doesn't load it from the network again until you change it on the dashboard.

## Load an important paywall first

If one paywall must be ready right away, such as an onboarding or first-launch paywall, prioritize its campaign with [Priority Placements](/docs/dashboard/dashboard-campaigns/campaigns-placements-prioritized). The SDK loads that campaign's paywalls before the rest.

> **Note:** On Android, use SDK 2.8.7 or later for prioritized preloading. Earlier versions load every assigned paywall in the first batch, alongside the prioritized campaign.

## Control preloading from your app

If your app has many paywalls, preloading all of them can use more network on first launch. You can turn automatic preloading off, then preload only the placements you need:

## Tab

```swift iOS
let options = SuperwallOptions()
options.paywalls.shouldPreload = false
Superwall.configure(apiKey: "MY_API_KEY", options: options)

// Later, preload the paywalls for specific placements
Superwall.shared.preloadPaywalls(forPlacements: ["onboarding_complete"])

// Or preload every paywall
Superwall.shared.preloadAllPaywalls()
```

## Tab

```kotlin Android
val options = SuperwallOptions()
options.paywalls.shouldPreload = false
Superwall.configure(this, apiKey = "MY_API_KEY", options = options)

// Later, preload the paywalls for specific placements
Superwall.instance.preloadPaywalls(setOf("onboarding_complete"))

// Or preload every paywall
Superwall.instance.preloadAllPaywalls()
```

## Tab

```dart Flutter
final options = SuperwallOptions();
options.paywalls.shouldPreload = false;
Superwall.configure("MY_API_KEY", options: options);

// Later, preload the paywalls for specific placements
Superwall.shared.preloadPaywallsForPlacements({"onboarding_complete"});

// Or preload every paywall
Superwall.shared.preloadAllPaywalls();
```

## Tab

```tsx Expo
const { preloadPaywalls, preloadAllPaywalls } = useSuperwall();

// Preload the paywalls for specific placements
await preloadPaywalls(["onboarding_complete"]);

// Or preload every paywall
await preloadAllPaywalls();
```

These methods don't reload paywalls that are already preloaded. For each SDK's options, see [SuperwallOptions](/docs/sdk/guides/configuring#preloading-paywalls).

## Cache on Device

Each paywall also has a **Cache on Device** setting. In the paywall editor, click **Settings** in the sidebar and turn on **Cache on Device**.

With it on, the SDK loads the paywall's web content from the device's cache when it's there, and from the network only when it isn't. This helps most with paywalls that have large assets, such as a video, that would otherwise take a few seconds to fetch. It works on iOS and Android, including apps built with Flutter and Expo.

## How long changes take to reach devices

* Superwall's CDN caches your configuration for up to **1 hour**. After you publish a change, new users get it right away, and existing users can see the old version for up to an hour.
* Reinstalling the app clears the paywalls cached on the device.
* `Superwall.reset()` clears the user's data on the device, but not their assignments on Superwall's servers.

If a paywall still looks old after an hour, see [Why is my paywall not updating after publishing?](/docs/support/troubleshooting/why-is-my-paywall-not-updating-after-publishing)

## Slow or missing network

If the network is slow or unavailable, preloading can't finish, and the SDK retries. See [Handling connectivity interruptions](https://superwall.com/blog/handling-connectivity-interruptions-with-superwall).

## Related

* [Priority Placements](/docs/dashboard/dashboard-campaigns/campaigns-placements-prioritized)
* [Paywall settings](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-settings)
* [Local Resources](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-local-resources), to bundle images and videos with your app so the paywall doesn't download them