# 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

# Web-Only Checkout

Use web checkout without a mobile app for web apps, websites, or any non-App-Store product.

You can use Superwall's [web checkout links](/docs/web-checkout/web-checkout-creating-campaigns-to-show-paywalls) without an iOS or Android app. It's suitable for things like a web app, SaaS products, or any scenario where you want to handle the post-purchase flow yourself.

All that's required is creating a web app in Superwall. Then, for its post-purchase behavior use **Redirect mode** instead of *Redeem* mode:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/webcheckout-noapp-redirect.png)

After a user completes checkout from a paywall, they get redirected to your URL with purchase data as query parameters:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/webcheckout-noapp-redirect-url.png)

For example, if your redirect URL is `https://amazingwebproduct.com/welcome`, then after a successful purchase the redirect URL would be the following:

```javascript
https://amazingwebproduct.com/welcome?
  app_user_id=user_123&
  email=user@example.com&
  stripe_subscription_id=sub_1234567890
```

## Setup

### 1\. Create a Superwall Web App

Create a new app in Superwall for your web product in a new or existing project. Follow the steps in [Creating an App](/docs/web-checkout/web-checkout-creating-an-app).

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/webcheckout-noapp-project.png)

### 2\. Configure Your Payment Provider

Set up Stripe by following the [Stripe Setup](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings) guide.

You can skip any iOS/Android related configuration sections since you won't be using a mobile app.

### 3\. Enable Redirect Mode

In your app's settings under **Post-Purchase Behavior**, select **Redirect** and enter your custom URL.

Your URL will receive the following query parameters after checkout:

| Parameter                | Description                                                                          |
| ------------------------ | ------------------------------------------------------------------------------------ |
| `app_user_id`            | The user's identifier (if you set one)                                               |
| `email`                  | User's email from checkout                                                           |
| `stripe_subscription_id` | The Stripe subscription ID, or the Stripe Checkout session ID for one-time purchases |
| Custom parameters        | Any placement parameters you set                                                     |

**Example redirect:**

```javascript
https://amazingwebproduct.com/welcome?
  app_user_id=user_123&
  email=user@example.com&
  stripe_subscription_id=sub_1234567890
```

### 4\. Handle the Redirect

When users land on your redirect URL, use the query parameters to:

* Verify the purchase with your backend.
* Create or update the user's account.
* Grant access to your product.
* Show a success or onboarding page.

## What's Next

* [Creating Products](/docs/web-checkout/web-checkout-adding-a-stripe-product) to add products to your checkout.
* [Creating Campaigns](/docs/web-checkout/web-checkout-creating-campaigns-to-show-paywalls) to show paywalls via  web checkout links. Remember, you use these URLs in any way you wish, but the checkout link itself is derived from two things:

1. The web paywall domain you created for the web app (found in Settings -> General).
2. And, the placement which is housed in a campaign.