# 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
# Presenting Paywalls from One Another
Learn how to present a different paywall from one that's already presented.
It's possible to present another paywall from one already showing. This can be useful if you want to highlight a special discount, offer, or emphasize another feature more effectively using a different paywall. Check out the example here:
* A [placement](/docs/dashboard/dashboard-campaigns/campaigns-placements) is evaluated when the button is tapped. Superwall sees that the user isn't subscribed, so a paywall is shown.
* Next, the user taps the "Custom Icons Too 👀" button.
* The current paywall dismisses, and then presents the icons-centric paywall.
> **Tip:** You can extend this technique to be used with several other interesting standard placements. For
> example, presenting a paywall when the user abandons a transaction, responds to a survey and more.
> Check out the examples [here](/docs/dashboard/dashboard-campaigns/campaigns-standard-placements#standard-placements).
There are two different ways you can do this, with [custom placements](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements#tap-behaviors) or by using [deep links](/docs/sdk/quickstart/in-app-paywall-previews). We recommend using custom placements, as the setup is a little easier.
> **Note:** Custom placements minimum SDK requirements are 3.7.3 for iOS, 1.2.4 for Android, 1.2.2 for
> flutter, and 1.2.6 for React Native.
They both have the same idea, though. You create a new campaign specifically for this purpose, attach a paywall and either add a filter (for deep linking) or a new placement (for custom placements) to match users to it.
> **Note:** While it's not *required* to make a new campaign, it is best practice. Then, if you later have
> other paywalls you wish to open in the same manner, you can simply add a new
> [audience](/docs/dashboard/dashboard-campaigns/campaigns-audience) for them in the campaign you make from the steps below.
### Use Custom Placements
## Add a Custom Placement Tap Behavior
Select a component on your paywall and add a **Custom Placement** Tap Behavior, and name it whatever you wish (i.e. showIconPaywall).
Finally, be sure to click **Publish** at the top of the editor to push your changes live
## Create a campaign for the other paywall to show
Create a new [campaign](/docs/dashboard/dashboard-campaigns/campaigns) specifically for this purpose, here — it's called "Custom Placement Example":
## Add the placement
In your new campaign, [add a new placement](/docs/dashboard/dashboard-campaigns/campaigns-placements#adding-a-placement) that matches the name of your custom action you added in step one. For us, that's `showIconPaywall`:
## Choose a paywall to show
Finally, choose a paywall that should present by **clicking** on the **Paywalls** button at the top:
### Use Deep Links
## Setup Deep Links
You'll need [deep links](/docs/sdk/quickstart/in-app-paywall-previews) set up for your app. This is how Superwall
will query parameters and later launch your desired paywall.
## Trigger the deep link from an existing paywall
Choose the paywall you want to open another paywall from. Then, click the element (a button, text, etc.) that should open the new paywall:1) In its component properties on the right-hand side, add a **Tap Behavior**.
2) Set its **Action** to **Open Url**.
3) For the URL, use your deep link scheme from step one, and then append a parameter which will represent which other paywall to present. This is specific to your app, but here — `offer` is the key and `icons` is the value. Your resulting URL should be constructed like this: `deepLinkScheme://?someKey=someValue`.
4) Set its **Type** to **Deep Link**.
5) Click **Done**.Here's what it should look like (again, with your own values here):
Finally, be sure to click **Publish** at the top of the editor to push your changes live.
## Create a campaign for the other paywall to show
Create a new [campaign](/docs/dashboard/dashboard-campaigns/campaigns) specifically for this purpose, here — it's called "Deeplink Example":
## Add the placement
In your new campaign, [add a placement](/docs/dashboard/dashboard-campaigns/campaigns-placements#adding-a-placement) for the `deepLink_open` standard placement:
## Edit the audience filter
Edit the default audience's filter to match `params.[whatever-you-named-the-parameter]`. Recall that in our example, the parameter was `offer` and the value was `icons`. So here, we'd type `params.offer` and **click** the **+** button:
Superwall will ask what type of new parameter this is — choose **Placement** and enter the parameter name once more (i.e. "offer"). Click **Save**:
Finally, choose the **is** operator and type in the value of your parameter (in our case, "icons"). Then, **click** the **+ Add Filter** button. Here's what it should look like:
## Choose a paywall to show
Finally, choose a paywall that should present by **clicking** on the **Paywalls** button at the top:
### Test Opens
After following the steps above for either method, be sure to test out your presentation. Open the relevant paywall on a device and tap on whichever button should trigger the logic. The currently presented paywall should dismiss, and then immediately after — the other paywall will show.