# 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

# Feature gating

Run code only when a user is entitled to it.

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

## The feature callback

Wrap the code you are gating in `feature` and the SDK decides whether it runs.

```ts
await sw.register({
  placement: "export_report",
  feature: () => downloadReport(),
});
```

The callback runs when:

* The user is already entitled, so no paywall is shown.
* The user purchased or restored on the paywall.
* The paywall was non-gated and the user dismissed it without buying.
* The placement was skipped: not found, no audience match, or holdout.

It does not run when a gated paywall is dismissed without a purchase.

> **Warning:** **A skipped placement still runs your feature.** If the placement name does not exist in any campaign, or the user matches no audience rule, the SDK runs `feature` and returns `{ type: "skipped" }`. A typo in a placement name grants the feature. This matches the iOS and Android SDKs. To check whether someone has paid, read entitlements and enforce on [your server](/docs/web/guides/server-side-gating).

> **Tip:** Gated versus non-gated is set on the paywall in the dashboard, not passed from code.

## Branching yourself

To decide in your own code, read the result instead.

```ts
const result = await sw.register({ placement: "export_report" });

switch (result.type) {
  case "presented":
    if (result.result.type === "purchased") unlock();
    break;
  case "skipped":
    console.log("no paywall shown:", result.reason);
    break;
  case "error":
    console.error(result.error);
    break;
}
```

## Checking entitlements directly

To read entitlement state without triggering a placement, use the entitlements namespace.

```ts
sw.entitlements.active.value;   // Entitlement[]
sw.entitlements.inactive.value;
sw.entitlements.all.value;

sw.entitlements.byProductIds(["pro_monthly"]);
```

These are reactive. Subscribe to re-render when they change:

```ts
const unsubscribe = sw.entitlements.active.subscribe((active) => {
  render({ isPro: active.some((e) => e.id === "pro") });
});
```

## Enforcement

> **Warning:** These checks control UI only. Local subscription state can be edited from DevTools. Enforce access to paid resources on your server with [`@superwall/server` or `@superwall/verify`](/docs/web/guides/server-side-gating).

Next, [track subscription state](/docs/web/quickstart/tracking-subscription-state).