# 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

# Users

Get a snapshot view of users who recently triggered a placement in your app, see their user journey, revenue events and more.

To view information about users who've recently triggered a placement in your app, **click** on the **Users** button in the sidebar. Looking for a summary of how Superwall keeps subscription states in sync and where this data surfaces? See [Subscription Management](/docs/dashboard/subscription-management).

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-users-sidebar.jpeg)

Once there, you'll see a list of users who've had a session within the last 24 hours by default (or you can filter them by a specific event):

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-users-toggle-by-event.jpeg)

### Searching by user identifier

If you need to find a specific user, use the search box at the top:

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-users-search.jpeg)

This will find users by their Superwall identifier (i.e. `$SuperwallAlias:44409AAF-244D-9F08-A18A-8F66B52FDZ01`). Hit **Enter** once you've copied or typed in an identifier, and the matched user's details will display.

### Filtering by event

Use the toggle at the right-hand side to toggle by a specific [placement](/docs/dashboard/dashboard-campaigns/campaigns-placements) or [standard placement](/docs/dashboard/dashboard-campaigns/campaigns-standard-placements) (such as session start, app close, app open, etc).

Below, Superwall displays all of the users who have opened a paywall the last 24 hours:

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-users-main-view.jpeg)

Any placements that are specific to your own app (i.e. ones that you've manually added to a campaign) will show with your app's logo next to it. All of Superwall's standard placements will have a Superwall logo.

> **Tip:** Another great use of the Users dashboard? Get a quick preview of how many times one of your
> placements has fired within the last day. Choose one from the placement toggle, and then you can
> quickly see how many times it's been hit by the resulting users Superwall returns.

### Viewing user profiles

To see more details about a user, click anywhere on one of the rows. Then, the user profile will be presented where you can review revenue events, SDK events, and more:

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-users-profile.jpeg)

It's divided into these sections:

1. **Overview:** Displays key user information including App User ID, Country, Total Spent, SDK Version, and user registration/last seen dates.
2. **Recent Events:** View revenue events and conversions, SDK events, and see the overall breadcrumb of actions the user has taken. You can filter or search by certain events as well.
3. **Entitlements:** Displays any active entitlements the user has attached, how long they'll be active and their corresponding identifiers. See "Granting entitlements" below for more.
4. **Aliases:** Any alias that Superwall has assigned the user will show here. Read more about how user aliases are created [here](/docs/sdk/quickstart/user-management).
5. **Apple Search Ads:** If you have the [Apple Search Ads](/docs/integrations/apple-search-ads) integration activated, you'll see any A.S.A. data that relates to the user (such as the keywords used which led to install, etc).
6. **User:** This houses basic information about the user, such as their install date, user seed and more.
7. **Device:** The user's device details. All device attributes are searchable here as well.

The user profile contains a wealth of information. You can search events by name by using the **Search Events** textbox, and quickly filter by event domains using the toggle at the top-right of the event browser:

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-users-toggle.jpeg)

The domains of events you can search and filter by are:

1. **Overview:** The default option, this shows all of the key events from today.
2. **Superwall Events:** These are [events](/docs/sdk/guides/3rd-party-analytics/tracking-analytics) automatically tracked by Superwall.
3. **App Events:** Placements that you've manually added to a campaign.
4. **Subscriptions Events:** Any transactions, trial starts, and similar subscription events.
5. **All Events:** Displays every single event that's occurred today.

Click on any of them to see more information about the event:

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/overview-users-toggle-metadata.jpeg)

### Granting entitlements

You can manually grant a user any entitlement your app offers. This is useful for activating pro features for someone, handling support issues, and more.

To grant an entitlement, **click** on the **+** icon:

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/grantEntitlement.png)

Then, select an entitlement, expiration date, and optionally a reason for granting it:

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/grantEntitlementOptions.jpeg)

**Click** on the **Grant Entitlement** button to save your changes.

To revoke any entitlement you've granted, **click** on the **Trash icon**:

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/revokeEntitlement.jpeg)

> **Warning:** If you are using a purchase controller, take care to follow our [implementation guide](/docs/sdk/guides/advanced-configuration). For example, manually granted entitlements register in our SDK as web entitlements. If you aren't accounting for those in your purchase controller code, manually granted entitlements will not work. See the example linked above under "Complete example for iOS" for guidance.