# 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 # Settings Configure Superwall Agents defaults, environment variables, machines, usage, billing, webhooks, keybindings, and account actions. Open **Settings** from the bottom of the sidebar. Settings is where you configure defaults and account-level behavior after the basic chat workflow is working. The Settings page showing the settings tabs for General, Environment, Machine, Usage, Billing, Webhooks, Keybindings, and Account ### General Use **General** for app-level defaults. * **Theme**: Choose light, dark, or system appearance. * **Agent Defaults model selector**: Sets the default model for new chats. * **Agent Defaults reasoning selector**: Sets the default reasoning effort for new chats. * **Stream Responses switch**: Shows assistant text as it is generated. When disabled, responses appear after the turn finishes. Changing a default does not rewrite old messages. It affects new chats and future turns that inherit the default. ### Environment The Settings Environment page for adding and saving environment variables Use **Environment** for variables that tools on the hosted machine can read. * **Variable name field**: Enter a shell-safe variable name such as `OPENROUTER_API_KEY`. * **Value field**: Enter the value to make available to new agent turns. * **Remove variable**: Deletes that variable row. * **Add Variable**: Adds another name/value row. * **Save**: Persists unsaved environment changes. Some integration variables are reserved. `SUPERWALL_API_KEY` comes from the organization selector. `GH_TOKEN`, `GITHUB_TOKEN`, and `SLACK_BOT_TOKEN` come from the GitHub and Slack connection flows. > **Note:** **Need a Superwall API key?** In Superwall Agents, select your organization in > the chat header. Agents provides a managed organization API key to new turns, > so you usually do not add `SUPERWALL_API_KEY` here. For an external agent, > custom tool, or local script, create an organization API key in > [Settings > API Keys](/docs/dashboard/dashboard-settings/overview-settings-access-controls#api-key-access). > Do not use the public `pk_` SDK key for server or API access. > **Warning:** Do not paste secret values into chat. Store them in Environment so tools can > use them without adding the secret to conversation history. ### Machine The Settings Machine page for managing hosted machines Use **Machine** to manage the hosted machine where agent tools run. * **Add Machine**: Creates a hosted machine. * **Activate machine**: Makes a machine active for chat, Files, Terminal, automations, and webhooks. * **Current machine**: Indicates the active hosted machine. * **Rename**: Renames a hosted machine. * **Reconnect**: Reconnects the active machine. * **Update**: Updates the active hosted machine when available. * **Delete**: Deletes a hosted machine. The hosted machine has its own filesystem and environment. To work with code or private files, connect GitHub, clone a repo from Terminal, upload files in chat, or add the needed environment variables before asking the agent to use them. ### Usage The Settings Usage page showing recent Superwall Agents usage Use **Usage** to understand recent usage. * **Series chips**: Toggle individual usage series on or off in the chart. * **Usage chart**: Shows usage over the last 30 days. * **Totals table**: Shows last-30-days totals by series. Usage updates periodically, so treat it as operational visibility rather than a real-time meter. ### Billing The Settings Billing page for managing the Superwall Agents subscription Use **Billing** to manage the Superwall Agents subscription. * **Manage**: Opens the billing portal. * **Subscribe**: Starts subscription checkout. * **Subscribed**: Indicates the subscription is already active. See [Billing and Usage](/docs/agents/billing-and-usage) for more detail. ### Webhooks The Settings Webhooks page showing existing webhook configurations Use **Webhooks** to connect chats with external systems. See [Webhooks](/docs/agents/webhooks) for payload examples and more. ### Keybindings The Settings Keybindings page for customizing Superwall Agents shortcuts Use **Keybindings** to customize global app shortcuts. Keybindings are stored in the active keybindings file shown by the hosted machine. ### Account The Settings Account page showing signed-in account details and account actions Use **Account** for browser-session and account actions. * **Signed In**: Shows the current browser session email. * **Name**: Shows the signed-in user and authorization scope. * **Delete**: Deletes Superwall AI account data for the current browser session, including hosted machine records and sandboxes, hosted chats and files, Superwall organization selection, GitHub and Slack integrations, shared chat data, process history, and the current auth session. * **Sign out**: Ends the current hosted frontend browser session. > **Warning:** Deleting an account is destructive. Managed provider keys and Superwall > organization API keys are preserved.