# 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

# Flow Elements

Add interactive elements to your flows: multiple choice, text entry, progress indicators, and date pickers.

Flows can be enhanced with interactive components designed for multi-page experiences. They capture user input, show progress, or request permissions. Use them to personalize the flow or gather information for branching.

## Multiple Choice

The multiple choice element presents options for users to select. This is the key element for enabling branching. User selections can determine which page they see next.

![A multiple choice element in a flow](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_mc_example.jpg)

### Configuration

* **Single-select or multi-select:** Choose whether users can pick one option or multiple.
* **Randomize order:** Shuffle the options each time (useful for surveys to reduce bias).
* **Choice items:** Each choice has a label and a value.

### Labels and values

Each choice has two parts:

* **Label:** What users see (e.g., "Grow subscriptions").
* **Value:** What gets stored (e.g., `goal_grow`).

The value is used internally for routing conditions and user attributes. Keep values short and consistent (lowercase, underscores).

![Labels and values for multiple choice items](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_mc_items_example.jpg)

### Storing selections

When a user makes a selection, two variables are available: `selectedValue` (the internal value, e.g., `goal_grow`) and `selectedLabel` (the display text, e.g., "Grow subscriptions"). If localization is active, `selectedLabel` returns the translated label for the user's locale.

You can use these in routing conditions to branch the flow, store them as user attributes for analytics or personalization, reference them in dynamic content on later pages, or pass them to your backend via webhooks.

> **Tip:** Multiple choice controls are commonly used for [branching](/docs/dashboard/dashboard-creating-flows/linking-pages).

## Input

The input element lets users type a response, like their name, email, or feedback.

![An input element in a flow](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_input_example.jpg)

### Configuration

* **Placeholder text:** The hint shown before users type.
* **Keyboard type:** Choose the appropriate keyboard (default, email, number, etc.).

### Storing responses

Like multiple choice, text entry values can be stored as user attributes. This is useful for personalizing later pages with the user's name, capturing email addresses for follow-up, or collecting feedback or custom responses.

## Indicator

The indicator element shows progress through the flow, like "Step 2 of 5."

![An indicator element in a flow](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_indicator_example.jpg)

### Configuration

* **Style:** Choose from different visual styles (dots, bars, numbers).
* **Current step:** Which step to highlight.
* **Total steps:** How many steps to show.

Add an indicator when your flow has more than 3-4 pages. Users are more likely to complete a flow when they can see their progress and know how much is left. You can also use their properties in dynamic values such as progression:

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

## Date Picker

The date picker element lets users select a date, time, or both using a scrollable wheel or compact input. This is useful for collecting birthdates, scheduling preferences, or any date-related input during onboarding.

![A date picker element in a flow](https://963b3ab1-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_datepicker_example.jpg)

### Configuration

* **Style:** Choose between **Wheel** (scrollable columns) or **Compact** (native date/time input).
* **Components:** Choose what to collect.
  * Wheel style supports **Date & Time**, **Date**, **Time**, and **Time List** (a single scrolling column with pre-formatted time options).
  * Compact style supports **Date** and **Time**.
* **Min Date / Max Date:** Constrain the selectable range. Options are **No Limit**, **Today**, **Relative** (e.g., 30 days before or 1 year after today), or a **Fixed Date**.
* **Minute Interval:** When using a time component with the wheel style, set the interval between selectable minutes (1, 5, 10, 15, 30, or 60).

### Storing selections

The selected value is stored as a string and accessible as a variable. The format depends on what components are configured: `YYYY-MM-DD` for date, `HH:MM:SS` for time, or `YYYY-MM-DDTHH:MM:SS` for date and time. You can use this value in routing conditions, dynamic content on later pages, or pass it to your backend.