# 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

# Retention Messaging Save Rate

Learn what the Retention Messaging Save Rate chart measures and when to use it.

![Retention Messaging Save Rate chart in the Superwall dashboard, with a dashed tail on the most recent points](https://superwall.com/docs/images/charts/retention-messaging-save-rate.jpg)

## What it shows

Retention Messaging Save Rate shows the percentage of retention messages sent where the
subscriber did not cancel within 24 hours of being shown the message.

The chart reads from [Apple Retention Messaging](/docs/integrations/apple-retention-messaging), so it
only appears for iOS apps. Retention Messages Sent and Saves are reported alongside the rate, so
both sides of the ratio are visible in the chart's table.

## How to use it

Use this chart to see whether your retention messages are holding onto subscribers who reached
the cancellation screen.

Break the chart down by **Retention Message**, **Retention Configuration**, **Response Type**,
**Retention Locale**, **Save Outcome**, or **Product** to compare which messages and rules save the
most subscriptions. Filter by **Retention Message Group** or **Retention Configuration Group** to
narrow the chart to one group.

## Good to know

The most recent points read high and settle downward. A message sent less than 24 hours ago has
not had time to be cancelled against, so it counts as a save until its window closes. Those points
are drawn as a dashed tail.

Totals over a multi-day range are recomputed from summed sends and saves rather than averaged
across days, so a quiet day does not weigh the same as a busy one.

For how sends and saves are counted, see
[Reporting](/docs/integrations/apple-retention-messaging#reporting).