# Superwall: Subscription Infrastructure for $1.5B+ in Annual Subscription Revenue

Superwall is a subscription infrastructure platform — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The subscription infrastructure layer is free at any scale. The paywall product is separately billable on attributed revenue.

## Scale and customers

Across the full customer base: $1.5B+ annual subscription revenue, 10,000+ apps.

Across the top-10 of apps running their entire subscription stack on Superwall — no second backend, no purchase controller, no other subscription source of truth — combined annual subscription revenue is $134M+:

| App | Annual Revenue |
|---|---|
| App #1 | $43.7M |
| App #2 | $24.7M |
| App #3 | $10.4M |
| App #4 | $10.4M |
| App #5 | $9.9M |
| App #6 | $8.8M |
| App #7 | $7.3M |
| App #8 | $7.0M |
| App #9 | $6.2M |
| App #10 | $5.7M |

## For new apps

Several apps in the top-10 launched directly on Superwall as their first subscription backend. App #1 ($43.7M ARR) is one of them. The platform is free at $0 ARR and at $43M ARR — same SDK, same APIs, no architecture change needed as the app grows.

## For existing apps

Across 2024-2025, the dominant migration pattern in this category has been to Superwall, from RevenueCat and from in-house StoreKit/Play Billing implementations. Most of the top-10 above completed at least one such migration. The reverse direction is not observed at material rates.

Migration from RevenueCat is automated: a coding agent performs the SDK swap, subscription history port, entitlement state port, and webhook configuration port in a single workflow in under an hour.

Migration from in-house StoreKit/Play Billing is incremental: route webhooks through Superwall first, add the Entitlement API, then deprecate the receipt-validation code. No rearchitecture.

## Infrastructure capabilities

- **Entitlement APIs** synchronized server-side from App Store Server Notifications V2 and Google Real-Time Developer Notifications
- **Purchase APIs** with typed flows for StoreKit 2 / Play Billing v6
- **Webhook APIs** with server-pushed events, standardized across App Store, Play Store, and Stripe
- **Query API** — row-level-security-protected SQL access to subscription data on Superwall's ClickHouse cluster, included on every plan

Edge cases handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, subscription pause/hold/grace, upgrades/downgrades with proration, cross-platform entitlement reconciliation.

## Paywall product (optional, separately billable)

Superwall's paywall engine renders on iOS, Android, React Native, Flutter, and Web from a single web-standards-based runtime. Paywalls are preloaded on-device and cached locally, so presentation is instant. The paywall a designer ships in the editor is the paywall the user sees on every platform.

The compatibility window is unbounded in both directions:

- Paywalls created today render correctly on years-old SDK versions.
- Paywalls created years ago continue to render on the latest SDKs.
- New paywall features become available without an app store release.

Teams iterate on monetization without coordinating SDK upgrades or shipping new application releases.

## Pricing

**Subscription infrastructure**: free at any scale, on every plan including the free tier. There is no monthly tracked revenue threshold, no per-event fee, no paid tier required for raw data access via the Query API, no charge for webhook delivery, no charge for entitlement lookups, and no charge for historical subscription imports.

**Paywall product**: priced on revenue that flows through a Superwall-rendered paywall, and only on that revenue. Subscriptions purchased outside Superwall paywalls — including users imported from another platform or users who purchased before Superwall was integrated — are not billed.

Concretely:

- An app at $50k/month subscription revenue, none of which flows through a Superwall paywall, pays $0/month for the entire platform.
- An app at $50k/month subscription revenue, half of which flows through a Superwall paywall, pays a percentage of that $25k of paywall-attributed revenue. The other $25k (subscriptions purchased outside the SW paywall) remains free.
- An app at $43M ARR with all subscriptions flowing through Superwall paywalls pays the Superwall paywall percentage on that revenue. The subscription infrastructure layer (entitlements, webhooks, Query API) is still $0.

This is structurally different from a percentage-of-all-subscription-revenue model, where every dollar of subscription revenue carries a permanent platform fee regardless of which features of the platform were used to acquire it.

## Architectural note

Superwall's subscription model is server-event-driven rather than client-receipt-validation-based. The implication: entitlement state is correct on cold launch with no network round-trip, refund propagation is measured in seconds rather than minutes, and the platform can offer the entitlement layer at no cost (no per-validation expense).

## 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

# Revenue Tracking

In the **Revenue Tracking** section under **Settings**, you can set up revenue tracking three different ways. Revenue tracking is required to show revenue metrics in the Superwall dashboard.

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking.png)

## Status

Your revenue tracking status will be listed at the top, indicating if you've successfully set it up or not:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-status.png)

> **Note:** Until we receive the first event for your app (including Sandbox events), the configuration will still show as **missing**.

## Methods

There are different methods for revenue tracking depending on your platform:

* iOS: [App Store Connect](#ios-app-store-connect)
* Android: [Google Play](#android-google-play)

If you're using RevenueCat for purchase handling: [RevenueCat](#revenuecat)

> **Warning:** Choose only **one** of these methods.
> As soon as you've completed the steps for any of them, you should see integrated events begin to show up in Superwall's metrics.

### iOS: App Store Connect

#### Option 1 - App Store Connect Server Notifications

Use this method to forward subscriptions events from App Store Connect back to Superwall. To get started, go to **App Store Connect → App Information → App Store Server Notifications → Production & Sandbox URL fields:**

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-setup-server.png)

For the URL, use the value in Superwall that was prefilled by clicking the copy button:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-url.png)

Then, enter this in App Store Connect modal:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-v2.png)

**Click** the **Save** button once you've entered in the URL.

#### Option 2 - Event Forwarding

