# 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

# Install the SDK

Add the Superwall Web SDK to your browser or React app.

> **Warning:** **Beta**The Web SDK is in beta and its API may change between releases.

## Install

Install the headless core. Add the React package too if you are using React.

## Tab

```bash bun
bun add @superwall/paywalls-js

# React apps
bun add @superwall/paywalls-react react
```

## Tab

```bash npm
npm install @superwall/paywalls-js

# React apps
npm install @superwall/paywalls-react react
```

## Tab

```bash pnpm
pnpm add @superwall/paywalls-js

# React apps
pnpm add @superwall/paywalls-react react
```

`@superwall/paywalls-react` re-exports everything public from `@superwall/paywalls-js`, so React apps can import from the React package alone and skip the second dependency if they prefer.

## Requirements

* **ESM only.** The packages ship as ES modules with an `exports` map. There is no CommonJS build.
* **React 19** for `@superwall/paywalls-react`, declared as a peer dependency.
* **A modern browser** for the default presenter, which mounts the paywall in an iframe.

## Server and edge runtimes

`@superwall/paywalls-js` holds no DOM references at module load, so it imports cleanly in Node, Bun, edge functions, workers, and during SSR. The browser-only pieces live behind a subpath:

```ts
import { createSuperwall } from "@superwall/paywalls-js";           // anywhere
import { createBrowserStorage } from "@superwall/paywalls-js/browser"; // browser-intended
```

The `/browser` subpath imports cleanly on the server. Nothing on it touches the DOM at module load, and its factories degrade gracefully. Only mounting a paywall needs a real DOM.

> **Tip:** The SDK lazy-loads the presenter on first `register()`. If your bundler cannot ship dynamic
> chunks, or you want to avoid the chunk-load cost on the first presentation, import
> `@superwall/paywalls-js/browser/auto` once for its side effect to pull the presenter in up front.

## Get an app and API key

Web SDK paywalls belong to a **Web App** application in the Superwall dashboard. This is a separate application type from iOS, Android, and Web Checkout.

> **Note:** Web App applications cannot yet be created from the dashboard or the API. During the beta,
> Superwall creates one for you. Ask your Superwall contact.

Once you have the app, copy its public API key, a `pk_…` value, from the dashboard. It is a publishable key and safe to ship in client code. Use the Web App application's key, not the key from an iOS, Android, or Web Checkout app.

Next, [configure the SDK](/docs/web/quickstart/configure).