# 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/ # SuperwallOptions A configuration class for customizing paywall appearance and behavior. > **Warning:** Only modify `networkEnvironment` if explicitly instructed by the Superwall team. Use `.release` (default) for production apps. > **Tip:** Use different `SuperwallOptions` configurations for debug and release builds to optimize logging and behavior for each environment. > **Note:** The SDK automatically chooses StoreKit 2 on iOS 15+ and falls back to StoreKit 1 on older versions, but you can override this with `storeKitVersion`. ## Purpose Configures various aspects of Superwall behavior including paywall presentation, networking, logging, and StoreKit version preferences. ## Signature ```swift @objcMembers public final class SuperwallOptions: NSObject { public var paywalls: PaywallOptions public var storeKitVersion: StoreKitVersion public var networkEnvironment: NetworkEnvironment public var logging: LoggingOptions public var localeIdentifier: String? public var shouldBypassAppTransactionCheck: Bool public var testModeBehavior: TestModeBehavior public var localResources: [String: AssetResource] } ``` ## Parameters ## Returns / State This is a configuration object used when calling [`configure()`](/docs/ios/sdk-reference/configure). ## Usage Basic options setup: ```swift let options = SuperwallOptions() // Configure paywall behavior options.paywalls.shouldShowPurchaseFailureAlert = false options.paywalls.shouldAutoShowPurchaseLoadingIndicator = true options.paywalls.automaticallyDismiss = true // Set StoreKit version preference options.storeKitVersion = .storeKit2 // Configure logging options.logging.level = .warn options.logging.scopes = [.superwallCore, .paywallViewController] // Set locale for testing options.localeIdentifier = "en_GB" // Bypass app transaction check (useful for testing) options.shouldBypassAppTransactionCheck = true // Use with configure Superwall.configure( apiKey: "pk_your_api_key", options: options ) ``` PaywallOptions configuration: ```swift let paywallOptions = PaywallOptions() // Presentation behavior paywallOptions.shouldShowPurchaseFailureAlert = false paywallOptions.shouldAutoShowPurchaseLoadingIndicator = true paywallOptions.automaticallyDismiss = true // Transaction behavior paywallOptions.transactionTimeout = 30.0 // seconds paywallOptions.restoreFailedPurchaseAlert.title = "Restore Failed" paywallOptions.restoreFailedPurchaseAlert.message = "Please try again" // Product overrides paywallOptions.overrideProductsByName = [ "primary": "produceID_to_replace_primary_product" ] // Assign to main options options.paywalls = paywallOptions ``` Logging configuration: ```swift let loggingOptions = LoggingOptions() loggingOptions.level = .debug loggingOptions.scopes = [.all] // or specific scopes like [.superwallCore, .network] options.logging = loggingOptions ``` Real-world example for production: ```swift func configureSuperwallForProduction() { let options = SuperwallOptions() // Minimal logging for production options.logging.level = .error // Customize paywall behavior options.paywalls.shouldShowPurchaseFailureAlert = true options.paywalls.automaticallyDismiss = true // Use StoreKit 2 for better performance on iOS 15+ options.storeKitVersion = .storeKit2 Superwall.configure( apiKey: "pk_your_production_api_key", options: options ) } ``` Debug configuration for development: ```swift func configureSuperwallForDebug() { let options = SuperwallOptions() // Verbose logging for debugging options.logging.level = .debug options.logging.scopes = [.all] // Show detailed error alerts options.paywalls.shouldShowPurchaseFailureAlert = true // Test with specific locale options.localeIdentifier = "es_ES" Superwall.configure( apiKey: "pk_your_test_api_key", options: options ) } ``` ## Related * [`PaywallOptions`](/docs/ios/sdk-reference/PaywallOptions) * [`localResources`](/docs/ios/sdk-reference/localResources) ## Runtime Interface Style Configuration While `SuperwallOptions` provides initial configuration, you can dynamically change the interface style (light/dark mode) for paywalls at runtime using: ```swift // Force dark mode for all paywalls Superwall.shared.setInterfaceStyle(to: .dark) // Force light mode for all paywalls Superwall.shared.setInterfaceStyle(to: .light) // Revert to system default Superwall.shared.setInterfaceStyle(to: nil) ``` Use this method if you have a themeing system that is different than the system. The change takes effect immediately and persists until changed again or the app restarts.