# 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

# Build a Paywall

Build paywalls with an AI agent using the Superwall Framework, or edit them in the visual editor with AI chat and Editor MCP.

The recommended way to build paywalls with AI is the **Superwall Framework**. Your agent writes the paywall as code in your repo, you preview it in the studio, and you push it to Superwall when it's ready.

## Recommended: the Superwall Framework

With the [Superwall Framework](/docs/framework), a paywall is a small React app that lives in your repo. Agents already know how to write that kind of code, so you can describe a paywall in plain English and have it built for you.

* **Preview everything before it ships.** The [studio](/docs/framework/studio) shows your paywall on iPhone, Android, and iPad, in light and dark mode, in every language, with and without a free trial. You pick what happens on every purchase.
* **Prices come from the store.** Products, prices, and trials come from the App Store, Google Play, or Stripe, so an agent can't hardcode a wrong price.
* **No app update needed.** Pushed paywalls go live on the next app open, and you A/B test them in campaigns like any other paywall.
* **Start from what you have.** An agent can rebuild an existing editor paywall as code, or turn a screen from your app into a paywall.

Pushing a paywall needs Superwall for Agents enabled on each app. To get access, contact [support@superwall.com](mailto\:support@superwall.com).

## Build with an AI agent

/docs/framework/build-with-an-agent

A plain-language guide to building, previewing, and shipping paywalls by chatting with an agent. No code required.

## Framework quickstart

/docs/framework/quickstart

Set up a project, preview your first paywall in the studio, and push it to Superwall.

## Migrate from the editor

/docs/framework/migrate-from-editor

Rebuild a paywall from the visual editor as code and compare the two side by side.

## Framework overview

/docs/framework

How the Framework works and when to use it.

## Other ways to build with AI

| You want to                                                                  | Use                                                                                   |
| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Edit a paywall in the visual editor by chatting                              | [AI Chat Builder](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-ai-chat) |
| Edit the paywall open in the editor from Claude Code, Codex, or Cursor       | [Editor MCP](/docs/agents/editor-mcp)                                                 |
| Create a visual editor paywall from a template without opening the dashboard | The [plugin](/docs/agents/plugins) or [Superwall MCP](/docs/agents/mcp)               |

### In the visual editor

Open a paywall and click **AI Chat** in the editor sidebar. Describe the change, attach reference images if you have them, and the [AI Chat Builder](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-ai-chat) makes draft edits for you to review. There's nothing to set up.

### From your own agent, in the editor

To keep working in Claude Code, Codex, or Cursor, connect your agent to the paywall open in your browser with [Editor MCP](/docs/agents/editor-mcp). Open **AI Chat** in the editor, click the agent connection pill, and follow the pairing steps. Your agent can then edit text, styles, products, variables, tap behaviors, and more while you watch.

### From a template

With the [plugin](/docs/agents/plugins) or [Superwall MCP](/docs/agents/mcp) connected, ask your agent to create a paywall. It can start from a template or from scratch, attach products, and set up a campaign to show it. For example: "Create a paywall from a template for my iOS app with the annual and monthly products, and show it on the `onboarding_complete` placement."