# 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

# Multiple Choice

Capture user selections with multiple choice elements for branching, personalization, and data collection.

The multiple choice element presents a set of options for users to select from. It is commonly used in onboarding flows to gather preferences, capture survey responses, or enable [branching](/docs/dashboard/dashboard-creating-flows/linking-pages) based on user input.

### Adding a multiple choice element

To add a multiple choice element:

1. In the left sidebar, click **+** to add a new element.
2. Choose **Multiple Choice** under the "Onboarding" header.

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/component_add_mc.jpg)

A multiple choice component has configuration options to add items, randomize ordering, and more. Select it from the sidebar, and you'll see these options on the right sidebar:

![](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/comps_mc_props.jpg)

### Selection mode

You can configure whether users select one option or multiple:

* **Single-select:** Users pick one option. The selection replaces any previous choice.
* **Multi-select:** Users can pick multiple options. All selections are stored.

### Randomize order

Enable **Randomize order** to shuffle the options each time the element appears. This is useful for surveys where you want to reduce selection bias from item ordering.

### Items

Each choice has two parts:

* **Label:** The text users see (e.g., "Grow subscriptions").
* **Value:** The internal value stored when selected (e.g., `goal_grow`).

Keep values short and consistent. Use lowercase letters and underscores for readability (e.g., `preferred_plan`, `user_goal`).

To add more choices, click **+ Add** in the component editor. You can reorder choices by dragging them.

### Using selections

Any multiple choice item is available as a variable. You can view variables either from the left side [variables](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-variables) menu, or via the floating toolbar. Either case, it's exposed via **Element -> Multiple Choice**.

Two variables are available for each multiple choice element:

* **`selectedValue`:** The programmatic value of the selected choice (e.g., `goal_grow`). Use this for routing conditions, storing as user attributes, or any logic that depends on a stable internal value.
* **`selectedLabel`:** The display label of the selected choice (e.g., "Grow subscriptions"). This is useful for showing the user's selection back to them in text on a later page. If localization is active, `selectedLabel` returns the translated label for the user's locale.

When a user makes a selection, these variables can be used in several ways:

* **Routing conditions:** Branch the flow based on what the user selected. See [branching](/docs/dashboard/dashboard-creating-flows/linking-pages#branching).
* **User attributes:** Store the selection as a user attribute for later personalization or analytics.
* **Dynamic values:** Reference the selection in text elsewhere on the page or in later pages.

### Using selections for branching

Multiple choice is the primary way to enable conditional branching in flows. After a user selects an option, you can route them to different pages based on their choice.

For example, if you ask "What is your primary goal?" with options like "Grow subscriptions" and "Reduce churn," you can send each group to a tailored page.

See [Linking Pages](/docs/dashboard/dashboard-creating-flows/linking-pages) for detailed branching setup.

### Localization

Multiple choice labels can be localized just like text elements. When you add a language in the [localization panel](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-localization), choice labels are included alongside your other translatable strings. This means:

* **AI Localize** translates choice labels automatically with the rest of your text.
* **CSV export/import** includes choice labels as rows, so your translation workflow covers them.
* **Missing translation filters** account for choice labels, so you can spot untranslated options.
* **Outdated detection** flags choice labels when the base text changes after translation.

When a user makes a selection while localization is active, the `selectedLabel` variable returns the translated text for their locale.

> **Tip:** Multiple choice elements work in both standalone paywalls and multi-page flows. In flows, they unlock branching. In paywalls, they can capture preferences before purchase.