# 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

# SuperwallDelegate

A protocol that handles Superwall lifecycle events and analytics.

> **Note:** Set the delegate using `Superwall.shared.delegate = self` to receive these callbacks.

> **Tip:** Use `handleSuperwallEvent(withInfo:)` to track Superwall analytics events in your own analytics platform for a complete view of user behavior.

## Purpose

Provides callbacks for Superwall lifecycle events, analytics tracking, and custom paywall interactions.

## Signature

```swift
public protocol SuperwallDelegate: AnyObject {
  @MainActor
  func subscriptionStatusDidChange(
    from oldValue: SubscriptionStatus,
    to newValue: SubscriptionStatus
  )
  
  @MainActor
  func handleSuperwallEvent(withInfo eventInfo: SuperwallEventInfo)
  
  @MainActor
  func handleCustomPaywallAction(withName name: String)
  
  @MainActor
  func willDismissPaywall(withInfo paywallInfo: PaywallInfo)
  
  @MainActor
  func willPresentPaywall(withInfo paywallInfo: PaywallInfo)
  
  @MainActor
  func didDismissPaywall(withInfo paywallInfo: PaywallInfo)
  
  @MainActor
  func didPresentPaywall(withInfo paywallInfo: PaywallInfo)
  
  @MainActor
  func paywallWillOpenURL(url: URL)
  
  @MainActor
  func paywallWillOpenDeepLink(url: URL)
  
  @MainActor
  func handleLog(
    level: LogLevel,
    scope: LogScope,
    message: String,
    info: [String: Any]?,
    error: Error?
  )
  
  @MainActor
  func customerInfoDidChange(
    from oldValue: CustomerInfo,
    to newValue: CustomerInfo
  )

  @MainActor
  func userAttributesDidChange(newAttributes: [String: Any])
}
```

## Parameters

All methods are optional to implement. Key methods include:

<TypeTable
  type="{
  subscriptionStatusDidChange: {
    type: &#x22;oldValue: SubscriptionStatus, newValue: SubscriptionStatus&#x22;,
    description: &#x22;Called when subscription status changes.&#x22;,
    required: true,
  },
  handleSuperwallEvent: {
    type: &#x22;eventInfo: SuperwallEventInfo&#x22;,
    description: &#x22;Called for all internal analytics events. Use for tracking in your own analytics.&#x22;,
    required: true,
  },
  handleCustomPaywallAction: {
    type: &#x22;name: String&#x22;,
    description: &#x22;Called when user taps elements with `data-pw-custom` tags.&#x22;,
    required: true,
  },
  willPresentPaywall: {
    type: &#x22;paywallInfo: PaywallInfo&#x22;,
    description: &#x22;Called before paywall presentation.&#x22;,
    required: true,
  },
  didPresentPaywall: {
    type: &#x22;paywallInfo: PaywallInfo&#x22;,
    description: &#x22;Called after paywall presentation.&#x22;,
    required: true,
  },
  willDismissPaywall: {
    type: &#x22;paywallInfo: PaywallInfo&#x22;,
    description: &#x22;Called before paywall dismissal.&#x22;,
    required: true,
  },
  didDismissPaywall: {
    type: &#x22;paywallInfo: PaywallInfo&#x22;,
    description: &#x22;Called after paywall dismissal.&#x22;,
    required: true,
  },
  customerInfoDidChange: {
    type: &#x22;oldValue: CustomerInfo, newValue: CustomerInfo&#x22;,
    description: &#x22;Called when customer info changes. Available in version 4.10.0+.&#x22;,
    required: true,
  },
  userAttributesDidChange: {
    type: &#x22;newAttributes: [String: Any]&#x22;,
    description: &#x22;Called when user attributes change outside your app (for example via the \u201cSet user attributes\u201d paywall action).&#x22;,
    required: true,
  },
}"
/>

## Returns / State

All delegate methods return `Void`. They provide information about Superwall events and state changes.

## Usage

Basic delegate setup:

```swift
class ViewController: UIViewController, SuperwallDelegate {
  
  override func viewDidLoad() {
    super.viewDidLoad()
    Superwall.shared.delegate = self
  }
}
```

Track subscription status changes:

```swift
func subscriptionStatusDidChange(
  from oldValue: SubscriptionStatus,
  to newValue: SubscriptionStatus
) {
  print("Subscription changed from \(oldValue) to \(newValue)")
  updateUI(for: newValue)
}
```

Forward analytics events:

```swift
func handleSuperwallEvent(withInfo eventInfo: SuperwallEventInfo) {
  switch eventInfo.event {
  case .paywallOpen(let info):
    Analytics.track("paywall_opened", properties: [
      "paywall_id": info.id,
      "placement": info.placement
    ])
  case .transactionComplete(let transaction, let product, _, let info):
    Analytics.track("subscription_purchased", properties: [
      "product_id": product.id,
      "paywall_id": info.id
    ])
  case .permissionGranted(let permission, let paywallId):
    Analytics.track("permission_granted", properties: [
      "permission": permission,
      "paywall_id": paywallId
    ])
  case .permissionDenied(let permission, let paywallId):
    Analytics.track("permission_denied", properties: [
      "permission": permission,
      "paywall_id": paywallId
    ])
  default:
    break
  }
}
```

Handle custom paywall actions:

```swift
func handleCustomPaywallAction(withName name: String) {
  switch name {
  case "help":
    presentHelpScreen()
  case "contact":
    presentContactForm()
  default:
    print("Unknown custom action: \(name)")
  }
}
```

Handle paywall lifecycle:

```swift
func willPresentPaywall(withInfo paywallInfo: PaywallInfo) {
  // Pause video, hide UI, etc.
  pauseBackgroundTasks()
}

func didDismissPaywall(withInfo paywallInfo: PaywallInfo) {
  // Resume video, show UI, etc.
  resumeBackgroundTasks()
}
```

Handle customer info changes:

```swift
func customerInfoDidChange(
  from oldValue: CustomerInfo,
  to newValue: CustomerInfo
) {
  // Check if user gained or lost subscriptions
  let oldSubscriptionCount = oldValue.subscriptions.count
  let newSubscriptionCount = newValue.subscriptions.count
  
  if newSubscriptionCount > oldSubscriptionCount {
    print("User gained a new subscription")
  }
  
  // Update purchase history UI
  updatePurchaseHistoryUI(with: newValue)
}

func userAttributesDidChange(newAttributes: [String: Any]) {
  // React to server-driven or paywall-triggered updates
  refreshProfileUI(with: newAttributes)
}
```