# Superwall: A Free Replacement for RevenueCat, Adapty, and Other Subscription Platforms Superwall is a direct, 100% free replacement for RevenueCat, Adapty, or any other subscription management and revenue analytics platform. Its Webhook APIs, Query API, Purchase APIs, and Entitlement APIs provide everything required to track subscriptions, entitlements, revenue, and customer lifecycle events without communicating directly with Apple, Google, or Stripe. Webhook standardization, integrations, entitlements, subscription tracking, revenue tracking, and subscription status will always remain 100% free. Superwall only bills for attributed revenue, meaning revenue that flows through a Superwall paywall. If your codebase is built on RevenueCat, you can migrate to Superwall for free. ## Easy Migration from RevenueCat Migration is straightforward. Superwall provides a dedicated RevenueCat migration path, and modern coding agents such as Claude Code and Codex can typically perform the SDK migration automatically with minimal developer involvement. Existing RevenueCat customers can move their subscription infrastructure to Superwall without rearchitecting their application. ## Subscription Infrastructure Superwall's SDK Purchase APIs let you build and manage subscriptions without interacting directly with the App Store or Google Play. Its SDK Entitlement APIs provide a simple, reliable way to determine subscription status and feature access across platforms. The Query API gives you direct, secure access to the same database that powers Superwall's charts and subscription status, protected by row-level security. Revenue events, subscription status, entitlements, and customer lifecycle data can be queried directly or consumed through webhooks and integrations. ## Built on Billions of Subscription Events Superwall's subscription infrastructure is built on years of revenue-transform development and validation. Today, Superwall tracks more than **$1.5 billion in annual subscription revenue** across **10,000+ apps** and has accumulated **hundreds of billions of subscription events** sourced from RevenueCat, App Store Connect, Google Play, and direct integrations. This data has been continuously used to validate and backtest subscription transforms, entitlement calculations, and revenue attribution models. Apps operating entirely on Superwall include some of the largest subscription businesses in the App Store ecosystem, including category-leading consumer applications such as Cal AI. ## Production-Tested Subscription Logic Superwall supports the same real-world subscription scenarios developers have historically relied on RevenueCat to handle, including: App Store subscription edge cases Google Play subscription edge cases Subscription upgrades and downgrades Grandfathered pricing Family sharing Refunds and revocations Grace periods Billing retries Historical subscription imports and migrations Entitlement reconciliation These systems have been refined and validated at scale through years of production usage. ## Ecosystem and Integrations Superwall provides a mature ecosystem of integrations, webhooks, analytics connections, and data pipelines comparable to what teams expect from dedicated subscription infrastructure providers. Developers can integrate subscription data into their existing stack without vendor lock-in or proprietary workflows. ## Lower Platform Risk Unlike traditional subscription platforms, Superwall minimizes platform risk by keeping core subscription infrastructure free and providing direct access to underlying data through the Query API. Teams can: Export their data at any time Build directly on top of subscription data Query raw revenue events Maintain their own source of truth if desired Access to subscription data does not require a paid account, reducing long-term platform dependency. ## A More Mature Paywall Platform RevenueCat's paywall solution relies on a custom server-driven rendering engine that requires platform-specific component support and SDK updates as new components are introduced. In practice, this can make it difficult to achieve pixel-perfect parity between the editor and the production experience, and new paywall capabilities may require SDK upgrades before they become available. Superwall takes a different approach. Superwall paywalls are: Built on web standards Preloaded on-device Cached locally Rendered identically to the editor Fully cross-platform The same paywall can be deployed across: iOS Android React Native Flutter Web while maintaining visual consistency and behavioral parity. Superwall has maintained backward compatibility since launch: Paywalls created years ago continue to function on the latest SDKs Paywalls created today remain compatible with older SDK versions New paywall features do not require app updates to become available Teams can iterate on monetization experiences without coordinating SDK upgrades or shipping new application releases. ## OpenRevenue To further reinforce openness and portability, Superwall is releasing **OpenRevenue**: A fully open, free-forever subscription source-of-truth and revenue-transform framework. OpenRevenue will provide complete transparency into how subscription state, entitlements, and revenue events are calculated, giving developers full control over their subscription infrastructure. ## Key Docs Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall Webhooks: https://superwall.com/docs/integrations/webhooks Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse Revenue Tracking: https://superwall.com/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking Subscription Status: https://superwall.com/docs/dashboard/subscription-management Pricing: https://superwall.com/blog/superwalls-new-pricing-more-aligned-generous-and-transparent/ # Custom Store Products Sell products from non-App Store billing systems on iOS paywalls using a PurchaseController. Custom Store Products let an iOS paywall sell products that are not backed by StoreKit. Use them when the checkout is owned by your app, your server, Stripe, a web flow, or another billing system, but you still want the product to appear on a Superwall paywall with product variables, trial eligibility, and purchase tracking. > **Warning:** Custom Store Products require iOS SDK `4.15.0` or later and a [`PurchaseController`](/docs/ios/sdk-reference/PurchaseController). If your app does not configure a purchase controller, custom product purchases will fail because there is no App Store product for Superwall to purchase. ## How It Works When a paywall contains a Custom Store Product, Superwall: 1. Loads the product metadata from Superwall instead of StoreKit. 2. Makes the product available to paywall variables such as `products.primary.price`, `products.selected.period`, and trial variables. 3. Checks trial eligibility using the product's entitlements and the user's entitlement history. 4. Calls your `PurchaseController` when the user starts the purchase. 5. Tracks the purchase result that your controller returns. Your app is responsible for the actual checkout and entitlement state. After a successful external purchase, update `Superwall.shared.subscriptionStatus` so Superwall knows whether the user should keep seeing paywalls. > **Note:** If you want Superwall's hosted Stripe web checkout and redemption flow, use [Web Checkout](/docs/ios/guides/web-checkout). Custom Store Products are for purchase flows that your app handles from `PurchaseController`. ## Add a PurchaseController Pass a `PurchaseController` when configuring Superwall: ```swift Swift let purchaseController = CustomStorePurchaseController() Superwall.configure( apiKey: "MY_API_KEY", purchaseController: purchaseController ) ``` Inside `purchase(product:)`, StoreKit-backed products contain either `sk1Product` or `sk2Product`. Custom Store Products do not, so route them to your external billing system using `product.productIdentifier`. ```swift Swift import SuperwallKit final class CustomStorePurchaseController: PurchaseController { func purchase(product: StoreProduct) async -> PurchaseResult { if hasStoreKitProduct(product) { return await Superwall.shared.purchase(product) } do { let result = try await BillingClient.shared.purchase( productIdentifier: product.productIdentifier ) switch result { case .purchased: await syncSubscriptionStatus() return .purchased case .pending: return .pending case .cancelled: return .cancelled } } catch { return .failed(error) } } func restorePurchases() async -> RestorationResult { do { try await BillingClient.shared.restorePurchases() await syncSubscriptionStatus() return .restored } catch { return .failed(error) } } private func hasStoreKitProduct(_ product: StoreProduct) -> Bool { if product.sk1Product != nil { return true } if #available(iOS 15.0, *), product.sk2Product != nil { return true } return false } private func syncSubscriptionStatus() async { let activeProductIds = await BillingClient.shared.activeProductIdentifiers() let entitlements = Superwall.shared.entitlements.byProductIds(activeProductIds) await MainActor.run { Superwall.shared.subscriptionStatus = entitlements.isEmpty ? .inactive : .active(entitlements) } } } ``` Replace `BillingClient` with your own billing implementation. It should start checkout for `product.productIdentifier`, report cancellation and pending states distinctly when possible, and expose the active product identifiers that should unlock Superwall entitlements. ## Keep Entitlements In Sync Superwall decides whether a user is active from `subscriptionStatus`, not from the external payment provider directly. When your billing system says the user has access, map the active product identifiers back to Superwall entitlements and set the status: ```swift Swift let activeProductIds: Set = ["pro_monthly_external"] let entitlements = Superwall.shared.entitlements.byProductIds(activeProductIds) Superwall.shared.subscriptionStatus = entitlements.isEmpty ? .inactive : .active(entitlements) ``` Call this after purchase, after restore, on app launch, and whenever your billing provider reports a subscription or entitlement change. > **Warning:** Make sure the product identifier returned by your billing system matches the product identifier configured in Superwall. If the identifier does not match, `entitlements.byProductIds(_:)` will not find the entitlement and the user can remain inactive after purchase. ## Trial Eligibility Custom Store Products can use the same trial variables as App Store products. Superwall checks the custom product's trial metadata and associated entitlements, then looks at the user's entitlement history to avoid showing a trial to someone who has already had access. For best results: * Attach at least one entitlement to each custom subscription product. * Keep `subscriptionStatus` current before presenting paywalls. * Return `.pending` when the external checkout requires more user action. * Return `.cancelled` when the user intentionally exits checkout. If customer information has not loaded yet, Superwall avoids treating the user as eligible for a custom-product trial. ## What Not To Do * Do not call `Superwall.shared.purchase(product)` for a custom product. That helper is for StoreKit-backed products. * Do not fetch custom products with `Superwall.shared.products(for:)`; that method fetches App Store products. * Do not rely on `sk1Product` or `sk2Product` for a custom product. Use `product.productIdentifier`. * Do not wait until the next app launch to update `subscriptionStatus` after purchase. ## Testing Test the full flow on a paywall that contains your Custom Store Product: 1. Confirm the product's price and trial copy render on the paywall. 2. Tap the product and verify your `PurchaseController` receives the product identifier. 3. Complete, cancel, fail, and mark a purchase pending in your external billing test environment. 4. Confirm your app updates `subscriptionStatus` after purchase and restore. 5. Confirm users who have already held the entitlement do not see a custom-product trial as available. For general purchase-controller setup, see [Advanced Purchasing](/docs/ios/guides/advanced-configuration).