# 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

# Why Are Users Still Seeing a Removed Paywall?

Troubleshoot why some users continue to see a paywall that you have removed from all campaigns, and learn how to reset sticky assignments.

## Symptoms

* A user purchases through or sees a paywall that no longer exists in any active campaign.
* You replaced an old paywall with a new one, but some users still see the old version.
* 100% of users should be seeing a new paywall, yet reports of the old paywall persist.

## Cause

Superwall uses **sticky assignments** to ensure consistent user experiences during experiments. When a user is first assigned to a paywall variant, that assignment is stored on the server and persists indefinitely. This means:

* Removing a paywall from a campaign does not automatically clear existing assignments.
* Users who were previously assigned to the old paywall will continue to see it, even if it is no longer attached to any audience.
* Changing presentation percentages or swapping paywalls only affects **new users** who have not yet been assigned.

This behavior is intentional. It preserves experiment integrity and allows you to keep existing users on old pricing while testing new pricing with new users. However, it can be surprising when you want all users to see a new paywall immediately.

> **Note:** Calling `Superwall.shared.reset()` clears on-device data but does **not** clear server-side assignments. The old assignment will be restored the next time the user triggers the placement.

## Solution

To force all previously-assigned users onto your new paywall, you need to reset the assignments in the dashboard.

### Open the campaignGo to **Campaigns** in the Superwall dashboard and select the campaign where the old paywall was previously configured.### Navigate to the audience's experimentClick the **Paywalls** tab for the relevant audience. You should see the old paywall variant listed, possibly with a count of assigned users still shown next to it.### Reset the assignmentsClick the **refresh icon** next to the assignment count for the old paywall variant. This clears all stored assignments for that variant, forcing those users to be reassigned based on your current campaign configuration the next time they trigger the placement.

> **Warning:** Resetting assignments also resets the experiment stats for that audience. If you need to preserve metrics, consider setting the old paywall's presentation percentage to 0% instead of resetting, then allowing new assignments to naturally flow to the new paywall.

## Preventing This in the Future

When replacing a paywall in a campaign, keep these points in mind:

* **Swap, then reset.** After adding the new paywall and removing the old one, reset assignments so existing users are reassigned.
* **Use presentation percentages.** If you want a gradual rollout, set the old paywall to 0% and the new one to 100%. New users will see the new paywall, but existing users will keep their current assignment until you reset.
* **Remove vs. reset.** Removing a paywall from an audience does not reset its assignments. You must explicitly reset assignments to clear them.