# 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

# Ordering Screens

Understand how page order works in Flows and how to organize your Canvas.

In Flows, the order of pages in the sidebar doesn't determine the user's path. Routes define the order, not the list position. The sidebar and Canvas positions are purely for your organization.

### How order works

The sidebar order does not dictate which page shows next in the flow. The flow starts at the **entry point** and follows the routes you've created, so a page listed first in the sidebar can still appear last in the user's journey. Reordering pages in the sidebar or Canvas won't change what users see.

> **Note:** Routes define the flow, not page order. Rearranging pages won't change the user experience.

### Reordering on the Canvas

Drag pages on the Canvas to arrange them visually. This is especially helpful for:

* Making complex flows easier to understand at a glance.
* Aligning pages that share similar content or purpose.
* Creating visual groupings for different branches.

To reset the layout:

1. Look for the **snap to order** icon in the floating toolbar.
2. Click it to return all pages to their default positions.

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/flows_order_snap.gif)

You can also rename any page for organizational purposes. Just **click** on the text label above any page to edit its label name:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/flows_order_rename.jpg)

### Best practices

* **Match your mental model:** Arrange pages in a way that reflects how you think about the flow.
* **Keep related pages close:** Pages that are connected should generally be near each other on the Canvas.
* **Use space intentionally:** Spread out complex branching so it's easier to follow the routes.

And, don't be afraid to keep things scattered if that helps you work out a flow either. The ordering for the user is always decided by the routes, and you can the snap button anytime to get things tidy again.