# 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 # Recipes Try prompts for experiment analysis, campaign review, implementation checks, recurring reports, and next-test planning. Recipes are prompts you can use as a starting point. Copy one into Superwall Agents, then swap in your app, campaign, placement, date range, or segment. Good prompts name the business question and the decision you want to make. Ask for the analysis, the evidence, and the next step. ### Experiment analysis Use these when you want to understand what changed and what to test next. ```text Analyze the latest experiment results for our onboarding paywall. Tell me what changed, which variant is winning, which segments look different, and what experiment we should run next. ``` ```text Analyze the latest paywall experiment. Which variant is winning, what segment differences matter, and what should we test next? ``` ```text Compare paywall conversion, trial conversion, and ARPU over the last 30 days by country and demand score bucket. Show charts and call out the biggest opportunities. ``` ### Campaign and placement review Use these when you want to find weak spots in campaign performance. ```text Find campaigns with strong traffic but weak paywall conversion. Group by placement and suggest the highest-leverage changes. ``` ```text Compare trial conversion and ARPU by country over the last 30 days. Show charts and recommend where we should run localized paywall tests. ``` ```text Look at users who saw paywalls multiple times but did not convert. What patterns do they share, and what experiment could address them? ``` ### Implementation checks Use these when your app repo is available and you want the agent to compare implementation details against your Superwall setup. ```text Inspect the iOS repo connected through GitHub and verify that our Superwall SDK integration correctly identifies users, resets on logout, registers placements, and handles subscription status. ``` ```text Inspect the connected iOS repo and verify that the Superwall SDK integration matches our selected application. Check configuration, identify/reset behavior, placement registration, and subscription status handling. ``` ```text Find every placement registered in that repo and compare it to our campaign setup. Call out missing, unused, or inconsistently named placements. ``` ### Recurring reports Use these when the same analysis should happen on a schedule. ```text Every Monday at 9 AM America/Chicago, review the previous week's experiment results and suggest three next tests with expected impact and risks. ``` ```text Analyze the previous 7 days of onboarding campaign performance. Compare paywall conversion, trial conversion, paid conversion, and ARPU to the prior 7 days. Create charts, summarize notable changes, and recommend three experiments for the next week. ``` ### Multi-app or multi-project work If you work across multiple apps or organizations, name the target directly in the prompt. ```text For the Acme Fitness iOS project, analyze onboarding campaign performance for the last 14 days and suggest the next experiment. ```