# 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 Skill Give AI coding agents up-to-date Superwall docs, API access, and step-by-step SDK integration guides using the Superwall Skill. The [Superwall Skill](https://github.com/superwall/skills) is a set of [Agent Skills](https://agentskills.io) that give AI coding agents everything they need to work with Superwall. It has access to live documentation, API access, dashboard information, and guided SDK integration flows for every platform. > **Note:** This is different from [Superwall Agents](/docs/agents), which is the Superwall AI workspace for chats, analysis, automations, webhooks, and hosted machine work. The Superwall Skill is for giving AI coding agents Superwall docs, API access, and SDK guidance. The Skill can perform all of the tasks the [Superwall MCP](/docs/dashboard/guides/superwall-mcp) can, and is recommended when you are working in an external coding agent. > **Tip:** The Skill can also connect to a live paywall editor session. Open **AI Chat** in the paywall editor, expand the agent connection panel, choose **Skill**, install the Skill if needed, then paste the pairing-code prompt into your agent. See [Editor MCP](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-mcp) for the full flow. ## Installation Install with the [skills.sh](https://skills.sh) CLI. This works with any agent that supports skills, including Claude Code, Cursor, and Codex. Install all skills (recommended): ```bash npx skills add superwall/skills ``` Or install individual skills: ```bash # General skill (docs, API, dashboard links) npx skills add superwall/skills --skill superwall # Platform-specific quickstart npx skills add superwall/skills --skill superwall-ios-quickstart npx skills add superwall/skills --skill superwall-android-quickstart npx skills add superwall/skills --skill superwall-flutter-quickstart npx skills add superwall/skills --skill superwall-expo-quickstart ``` ## What's included The Superwall Skill is made up of a general-purpose skill and platform-specific quickstart skills. ### General skill The `superwall` skill gives agents access to: * **Live documentation**: Agents fetch docs on demand from `llms.txt` and per-page markdown endpoints, so they always have the latest information. * **API access**: A bundled `sw-api.sh` helper wraps the Superwall V2 API. Agents can list projects, inspect applications, and manage resources directly from the terminal. * **Dashboard links**: URL patterns for every dashboard page, so agents can link you to the right place (settings, campaigns, paywalls, users, and more). * **SDK source cloning**: Agents can clone SDK repos locally to trace internal behavior when debugging. * **Webhook and integration catalog**: Fetched live from the Superwall integrations endpoint. * **Editor pairing**: Agents can attach to the paywall currently open in the editor when you provide the pairing code from the editor's agent connection panel. ### Platform quickstart skills Each quickstart skill walks the agent through a full SDK integration, step by step: | Skill | Platform | | ------------------------------ | ------------------------- | | `superwall-ios-quickstart` | iOS (Swift / Objective-C) | | `superwall-android-quickstart` | Android (Kotlin / Java) | | `superwall-flutter-quickstart` | Flutter | | `superwall-expo-quickstart` | Expo | Every quickstart follows the same flow: 1. **Install**: Installs the SDK dependency. 2. **Configure**: Ensures Superwall is ready at app launch. 3. **User management**: Identify users on sign-in, reset on logout. 4. **Feature gating**: Register placements and present paywalls. 5. **Subscription tracking**: Observe subscription status changes. 6. **User properties**: Set custom attributes for audience targeting. 7. **Paywall previews**: Sset up deep links for on-device previews. The agent reads bundled reference docs for each step, inspects your project, and implements minimal, production-safe changes before moving on to the next step. ## API access The general skill includes a bash helper (`sw-api.sh`) that wraps the Superwall REST API V2. It requires a `SUPERWALL_API_KEY` environment variable. That's an org-scoped bearer token you can generate from [API Keys settings](https://superwall.com/select-application?pathname=/applications/\:app/settings/api-keys). ```bash # List all available API routes (no API key needed) sw-api.sh --help # Show the full spec for a specific route sw-api.sh --help /v2/projects # List all projects sw-api.sh /v2/projects # Get a specific project sw-api.sh /v2/projects/{id} # Create a project sw-api.sh -m POST -d '{"name":"My Project"}' /v2/projects ``` The `--help` flag fetches the live OpenAPI spec, so the route reference is always current. ### Data hierarchy Superwall organizes data as **Organization → Projects → Applications**. Each application has a `platform` (ios, android, flutter, react\_native, web), a `bundle_id`, and a `public_api_key` used for SDK initialization. The org-scoped `SUPERWALL_API_KEY` is separate, it's used for API calls. ## Quick start Ask your AI agent to integrate Superwall into your app. The agent will: 1. Detect your platform from the project structure (e.g., `Package.swift` → iOS, `pubspec.yaml` → Flutter). 2. Determine your purchase controller path, whether you're using Superwall's default purchase handling, RevenueCat, or a custom setup. 3. Walk through the quickstart steps, implementing each one in your codebase. If you've installed the general skill with an API key, the agent can also look up your projects and applications to find the right `public_api_key` for SDK configuration. ## Related * [Superwall Agents](/docs/agents): For experiment analysis with connected Superwall tooling, automations, webhooks, and hosted machines. * [Superwall MCP](/docs/dashboard/guides/superwall-mcp): For managing your Superwall account from AI tools. * [Editor MCP](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-mcp): For connecting external agents to the paywall currently open in the editor. * [AI Chat Builder](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-ai-chat): For using Superwall's built-in editor chat to build and refine paywalls. * [Vibe Coding](/docs/sdk/guides/vibe-coding): All the AI tools available for working with Superwall listed in one place.