# 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/ # Paywall Settings Sidebar The settings sidebar is split into 3 sections: Products; Design; and Advanced. > **Warning:** The legacy editor is deprecated. Please visit the docs covering our new > [editor](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-overview). ### Products In this section, you choose your products to display on your paywall. You'll need to set up your products via Settings as detailed [here](/docs/dashboard/products). ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/8cf8e67-Screenshot_2023-06-14_at_16.53.22.png) ### Settings These settings determine how the paywall displays and how it behaves. ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/93599d2-Screenshot_2023-06-14_at_17.25.08.png) #### Presentation Style Here, you can set the presentation style to one of the following: * Modal: Presents the paywall modally that can be swiped away. * Full Screen: Presents the paywall over the entire screen. * Push: Presents the paywall as if it's being pushed on to a navigation stack. This requires v2.4+ of the SDK. * No Animation: Presents the paywall without animation. This requires v2.4+ of the SDK. * Drawer: Presents the paywall as a drawer, taking up 70% of the screen. This is an iOS 16 only feature that works with SDK v3+. #### Presentation Targeting The default behavior of the SDK presents a paywall only to users who aren't subscribed. However, you can override this to always present regardless of subscription status by setting *Present Paywall* to *Always*. #### Feature Gating Feature gating allows your team to retroactively decide if the paywall is *Gated* or *Non Gated*. | Type | Behavior | Example | | ----------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------ | | **Non Gated** (default) | Show Paywall → Execute Feature | When "Sign Up" button is pressed, show a paywall, but continue onboarding after it closes. | | **Gated** | Show Paywall → Is user paying?If Yes → Execute FeatureIf No → Do Nothing | When "Start Workout" button is pressed, show a paywall. Only continue if paying. | Remember, the [register feature block](/docs/sdk/quickstart/feature-gating) is always executed if: 1. No campaign is configured for the event 2. The user is already paying #### Cache on device Caching is enabled by default on paywalls. This means that after the first load of a paywall, it will be cached on disk for use next time the app is opened unless you make a change to it on the editor. This greatly reduces network load and the time taken to load paywalls. It does of course increase memory usage of your app so you can turn caching off if you wish by setting *Cache on device* to *Disabled*. ### Fonts You can set the font and font size and font weight used for your paywall, including custom fonts. ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/c514eb7-Screenshot_2023-06-14_at_17.46.28.png) ### Sizing, Spacing, and Colors Set the global design for your paywall. ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/bc61385-Screenshot_2023-06-14_at_17.55.16.png) #### Free Trial Reminder You can add a local notification that fires after a number of days, when a free trial has been purchased. After the user starts a free trial, it will ask them to enable notifications if they haven't already done so. ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/free-trial-reminder.png)
> **Note:** **In sandbox mode, the free trial reminder will fire after x minutes, instead > of x days.** ![local-notifications](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/local-notification.jpg) This is how the title, subtitle, and body appears in a notification: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/notificationExample.png) If you use local notifications within your app, you'll want to use the following functions to clear your app's pending and delivered notifications without affecting Superwall: * `UNUserNotificationCenter.current().removeAllPendingNonSuperwallNotificationRequests()` * `UNUserNotificationCenter.current().removeAllDeliveredNonSuperwallNotifications()` You can use the following to remove notifications specific to Superwall: * `UNUserNotificationCenter.current().removeAllDeliveredSuperwallNotifications()` * `UNUserNotificationCenter.current().removeAllPendingSuperwallNotificationRequests()` ### Advanced Here you can apply custom CSS and JS to your paywall. ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/88811cb-Screenshot_2023-06-14_at_17.57.21.png)