# 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 Control how users move through your flow with forward and backward navigation. Navigation in Flows is handled by the Navigation element and other components you add tap behaviors to (such as CTA buttons). Users move forward along the routes you've defined, or backward through the pages they've already visited. The system is intentionally simple. Complex routing logic lives in the routes, not the buttons. ### The Navigation element The [Navigation element](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-navigation-component) is what enables flow navigation. Add it to any page to unlock forward and backward controls. To add it: 1. In the left sidebar, click **+** to add a new element. 2. Choose **Navigation** under the "Base Elements" header. Without a Navigation element, you have a paywall. With it, you can create a Flow. ### Adding navigation to components Any element can have a [tap behavior](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements#tap-behaviors). Using the "Navigate Page" behavior, you can tell a component to progress the flow forward or backwards: ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_nav_add.jpg) To configure a component to navigate: 1. Select the button element. 2. In the right sidebar, find **Tap Behavior**. 3. Choose **Navigate Page** from the action options. 4. Select **Forward** or **Backward**. To see them in action, change the canvas view to **Device**, and then click on the component to fire off its tap behavior: ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_nav_test.gif) Additionally, you can manually set which page should be navigated to within the floating toolbar using its variable editor: ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_nav_vars.gif) ### Going forward and backward When a user taps **Forward**, they move to the next page based on the route you've connected from the current page. If there's no branching, they go to the single connected page. If there's branching, the route conditions determine which page comes next. When they tap **Back**, they return to the last page they visited in that session. Back navigation follows the user's history; it does not re-evaluate route conditions in reverse. ### Auto-advance timer For pages that don't require user interaction, you can automatically advance to the next page after a set duration. This is useful for animation screens, feature previews, or any page where you want to keep the user moving through the flow without requiring a tap. ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_link_auto_progress.jpg) To set up auto-advance: 1. Select the page you want to auto-advance. 2. Find the **Auto Advance** hour glass button below the page. 3. Enter the duration in seconds. Once configured, the page will automatically navigate forward when the timer completes: ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_link_auto_progress_set.jpg) ### CTA buttons are simple by design Since routes and branches determine where a user ends up, remember that CTA buttons in Flows commonly do one of two things: progress it forward or go backward. You won't set a specific page number on a button in Flows. Instead, you simply move forward or backwards. All conditional logic (which page to show next based on user input or attributes) is defined in the routes, not the buttons. This keeps your flow easier to maintain and reason about. > **Tip:** Think of CTA buttons as "next" and "back". The routes decide where "next" actually goes.