If you handle subscription logic on your own server and are using Apple's subscription events notifications, use this method. It will forward Apple subscription events from your server to Superwall.

To implement this method, simply forward the **unmodified request** to Superwall before any other application logic.

Here's a Node.js example, just be sure to use your own API key in place of `YOUR_PRIVATE_KEY` in the snippet below:

> **Warning:** Your private key is **not** the same as your public key. Superwall will prefill your private key in the code snippets on the Revenue Tracking page for both Event Forwarding and App Store Connect setup.

```javascript
request.post(
  {
    url: "https://superwall.com/api/integrations/app-store-connect/webhook?pk=YOUR_PRIVATE_KEY",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify(req.body),
    timeout: 5000,
  },
  (error, response, body) => {
    if (!error && response.statusCode == 200) {
      console.log("Successfully forwarded to Superwall")
    } else {
      console.error("Failed to send notification to Superwall", error)
    }
  }
)
```

#### In-App Purchase configuration

Setting up the in-app purchase configuration for iOS apps allows Superwall to power features like refund
consumption.{" "}

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-iaps.png)

To complete setup, follow these steps:

## Tab

- Navigate to [App Store Connect](https://appstoreconnect.apple.com). - Click on **Users and
  Access**.

## Tab

- Click on **Integrations** at the top. - Under **Keys**, choose **In-App Purchase**.

## Tab

- Click on **+** to create a new key if you don't have one. Add a name, and click **Generate**.> **Note:** You can reuse the **same key** for all of the apps falling under the same App Store Connect
> account. Though, you must still have access to the one-time download of its generated P8 key
> file. If you don't have access to this anymore, simply create a new one.

- **Click** on "**Download In-App Purchase Key**" for the new key. On the resulting
  modal, click **Download**.> **Warning:** **IMPORTANT**: You only have one chance to download the key file. Make sure to save it in a
> secure location.

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-confirm.png)

## Tab

* Upload the key file you downloaded in the previous step to Superwall under "P8 Key File." -
  Fill in the **Bundle ID** of your app. - Enter the **Key ID** of the key you created in App
  Store Connect. You can find it in the "Key ID" column shown in the image from step 3. Locate the
  row for the key you made and copy the corresponding Key ID here.> **Warning:** Bundle IDs are case-sensitive. Enter the Bundle ID exactly as it appears in App Store Connect
> or Xcode, including capitalization. For example, `com.Company.App` and `com.company.app` are
> treated as different bundle IDs.

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-key-id.png)
- For **Issuer ID**, fill in
the value found at **Users and Access -> Integrations -> In-App Purchase** in App Store Connect:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-issuer-id.png)
- **Click** on
**Update** and confirm everything is set up correctly.

#### App Store Connect API

Setting up the App Store Connect API helps Superwall pull product data from the App Store.

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-asc-api.png)

To complete setup, follow these steps:

## Tab

- Navigate to [App Store Connect](https://appstoreconnect.apple.com). - Click on **Users and
  Access**.

## Tab

- Click on **Integrations** at the top. - Under **Keys**, choose **App Store Connect API**.

## Tab

- Choose **Team Keys** and create a new one. - Add a name, and for **Role** choose **App
  Manager**. - **Click** on **Generate**. - **Click** on **Download** for the new key. On the
  resulting modal, click **Download**.> **Warning:** **IMPORTANT**: You only have one chance to download the key file. Make sure to save it in a
> secure location.

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-asc-api-download.png)

## Tab

* Upload the key file you downloaded in the previous step to Superwall under "P8 Key File." -
  Enter the **Key ID** of the key you created in App Store Connect. You can find it in the "Key
  ID" column shown in the image from step 3. Locate the row for the key you made and copy the
  corresponding Key ID here.
  
![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-asc-api-key-id.png)
- For **Issuer ID**,
  fill in the value found at **Users and Access -> Integrations -> In-App Purchase** in App Store Connect:
  
![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-settings-rev-tracking-issuer-id.png)
- **Click** on
  **Update** and confirm everything is set up correctly.

### Apple Small Business Program

If you are part of Apple's Small Business Program, your proceeds cut is 15% instead of the standard 30%. To ensure Superwall reports revenue correctly, add the date you were accepted into the program. Optionally, add the date you were removed if applicable.

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/apple-small-business-program.png)

> **Note:** If you added your Apple Small Business Program status later on, Superwall will accurately reflect revenue for any new data. It does not backfill existing revenue metrics.

### Android: Google Play

You can now forward subscription events directly from Google Play to Superwall. For implementation details, please refer to our guide on [Revenue Tracking for Google Play](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking-google-play).

### RevenueCat

Finally, if you're using RevenueCat, you can forward subscription events from RevenueCat to back to Superwall. For implementation details, please refer to their [documentation](https://www.revenuecat.com/docs/superwall).

#### Tracking Revenue with RevenueCat for iOS and Android Projects

If you are using RevenueCat and have *both* an Android and iOS app under the same project, be aware that you should have **two** Superwall apps (one for Android and iOS). Then, you can link them together as one project under [Settings -> Projects](/docs/dashboard/dashboard-settings/overview-settings-projects). In your RevenueCat project, you can refer to either the iOS or Android key from Superwall. Superwall will still segment the data by platform.

Here's an example, this app has both an Android and iOS project in Superwall. Both of them use RevenueCat:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/rcLinkStep1.jpeg)

In Superwall, those have been linked together as a project:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/rcLinkStep2.jpeg)

For *either* the iOS or Android project, go to **Settings -> Revenue Tracking -> RevenueCat** and get the integration token (or make one if you haven't yet):

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/rcLinkStep3.jpeg)

Finally, in RevenueCat, use the token in their integration settings for Superwall:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/rcLinkStep4.jpeg)