# 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

# Connect an Agent with MCP

Connect Claude Code, Codex, Cursor, or another MCP-compatible agent to the paywall currently open in the Superwall editor.

Editor MCP lets an external AI agent control the paywall currently open in your browser. Use it when you want to keep working in Claude Code, Codex, Cursor, or another MCP-compatible agent while giving that agent live access to the editor.

![Editor MCP connection panel showing install options and a pairing code](https://superwall.com/docs/images/paywall-editor-agent-connect.jpg)

> **Note:** Editor MCP is different from the [Superwall MCP](/docs/dashboard/guides/superwall-mcp). The Superwall MCP manages account resources such as projects, applications, campaigns, products, and paywalls. Editor MCP controls the one paywall editor session open in your browser.

## Connect an agent

1. Open the paywall you want the agent to edit.
2. Open **AI Chat** in the editor sidebar.
3. Click the agent connection pill.
4. Choose **Skill** or **MCP**.
5. Copy the install command shown in the editor.
6. Paste the pairing prompt into your agent.

If you choose **Skill**, the editor shows:

```bash
npx skills add superwall/skills
```

Then paste the generated prompt into your agent:

```txt
Connect to the Superwall editor using the skill with pairing code: XXXX-XXXX-XXXX
```

If you choose **MCP**, select your client first. The editor generates the right command or configuration for Claude Code, Codex, Cursor, or another MCP client. Use the command shown in the editor because it includes the correct Editor MCP URL for your environment.

The MCP prompt looks like this:

```txt
Connect to the superwall-editor MCP with pairing code: XXXX-XXXX-XXXX
```

## Connected state

After the agent attaches, the connection pill shows the connected client and tool activity.

For example, this is what it looks like when an agent uses the pairing code to connect to the editor:

![Example agent connecting to the Superwall editor over MCP](https://superwall.com/docs/images/ai_mcp_claude_connecting.jpg)

After the connection completes, the editor shows the attached client and recent tool activity.

![Editor MCP connection panel showing a connected agent and tool activity](https://superwall.com/docs/images/paywall-editor-agent-connected.jpg)

The editor keeps the browser session open while the page is open. From the connection panel you can:

* **Disconnect Agent:** Release the current agent while keeping the editor session available for another pairing.
* **End Session:** Close the browser editor session and invalidate the pairing code.

Only one external controller can be attached to an editor session at a time. Disconnect the current agent before attaching a different one.

## What agents can do

Attached agents receive the editor's live tool list. The exact list can change as the editor evolves, but today agents can:

* **Inspect and edit the paywall:** Agents can read the current paywall, selected elements, children, navigation pages, computed styles, and screenshots. They can then update text, styles, names, node order, hierarchy, or write native paywall HTML directly into the editor.
* **Work with content and resources:** Agents can upload image and video assets, create and edit products, manage style tokens, and update variables, variable values, and dynamic values. They can also add localization languages, run AI localization, and configure trial-started notifications.
* **Configure behavior and advanced flows:** Agents can add or clear tap behaviors such as purchase, restore, close, open URL, set state, select product, navigate page, request permission, request callback, scroll, focus input, delay, animation, and haptics. They can also edit routes, transitions, branches, advanced native elements, and use search or find/replace to make broader changes.

## Session limits

Editor MCP uses pairing codes and session tokens rather than your account-level MCP OAuth flow.

| Limit                   | Behavior                                                                               |
| ----------------------- | -------------------------------------------------------------------------------------- |
| Pairing code lifetime   | Pairing codes expire after 10 minutes.                                                 |
| Editor session lifetime | Browser editor sessions expire after 24 hours.                                         |
| Tool timeout            | Tool calls time out after 30 seconds.                                                  |
| Browser reconnect       | The browser has a short reconnect window if the page refreshes or briefly disconnects. |
| Failed pair attempts    | Too many wrong pairing codes end the session.                                          |

If a pairing code expires, open the connection panel again and use the new code.

## Troubleshooting

### The agent cannot attach

Check that the paywall editor tab is still open, the pairing code has not expired, and the agent is using the prompt from the current connection panel.

### The session says another controller is connected

Only one controller can be attached. Click **Disconnect Agent**, then attach the new agent with the latest pairing code.

### Tool calls fail after a browser refresh

Wait a moment for the editor to reconnect. If calls still fail, end the session and create a new connection from the editor.

### The agent edited the wrong thing

Use the editor's undo and history tools to review or roll back changes. Select the exact element you want changed before sending the next prompt so the agent receives that selection as context.

## Related

* [AI Chat Builder](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-ai-chat): Use Superwall's built-in chat builder inside the editor.
* [Superwall MCP](/docs/dashboard/guides/superwall-mcp): Manage account resources from external AI tools.
* [Superwall Skill](/docs/dashboard/guides/superwall-skill): Give coding agents Superwall docs, API helpers, and SDK integration guidance.