# 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

# overrideProductsByName

Globally override products on any paywall by product name.

## Purpose

Allows you to globally override products on any paywall that have a given name. The key is the product name in the paywall, and the value is the product identifier to replace it with. This is useful for A/B testing different products or dynamically changing products based on user segments.

## Signature

```dart
// Setter
set overrideProductsByName(Map<String, String>? overrideProducts)

// Getter
Future<Map<String, String>?> getOverrideProductsByName()
```

## Parameters

<TypeTable
  type="{
  overrideProducts: {
    type: &#x22;Map<String, String>?&#x22;,
    description: &#x22;A map where keys are product names in paywalls (e.g., `\&#x22;primary\&#x22;`, `\&#x22;secondary\&#x22;`) and values are the product identifiers to replace them with (e.g., `\&#x22;com.example.premium_monthly\&#x22;`). Pass `null` to clear all overrides.&#x22;,
  },
}"
/>

## Returns / State

* **Setter**: Sets the global product overrides. Changes take effect immediately for all future paywall presentations.
* **Getter**: Returns a `Future<Map<String, String>?>` containing the current override mapping, or `null` if no overrides are set.

## Usage

Setting product overrides:

```dart
// Override products globally
Superwall.shared.overrideProductsByName = {
  'primary': 'com.example.premium_monthly',
  'secondary': 'com.example.premium_annual',
  'tertiary': 'com.example.premium_lifetime',
};

// All paywalls will now use these product identifiers
// instead of the ones configured in the dashboard
```

Clearing overrides:

```dart
// Clear all overrides
Superwall.shared.overrideProductsByName = null;
```

Getting current overrides:

```dart
final overrides = await Superwall.shared.getOverrideProductsByName();
if (overrides != null) {
  print('Current overrides: $overrides');
} else {
  print('No overrides set');
}
```

Dynamic overrides based on user segment:

```dart
void _setProductOverridesForUser(User user) {
  if (user.isPremium) {
    // Premium users get annual products
    Superwall.shared.overrideProductsByName = {
      'primary': 'com.example.premium_annual',
    };
  } else {
    // Regular users get monthly products
    Superwall.shared.overrideProductsByName = {
      'primary': 'com.example.premium_monthly',
    };
  }
}
```

A/B testing different products:

```dart
void _setupProductABTest() {
  final random = Random();
  if (random.nextBool()) {
    // Variant A: Monthly product
    Superwall.shared.overrideProductsByName = {
      'primary': 'com.example.premium_monthly',
    };
  } else {
    // Variant B: Annual product
    Superwall.shared.overrideProductsByName = {
      'primary': 'com.example.premium_annual',
    };
  }
}
```

## Notes

* Overrides apply globally to all paywalls that use the specified product names
* Overrides take effect immediately for all future paywall presentations
* You can also set overrides per-paywall using [`PaywallOptions.overrideProductsByName`](/docs/flutter/sdk-reference/PaywallOptions#overrideproductsbyname)
* Per-paywall overrides take precedence over global overrides

## Related

* [`PaywallOptions.overrideProductsByName`](/docs/flutter/sdk-reference/PaywallOptions) - Override products for a specific paywall
* [`PaywallOptions`](/docs/flutter/sdk-reference/PaywallOptions) - Paywall configuration options