# 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

# Superwall Agents

Use Superwall Agents to analyze experiments, inspect your setup, automate reports, and turn Superwall data into growth work.

Superwall Agents gives you an AI workspace for the growth work that usually takes the most digging: reading experiment results, finding patterns in your data, checking implementation details, and turning what it finds into the next thing to try.

Use Superwall Agents from [superwall.ai](https://superwall.ai). Log in with your existing Superwall account to access all of your organizations and apps.

<img src="/docs/images/agents-overview.png" alt="A Superwall Agents workspace showing a chat analyzing experiment results, a chart, and suggested next experiments" />

### What you can do

* **Analyze experiment results**: Ask what changed, which variant is winning, what segments are driving the result, and what the next test should be when your connected Superwall tooling exposes that data.
* **Turn analysis into action**: Ask for concrete experiment ideas, paywall changes, campaign adjustments, or implementation checks.
* **Inspect available code**: Connect GitHub, upload files, or clone a repo onto the hosted machine, then ask the agent to read files, run commands, and help debug SDK integration issues.
* **Automate recurring work**: Schedule a prompt for a chat, such as a weekly experiment readout or a daily anomaly check.
* **Connect external systems**: Use webhooks to trigger a chat from another service, and send chat events back to your own tooling.
* **Generate artifacts**: Create charts, summaries, files, and reports that can be shared with your team.

### Start here

1. **[Workspace tour](/docs/agents/workspace-tour):** Learn what the sidebar, composer, selectors, integrations, suggested prompts, and selected UI states do.
2. **[Create an agent chat](/docs/agents/create-an-agent):** Start a focused chat, attach context, review generated artifacts, steer running work, and share useful conversations.

### Using agents

3. **[Automation](/docs/agents/automations):** Schedule recurring prompts for reports, monitoring, experiment review, and other work that should happen on a cadence.
4. **[Webhooks](/docs/agents/webhooks):** Trigger chats from external systems and send chat events back to your own tooling.
5. **[Sharing Chats](/docs/agents/sharing-chats):** Share a completed conversation with teammates and manage the shared link.
6. **[Integrations](/docs/agents/integrations):** Connect GitHub, Slack, skills, web search, models, and hosted machine environment variables.
7. **[Files](/docs/agents/files):** Browse files available on the active hosted machine, open generated reports, and inspect uploaded or cloned context.
8. **[Terminal](/docs/agents/terminal):** Run commands on the same hosted machine the agent can use.
9. **[Settings](/docs/agents/settings):** Configure defaults, environment variables, machines, usage, billing, webhooks, keybindings, and account controls.

### Misc

10. **[Billing and usage](/docs/agents/billing-and-usage):** Review usage, understand how work is counted, and manage the subscription attached to your account.
11. **[Troubleshooting](/docs/agents/troubleshooting):** Resolve common setup, machine, integration, file, webhook, billing, and chat issues.
12. **[Recipes](/docs/agents/recipes):** Try prompts for experiment analysis, campaign review, implementation checks, recurring reports, and follow-up ideas.