# 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

# Stacks

From a component standpoint, stacks are the foundation of every layout. Most components and snippets will start with a stack. Under the hood, they mimic a flexbox layout.

> **Tip:** If you are new to CSS Flexbox, try out this interactive [tool](https://flexbox.help). Or, simply change the properties in the editor to see realtime changes.

### Stack Specific Properties

Stacks have unique properties:

![](https://json-ld-superwall-docs-staging.staffbar.workers.dev/docs/images/pweditor_stacks_1.png)

* **Axis**: Determines the arrangement of items within the stack.
  1. `Horizontal`: Items are arranged left to right.
  2. `Vertical`: Items are arranged top to bottom.
  3. `Layered`: Items are stacked on top of each other.

* **Vertical**: Controls the vertical alignment of the items within the stack.
  1. `Top`: Aligns items to the top of the container.
  2. `Center`: Aligns items vertically in the center of the container.
  3. `Bottom`: Aligns items to the bottom of the container.
  4. `Stretch`: Stretches items to fill the vertical space of the container.
  5. `Baseline`: Aligns items according to their baseline.

* **Horizontal**: Controls the horizontal alignment of the items within the stack.
  1. `Left`: Aligns items to the left of the container.
  2. `Center`: Aligns items horizontally in the center of the container.
  3. `Right`: Aligns items to the right of the container.
  4. `Fill Equally`: Distributes items evenly across the container, filling the space equally.
  5. `Space Evenly`: Distributes items with equal space around them.
  6. `Space Around`: Distributes items with space around them, with half-size space on the edges.
  7. `Space Between`: Distributes items with space only between them, with no space at the edges.

* **Spacing**: Defines the amount of space between items within the stack, measured in pixels by default.

* **Wrap**: Specifies how items within the stack should behave when they exceed the container's width.
  1. `Don't Wrap`: Items remain in a single line and do not wrap onto a new line.
  2. `Wrap`: Items wrap onto the next line when they exceed the container's width.
  3. `Wrap Reverse`: Items wrap onto the previous line in reverse order.

* **Scroll**: Determines the scrolling behavior of the stack.
  1. `None`: Disables scrolling within the stack.
  2. `Normal`: Enables standard scrolling behavior.
  3. `Paging`: Enables paginated scrolling, allowing users to swipe through pages of items. See "Creating Carousels" below.
  4. `Infinite`: Endless scrolling, items clone and repeat themselves once they reach the end.

* **Snap Position**: Defines the position at which items snap into place during paging. Only relevant if `Scroll` is set to `Paging`.
  1. `Start`: Items snap to the start of the container.
  2. `Center`: Items snap to the center of the container.
  3. `End`: Items snap to the end of the container.

* **Auto Paging**: Controls whether a carousel's contents should automatically page between items. Only relevant if `Scroll` is set to `Paging`.
  1. `Disabled`: Auto paging is turned off, and items page via user interaction.
  2. `Enabled`: Auto paging is turned on and items will automatically page according to the paging delay.

* **Paging Delay**: The duration to automatically advance the slides. Only relevant if `Scroll` is set to `Paging` and `Auto Paging` is set to `Enabled`.

* **Infinite Scroll Speed**: The amount of pixels per frame that the carousel should advance. Only relevant if `Scroll` is set to `Infinite`.

To see how to use stacks for common designs, check out these pages:

* [Carousel](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-carousel-component)
* [Autoscrolling](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-autoscroll-component)
* [Slides](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-slides-component)
* [Navigation](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-navigation-component)