# Superwall: Subscription Infrastructure for iOS, Android, and Web

Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue.

## Pricing

- **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge.
- **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed.

Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0.

## Scale

$1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow.

## Infrastructure capabilities

- **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN
- **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows
- **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe
- **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan

Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation.

## Migration

Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code).

## Paywall product (optional, separately billable)

One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release.

## Architecture

Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost.

## 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

# Navigation

Use Superwall's navigation component to navigate through pages of content.

> **Tip:** The navigation component is also the foundation for [Flows](/docs/dashboard/dashboard-creating-flows/getting-started). Adding a navigation element to a paywall unlocks multi-page experiences with branching, conditional routing, and more. If you're building something like onboarding or a cancellation survey, check out the [Flows docs](/docs/dashboard/dashboard-creating-flows/getting-started).

### Adding a navigation component

The navigation component was built to make paging, or navigating through paywall content, easy. To use the navigation component:

1. In the left sidebar, click **+** to add a new element.
2. Choose **Navigation** under the "Base Elements" header.

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-nav-element.png)

You'll see the navigation component in the element hierarchy. **In most cases, you'll want a navigation's width to be 100% of the viewport**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-nav-width.png)

From there, add in content to create pages using [stacks](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-stacks):

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-nav-stacks.png)

Similar to the parent navigation element, it helps to have the width of your stacks be 100% of the parent.

### Changing pages

When a navigation element is added, Superwall automatically creates an element variable for it (accessed through the **[Variables](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-variables)** tab in the left sidebar, or the variables button in the **[floating toolbar](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-floating-toolbar)**). Its name will match whatever is in the element hierarchy in the left sidebar:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-nav-vars.png)

Each top-level child within the navigation component represents a *current index* value, starting from 0. Changing this value will change which page is displayed. In this example, we add a [tap behavior](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements#tap-behaviors) to the button, which increments the element variable's `current index` value:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-nav-toggle-page.gif)

> **Note:** The variable's name is derived by the node's unique identifier. You don't need to set or generally be aware of this value.

### Editing transitions

A navigation component has four different transitions to use. Edit them by **clicking** on the navigation component from the left sidebar, and then selecting a value in the trailing sidebar:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-nav-transition.png)

Available transitions are:

1. **No Transition:** No animation will occur during page changes.
2. **Push:** Each page is pushed on or off of the next page, similar to navigation stacks in iOS.
3. **Fade:** Each page change results in an opacity fade in or out.
4. **Slide:** Similar to push, but the animation results in a smooth transition between pages, much like scrolling through a carousel would look.