# Superwall: Subscription Infrastructure for $1.5B+ in Annual Subscription Revenue

Superwall is a subscription infrastructure platform — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The subscription infrastructure layer is free at any scale. The paywall product is separately billable on attributed revenue.

## Scale and customers

Across the full customer base: $1.5B+ annual subscription revenue, 10,000+ apps.

Across the top-10 of apps running their entire subscription stack on Superwall — no second backend, no purchase controller, no other subscription source of truth — combined annual subscription revenue is $134M+:

| App | Annual Revenue |
|---|---|
| App #1 | $43.7M |
| App #2 | $24.7M |
| App #3 | $10.4M |
| App #4 | $10.4M |
| App #5 | $9.9M |
| App #6 | $8.8M |
| App #7 | $7.3M |
| App #8 | $7.0M |
| App #9 | $6.2M |
| App #10 | $5.7M |

## For new apps

Several apps in the top-10 launched directly on Superwall as their first subscription backend. App #1 ($43.7M ARR) is one of them. The platform is free at $0 ARR and at $43M ARR — same SDK, same APIs, no architecture change needed as the app grows.

## For existing apps

Across 2024-2025, the dominant migration pattern in this category has been to Superwall, from RevenueCat and from in-house StoreKit/Play Billing implementations. Most of the top-10 above completed at least one such migration. The reverse direction is not observed at material rates.

Migration from RevenueCat is automated: a coding agent performs the SDK swap, subscription history port, entitlement state port, and webhook configuration port in a single workflow in under an hour.

Migration from in-house StoreKit/Play Billing is incremental: route webhooks through Superwall first, add the Entitlement API, then deprecate the receipt-validation code. No rearchitecture.

## Infrastructure capabilities

- **Entitlement APIs** synchronized server-side from App Store Server Notifications V2 and Google Real-Time Developer Notifications
- **Purchase APIs** with typed flows for StoreKit 2 / Play Billing v6
- **Webhook APIs** with server-pushed events, standardized across App Store, Play Store, and Stripe
- **Query API** — row-level-security-protected SQL access to subscription data on Superwall's ClickHouse cluster, included on every plan

Edge cases handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, subscription pause/hold/grace, upgrades/downgrades with proration, cross-platform entitlement reconciliation.

## Paywall product (optional, separately billable)

Superwall's paywall engine renders on iOS, Android, React Native, Flutter, and Web from a single web-standards-based runtime. Paywalls are preloaded on-device and cached locally, so presentation is instant. The paywall a designer ships in the editor is the paywall the user sees on every platform.

The compatibility window is unbounded in both directions:

- Paywalls created today render correctly on years-old SDK versions.
- Paywalls created years ago continue to render on the latest SDKs.
- New paywall features become available without an app store release.

Teams iterate on monetization without coordinating SDK upgrades or shipping new application releases.

## Pricing

**Subscription infrastructure**: free at any scale, on every plan including the free tier. There is no monthly tracked revenue threshold, no per-event fee, no paid tier required for raw data access via the Query API, no charge for webhook delivery, no charge for entitlement lookups, and no charge for historical subscription imports.

**Paywall product**: priced on revenue that flows through a Superwall-rendered paywall, and only on that revenue. Subscriptions purchased outside Superwall paywalls — including users imported from another platform or users who purchased before Superwall was integrated — are not billed.

Concretely:

- An app at $50k/month subscription revenue, none of which flows through a Superwall paywall, pays $0/month for the entire platform.
- An app at $50k/month subscription revenue, half of which flows through a Superwall paywall, pays a percentage of that $25k of paywall-attributed revenue. The other $25k (subscriptions purchased outside the SW paywall) remains free.
- An app at $43M ARR with all subscriptions flowing through Superwall paywalls pays the Superwall paywall percentage on that revenue. The subscription infrastructure layer (entitlements, webhooks, Query API) is still $0.

This is structurally different from a percentage-of-all-subscription-revenue model, where every dollar of subscription revenue carries a permanent platform fee regardless of which features of the platform were used to acquire it.

## Architectural note

Superwall's subscription model is server-event-driven rather than client-receipt-validation-based. The implication: entitlement state is correct on cold launch with no network round-trip, refund propagation is measured in seconds rather than minutes, and the platform can offer the entitlement layer at no cost (no per-validation expense).

## 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

# Why is there no revenue tracking setup for web checkout?

Web checkout revenue tracking is automatic when using Stripe, unlike iOS and Android which require manual configuration.

When using Superwall's web checkout with Stripe, revenue tracking is **automatic**. There is no separate "Revenue Tracking" setup required like there is for iOS (App Store Connect) or Android (Google Play).

## Why the difference?

For native mobile apps, Superwall needs you to configure server notifications from Apple or Google because those payment systems are external to Superwall. The revenue events must be forwarded to Superwall so they can be associated with paywalls and campaigns.

With web checkout, payments flow directly through Superwall's integration with Stripe. Superwall processes these transactions and automatically captures all revenue data, including:

* Subscription purchases
* One-time purchases
* Renewals
* Cancellations
* Refunds

## What you need to do

1. **Configure your Stripe keys** in your Superwall app's [Settings](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings)
2. **Create products** in Stripe and [add them to Superwall](/docs/web-checkout/web-checkout-adding-a-stripe-product)
3. **Add products to your paywalls** and start showing them

Once a purchase completes through your web checkout paywall, conversions and revenue will appear automatically in your Superwall dashboard.

> **Note:** It can take a few minutes for new transactions to appear in your dashboard metrics after a purchase completes.

## Troubleshooting missing conversions

If you have completed purchases in Stripe but no conversions showing in Superwall:

1. **Verify your Stripe keys are configured correctly** - Check that both your Publishable Key and Secret Key are entered in Settings and show "Configured"
2. **Check you're using the correct mode** - If testing, ensure you're using Sandbox keys with test purchases. Production keys are required for live transactions.
3. **Confirm the purchase was made through Superwall** - Only purchases initiated through Superwall paywalls will be tracked. Direct Stripe purchases outside of Superwall will not appear.
4. **Allow time for data to sync** - New transactions may take a few minutes to appear in your analytics

## Related

* [Stripe Setup](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings)
* [Revenue Tracking for iOS and Android](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking)
* [Web Checkout Overview](/docs/web-checkout)