# Superwall: Subscription Infrastructure for iOS, Android, and Web Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue. ## Pricing - **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge. - **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed. Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0. ## Scale $1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow. ## Infrastructure capabilities - **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN - **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows - **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe - **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation. ## Migration Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code). ## Paywall product (optional, separately billable) One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release. ## Architecture Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost. ## 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 # Automation Schedule recurring prompts for experiment analysis, monitoring, reporting, and follow-up work. Automations send a saved prompt to a chat on a schedule. Use them for recurring analysis and operational checks that should happen without someone remembering to ask. **Click** on **+ Create Automation** to get started: The Superwall Agents new automation dialog for scheduling a recurring prompt Set the prompt and schedule, and the agent will run the prompt at that time, and you can visit the results once they do in your chat history. Automations themselves are attached to chats. The scheduled prompt is sent back into that chat, so the result stays with the surrounding context. Some common automation requests might be: * Weekly experiment readout. * Daily campaign anomaly check. * Monday paywall opportunity report. * Trial conversion and billing issue review. * Weekly SDK integration health check. * Webhook delivery summary. * Churn or cancellation timing report. ### Create an automation from chat You can also ask the agent to schedule a recurring prompt: ```text Every Monday at 9 AM America/Chicago, analyze the previous week's experiment results and suggest the next three paywall tests. ``` The agent can configure the chat automation for you when the schedule is clear. ### Write automation prompts carefully Automated prompts should include enough context to run unattended: ```text Analyze the previous 7 days of onboarding campaign performance for the selected Superwall organization. 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. ``` Avoid prompts that depend on follow-up questions: ```text Analyze the experiment we talked about. ``` ### Timezones Automations use the timezone saved with the schedule. If the exact business timezone matters, name it in the prompt and verify it in the automation dialog. ### Limitations Automations run without a person present. During automated turns, the agent cannot use interactive question or form tools. If the agent needs credentials, organization context, files, or a connected integration, configure those before the automation runs. ### Billing Scheduled chats require an active Superwall Agents subscription when they run through the hosted control plane. If billing is required, Superwall Agents will show a billing message instead of running the scheduled turn.