# 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

# Home Page

The Superwall Dashboard is your control center. This is where you configure paywalls, set up triggers, view analytics and more. If you don’t already have an account, you can [sign up for free](http://superwall.com/sign-up).

When you log in for the first time or create a new app, you'll see an onboarding checklist titled **Getting Started**:

![](https://superwall.com/docs/images/d52485e-Screen_Shot_2022-05-17_at_2.06.11_PM.png)

As you complete the steps to integrate Superwall these items will check off automatically. See our [Quick Start](/docs/sdk/quickstart/install) guide for help.

### Paywalls

> 👍
>
> Superwall builds everyone a free paywall by hand
>
> Superwall has built hundreds of paywalls for clients and has a unique vantage point on the industry. As a token of gratitude for signing up, we create a paywall for each customer, using best practices we've picked up along the way. Check your email for updates :)

The [Paywalls](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-overview) section of the dashboard is where you'll configure and manage all your paywalls. When you first log in, you'll see an **Example Paywall** built out for you.

Here's what your Paywalls section might look like at scale.

![](https://superwall.com/docs/images/d224012-Screenshot_2022-11-28_at_14.28.05.png)

You can toggle its interface style to view analytics too.

### Campaigns

The [Campaigns](/docs/dashboard/dashboard-campaigns/campaigns) section of the dashboard is where you configure *when* and *who* to show a paywall to, using triggers and rules. In the image below, Campaign 2 is triggered when the SDK fires either a `pressed_continue_welcome_screen` or `load_feed` event. Campaign 1's trigger is switched *off*, indicated by a cross through its icon and lack of background color. This means that the campaign won't be triggered for a `viewed_welcome_screen` event:

![](https://superwall.com/docs/images/db38070-Screen_Shot_2022-05-17_at_2.28.22_PM.png)

### Analytics

After integrating Superwall into your app, you'll notice useful analytics populate in realtime at the top of the dashboard. You can use the top right dropdown to toggle between data for **New Installs** and **All Users**, as well as refine the date range.

![](https://superwall.com/docs/images/7f47f4d-Screenshot_2022-11-28_at_14.32.08.png)

Clicking a metric redirects to the Charts page where you can break down a chart for a given time range and granularity:

![](https://superwall.com/docs/images/31908e7-Screenshot_2022-11-28_at_14.36.32.png)

Below the high level metrics on the dashboard, you can see breakdowns per campaign/trigger/rule/paywall for the selected date range:

![](https://superwall.com/docs/images/bf7ca69-Screenshot_2022-11-28_at_14.45.50.png)

### Settings

Clicking the **sign out icon** in the bottom left corner will bring up a list of
actions that allow you sign out or switch teams to view different apps.

![Logout](https://superwall.com/docs/images/dashboard/logout.png)