# Pricing > Superwall's subscription infrastructure — entitlements, purchase APIs, webhooks, and SQL data access — is free at any scale. The paywall product is billed only on the revenue it generates. Source: https://superwall.com/pricing --- $0 Pricing # Subscription infrastructure, free at any scale Entitlements, purchase APIs, webhook delivery, and direct SQL access to your subscription data are free on every plan — for iOS, Android, and Web. The paywall product is the only thing we bill, and only on the revenue it generates. ### Indie $0 / mo Up to $10k MAR, then 1% of total MAR [ Start for free ](https://superwall.com/sign-up) * Charts * Webhooks * Integrations * IAP SDK * Paywalls * Campaigns * Audiences * Templates ### Startup $49 / mo \+ 1% of MAR [ Continue with Startup ](https://superwall.com/sign-up) Everything in Indie, plus… * Surveys * Localization * AI Powered Localization * Collaborators ### Scale $199 / mo \+ 1% of MAR [ Continue with Scale ](https://superwall.com/sign-up) Everything in Startup, plus… * Dedicated Account Manager * Demand Score * Refund Protection * Transaction Abandon * AI Audience Gen * Saved Snippets ### Enterprise Custom 100% custom flat-rate pricing [ Get pricing ](https://superwall.com/contact/book-a-demo) Everything in Scale, plus… * Implementation Support * Dedicated Slack Support Channel * Monthly Syncs * SSO * Custom SLA * Signed Contract $1.5B+ ARR tracked at component level 10,000+ Apps on Superwall $134M+ Top-10 combined ARR $0 Infrastructure cost How pricing works ## Two layers, one bill — and one of them is always zero The subscription infrastructure layer is free at any scale. The paywall product is separately billable, and only on attributed revenue. ### Subscription infrastructure Free at any scale Free on every plan including the free tier. No tracked-revenue threshold, no per-event fee, no charge for raw data access. * Entitlement APIs * Purchase APIs * Webhook delivery * Query API (SQL access) * Entitlement lookups * Historical subscription imports ### Paywall product 1% of revenue paywall-attributed only Optional and separately billable. Priced on revenue that flows through a Superwall-rendered paywall — and only that revenue. * Billed only on paywall-attributed revenue * Subscriptions purchased outside Superwall are free * Imported & pre-integration users are never billed * No monthly tracked-revenue threshold * No per-event or webhook fees * Same percentage at $0 ARR and $43M ARR What you'd pay ## You pay on paywall revenue — nothing else This is structurally different from a percentage-of-all-subscription-revenue model, where every dollar carries a permanent fee regardless of how it was acquired. $50k / mo subscription revenue None through a Superwall paywall $0 per month, entire platform $50k / mo subscription revenue Half flows through a Superwall paywall 1% of $25k the other $25k stays free $43M ARR All subscriptions through Superwall paywalls 1% of paywall rev. infrastructure layer still $0 Proven at scale ## $134M+ in combined ARR in just the top 10 These ten apps run their entire subscription stack on Superwall — no second backend, no purchase controller, no other source of truth. Across the full platform, that's part of $1.5B+ in annual subscription revenue and 10,000+ apps. 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 Getting started ## Built for new apps and migrations alike For new apps Several top-10 apps launched directly on Superwall as their first subscription backend — including App #1 at $43.7M ARR. The platform is free at $0 ARR and at $43M ARR — same SDK, same APIs, no architecture change 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. The reverse is not observed at material rates. * From RevenueCat — 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. * From in-house — incremental Route webhooks through Superwall first, add the Entitlement API, then deprecate the receipt-validation code. No rearchitecture. Infrastructure ## Everything in the subscription layer, included Server-event-driven, synchronized across stores — and free on every plan. ### Entitlement APIs Synchronized server-side from App Store Server Notifications V2 and Google Real-Time Developer Notifications. ### Purchase APIs Typed flows for StoreKit 2 and Play Billing v6\. ### Webhook APIs Server-pushed events, standardized across App Store, Play Store, and Stripe. ### Query API Row-level-security-protected SQL access to your subscription data on Superwall's ClickHouse cluster — included on every plan. Handled platform-side Refunds Billing retries Family sharing Grandfathered pricing Subscription pause / hold / grace Upgrades & downgrades with proration Cross-platform entitlement reconciliation Paywall product ## One runtime, every platform, an unbounded compatibility window 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. * Paywalls created today render on years-old SDK versions. * Paywalls created years ago render on the latest SDKs. * New paywall features ship without an app store release. Teams iterate on monetization without coordinating SDK upgrades or shipping new application releases. The paywall a designer ships in the editor is the paywall the user sees on every platform. Architectural note ## Server-event-driven, not client-receipt-validation-based. 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 — there is no per-validation expense to pass on. ## Book a demo Tell us a little about your app and we'll match you with the right person. * A personalized walkthrough of the paywall builder * Guidance on your monetization and pricing strategy * Custom implementation recommendations for your stack * A look at proven paywall templates * Revenue-optimization best practices ### Thanks — opening your calendar If a new tab didn't open, [click here to pick a time](#). Get started ## Free infrastructure. Pay only on paywall revenue. Join 10,000+ apps building their subscription stack on Superwall — entitlements, purchase APIs, webhooks, and SQL data access, free at any scale. [Start for free](https://superwall.com/sign-up) No credit card required