# 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/ # Adding Products Add your existing products from their respective storefront, such as the App Store or the Google Play Store, to an app so they can be used in one or more paywalls. For adding Stripe products, please view [this doc](/docs/web-checkout/web-checkout-adding-a-stripe-product). For iOS products purchased through your own billing system, see [Custom Store Products](/docs/ios/guides/custom-store-products). > **Warning:** Before you attempt to test a paywall on iOS via TestFlight, make sure they are in the "Ready to Submit" phase if it's their initial launch. For local testing, you can use a [StoreKit configuration file](/docs/sdk/guides/testing-purchases) at any point. > **Note:** Right now, Superwall for iOS does not support [Promotional > Offers](https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/subscriptions_and_offers/setting_up_promotional_offers), > only [Introductory > Offers](https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/subscriptions_and_offers/implementing_introductory_offers_in_your_app). > Superwall for Android only supports 1 billing phase per offer. To get started, select an app. Then **click** the **Products** button from the sidebar. Choose **+ Add Product**: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/add-product.png) From there, you have five fields to fill out: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/add-product-modal.png) | Field | Description | | ------------ | ---------------------------------------------------------------------------------------------------------- | | Identifier | The StoreKit, Google Play, or custom billing product identifier for your product. | | Trial | The trial duration attached to the product, if any. | | Price | The price attached to the product. Either type one in, or just the dropdown to select common price points. | | Period | The length of the subscription. | | Entitlements | The entitlements this product belongs to. | When you're done, click **Save**. Note that the pricing information you enter here is **only** used in the Paywall Editor for App Store and Google Play products. On device, that information is pulled directly from the App Store or Google Play Store and will be localized. For iOS Custom Store Products, the SDK uses the product metadata from Superwall and routes purchase attempts to your `PurchaseController`. > **Warning:** Take care to make sure your product identifier is correct and matches its storefront. This is the > most common cause for products not working correctly when testing. ## Entitlements Entitlements represent the amount of access or features users are entitled to. They can be used to offer different tiers of service, or just represent a single "active" subscription if your app only has one level of service (i.e. "Pro" unlocks everything). All products are granted a default entitlement. > **Warning:** **Subscription status is determined by entitlements.**If a product has no entitlements then when a user purchases it their subscription status will be **Inactive**. > Ensure each subscription product is linked to at least one entitlement. If you don't have multiple tiers of service, you can use only the default `pro` entitlement — you don't need to create any additional entitlements. To add an entitlement, **click** on the **Entitlements** tab within the products page. Then click **Add Entitlement**: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/addEntitlement.png) From there, give it a name, and click **Create**: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/createEntitlement.png) At this point, you can go back to your products and attach one or more entitlements to each one. ### Editing entitlements To edit or delete an entitlement, click on the trailing pencil icon or the trash can icon to remove one. Note that if your entitlement is associated with any product, you'll need to remove it first before you can delete it. ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/editEntitlement.png) ## Getting product identifiers *If you use RevenueCat to handle in-app subscriptions, skip to [Using RevenueCat](/docs/dashboard/products#using-revenuecat)* ### Using App Store Connect On **App Store Connect**, head over to **Your App ▸ App Store ▸ Subscriptions ▸ *Your Subscription Group***: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/0b4f712-Screen_Shot_2022-05-17_at_3.29.45_PM.png) Then, copy your **Product ID**: ![3372](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/f0c2605-Screen_Shot_2022-05-17_at_3.28.41_PM.png) Your products, whether live or pre-release, shouldn't be in the "Missing Metadata" state. If they are, you won't be able to test them on device. To fix this, make sure your products are in the "Ready to Submit" or "Approved" state. Superwall will automatically warn you if they are in this state when you have the [App Store Connect API set up](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking#app-store-connect-api): ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/asc_invalid_products.png) ### Using Google Play Console To add subscription products, on **Google Play Console**, head over to **Your App ▸ Monetize ▸ Products ▸ Subscriptions**: ![Google Play Products](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/google-play-products.png) You can also grab your **base plan id** and any offer ids if you're going to use them. To add in-app products, no base plan id is required. For **period**, select **None(Lifetime/Consumable)**: ![Google Play Products](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/google-play-in-app-products.png) #### Google Play Offers Google play allows you to create multiple base plans and multiple offers for each base plan. When using Superwall, you can either specify a specific offer or let Superwall choose the best offer for the user. **Automatically Choosing Offers** Once Google has returned offers that are applicable for that user, Superwall will use the following logic to choose the best offer for the user: * Find the longest free trial the customer is eligible for * If there is no free trial, find the cheapest introductory period the customer is eligible for * If there is none, fall back to the base plan * If you have an offer on one of your products that you never want to automatically be selected by this logic (for example, because it is a discount only used for a specific customer group), add the tag `sw-ignore-offer` to that offer in Google Play Console. To add the `sw-ignore-offer` tag in **Google Play Console**: 1. Open the subscription offer you want to exclude and choose **Advanced settings**. 2. In **Tags**, add `sw-ignore-offer` (all lowercase) and click **Save**. Superwall will ignore any offer that includes this tag when selecting the best offer for the user. That means that if your eligibility criteria is set so that someone can use an offer only once, we'll respect that and choose from the best remaining offers. **Specifying Offers** Let's say you have a base plan with two or more offers which differ in trial duration. You may want to A/B test these offers to see which one performs best. To achieve this, you can specify the offer id in the Superwall dashboard. When we specify an offer id, we'll ignore the logic above and always use the offer **if the user is eligible**. If the user is not eligible for the offer, we'll fall back to the base plan. The [eligiblity criteria](https://support.google.com/googleplay/android-developer/answer/12154973?hl=en#:~\:text=or%20inactive%20states.-,Offer%20eligibility%C2%A0,-You%20can%20provide) is set in the Google Play Console, and is based on the user's purchase history. ![Multiple Offers](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/multiple-offers.png) ## Using products in paywalls After you've added products to an app, you're ready to start using them in paywalls. Check out our [docs](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-products) for a step-by-step guide on how to do that. ## Understanding how consumable and non-consumable products work Superwall uses entitlements to determine ongoing access. Consumables and non-consumables are both one-time purchases, but they should be configured differently: * **Consumable products** (e.g., credits, tokens, energy boosts) should usually have **Period** set to **None (Lifetime / Consumable)** and **no entitlements** selected. Your app grants the benefit after the purchase event. * **Non-consumable products** (e.g., a lifetime unlock) should use **Period** set to **None (Lifetime / Consumable)** and should be linked to the entitlement they unlock. If a product has no entitlements, purchasing it will not make the user's subscription status active. This is expected for consumables. Finish setup in the SDK guide for your platform: * [iOS consumable products](/docs/ios/guides/consumable-products) * [Android consumable products](/docs/android/guides/consumable-products) * [Flutter consumable products](/docs/flutter/guides/consumable-products) * [Expo consumable products](/docs/expo/guides/consumable-products) On iOS, consumables also require `SKIncludeConsumableInAppPurchaseHistory` in your `Info.plist` as a Boolean set to `YES`. On pre-iOS 18 devices, StoreKit 1 will be used when this key is present. See the [iOS consumables guide](/docs/ios/guides/consumable-products) for the exact setup. ## Understanding paid offer types Any **paid up front** or **pay as you go** product offer types will also be referenced using the `trial` variables. In Superwall, these are represented as "paid trials". For example, to reference the product's trial price of $3.99 in the image below, you'd use `products.selected.trialPeriodPrice`: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/paidOfferExample.png) For more on setting customized text using Liquid Templating, visit this [doc](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-liquid). ## A note on StoreKit configuration files If you're using a StoreKit Configuration file, pricing information will come from there during local testing. Therefore, it's important to keep your StoreKit Configuration file, Superwall, and the App Store products all in sync. Follow our [Setting up StoreKit testing](/docs/sdk/guides/testing-purchases) guide for more information. > **Note:** Having an issue on device with products not appearing? Run through [this > checklist](/docs/support/troubleshooting/products-not-loading) to make sure everything is configured > correctly.