# 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

# Products Not Loading: iOS Simulator

This is a guide to getting products to load in:

* ✅ iOS Simulator

* ❌ [Real iOS device](/docs/support/troubleshooting/products-not-loading/1253018505-products-not-loading-ios)

If you're having issues with products loading elsewhere please reference the [Products Not Loading: Troubleshooting Guide](/docs/support/troubleshooting/products-not-loading).

***

# Problem

The iOS simulator **cannot** load products directly from Apple like real devices do.

# Solution

In order to load products in an iOS simulator you **have** to set up a [local StoreKit config file](https://superwall.com/docs/ios/guides/testing-purchases). Without it, your products will not load.

This is true regardless of SDK type, native iOS, Flutter, and Expo all need to configure a StoreKit config file **in Xcode** in order to load products on iOS simulator.

Because StoreKit config files supply products *directly* and not from Apple servers, we recommend checking that your products are set up correctly at least once by running from **TestFlight**.

# Still Not Working?

When using a StoreKit config file, products are loaded *directly* from there into the app based on the product id, not from Apple or Superwall servers. If your products are still not loading, it is because one of these two issues

1. Double check that the scheme being run has a StoreKit config correctly set

2. Check that the product ids on your paywall in the Superwall Dashboard **exactly** match what's in your StoreKit config file

# Support

Please check **all** steps before contacting support.

We have covered all known causes for this issue, and aim to make this a completely comprehensive guide. If you have any thoughts on how to improve or know of any other causes, please leave feedback below!