# 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

# How do I migrate to Superwall from another provider?

Guide for migrating from Adapty, Qonversion, Glassfy, or other subscription SDKs to Superwall

# How do I migrate to Superwall from another subscription provider?

If you're currently using a subscription management provider like Adapty, Qonversion, Glassfy, or another SDK and want to migrate to Superwall, here's what you need to know.

## Will My Existing Subscribers Keep Their Access?

**Yes.** Superwall reads subscription status directly from the device's App Store (iOS) or Google Play (Android) records. This means:

* Existing subscribers are automatically recognized when you switch SDKs
* No manual migration of subscription data is required
* Users won't experience any interruption to their access

When a user opens your app with the new Superwall SDK, their active subscriptions are detected automatically, regardless of which SDK was used to originally make the purchase.

## What Gets Migrated Automatically

| Data                                             | Migrated?                             |
| ------------------------------------------------ | ------------------------------------- |
| Active subscription status                       | ✅ Yes - read directly from the device |
| Entitlement access                               | ✅ Yes - based on active subscriptions |
| Cross-device sync (same Apple ID/Google account) | ✅ Yes                                 |

## What Does NOT Migrate

| Data                                     | Migrated?                               |
| ---------------------------------------- | --------------------------------------- |
| Historical analytics and metrics         | ❌ No                                    |
| Paywall designs and configurations       | ❌ No - must be recreated in Superwall   |
| A/B test history and experiment data     | ❌ No                                    |
| Custom user attributes from previous SDK | ❌ No - must be re-set via Superwall SDK |

## Re-setting Custom User Attributes

Superwall reads subscription state directly from Apple and Google, so transaction history does not need to be migrated. Your own user metadata can be added as user attributes. The original transaction ID is a stable key that bridges a returning subscriber back to their record in your backend.

The flow:

### Read the original transaction ID on deviceOn iOS, use StoreKit 2's `Transaction.currentEntitlements` and read `transaction.originalID`. On Android, use the Play Billing `purchaseToken`.```swift
import StoreKit

func fetchOriginalTransactionID() async -> String? {
  for await result in Transaction.currentEntitlements {
    guard case .verified(let transaction) = result else { continue }
    return String(transaction.originalID)
  }
  return nil
}
```### Look up the user in your backendSend the original transaction ID to your backend, which returns a stable `userId` and any metadata you want exposed to Superwall (plan tier, signup date, referrer, etc.).### Identify, then set attributesCall `identify` first so the attributes attach to the right user.```swift
Superwall.shared.identify(userId: userId)
Superwall.shared.setUserAttributes([
  "plan_tier": "pro",
  "signup_date": "2024-01-15",
  "referrer": "appstore_search"
])
```

> **Note:** `setUserAttributes` merges with existing attributes rather than replacing them. Pass `nil` for a key to remove it.

> **Warning:** A few things to watch for:- Always call `identify` before `setUserAttributes`, otherwise attributes attach to the anonymous user.
> - On a fresh install before a restore, `currentEntitlements` may be empty.
> - Sandbox and production original transaction IDs differ.
> - With Family Sharing, the original transaction ID belongs to the original purchaser, not the family member.

Run this on app launch (after StoreKit hydrates), after a successful purchase, and after a restore. It is safe to call every launch since `identify` is idempotent.

## Migration Steps

1. Remove your current subscription SDK from your project
2. Follow the [Superwall installation guide](/docs/getting-started-with-our-sdks) for your platform

## Troubleshooting

### Subscription status not detected

If an existing subscriber isn't being recognized:

1. Have them tap "Restore Purchases" on any paywall
2. Ensure they're signed into the same App Store/Google Play account used for the original purchase
3. Check that the subscription hasn't expired