# 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/
# Presenting Paywalls from One Another
Learn how to present a different paywall from one that's already presented.
It's possible to present another paywall from one already showing. This can be useful if you want to highlight a special discount, offer, or emphasize another feature more effectively using a different paywall. Check out the example here:
* A [placement](/docs/dashboard/dashboard-campaigns/campaigns-placements) is evaluated when the button is tapped. Superwall sees that the user isn't subscribed, so a paywall is shown.
* Next, the user taps the "Custom Icons Too 👀" button.
* The current paywall dismisses, and then presents the icons-centric paywall.
> **Tip:** You can extend this technique to be used with several other interesting standard placements. For
> example, presenting a paywall when the user abandons a transaction, responds to a survey and more.
> Check out the examples [here](/docs/dashboard/dashboard-campaigns/campaigns-standard-placements#standard-placements).
There are two different ways you can do this, with [custom placements](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements#tap-behaviors) or by using [deep links](/docs/sdk/quickstart/in-app-paywall-previews). We recommend using custom placements, as the setup is a little easier.
> **Note:** Custom placements minimum SDK requirements are 3.7.3 for iOS, 1.2.4 for Android, 1.2.2 for
> flutter, and 1.2.6 for React Native.
They both have the same idea, though. You create a new campaign specifically for this purpose, attach a paywall and either add a filter (for deep linking) or a new placement (for custom placements) to match users to it.
> **Note:** While it's not *required* to make a new campaign, it is best practice. Then, if you later have
> other paywalls you wish to open in the same manner, you can simply add a new
> [audience](/docs/dashboard/dashboard-campaigns/campaigns-audience) for them in the campaign you make from the steps below.
### Use Custom Placements
## Add a Custom Placement Tap Behavior
Select a component on your paywall and add a **Custom Placement** Tap Behavior, and name it whatever you wish (i.e. showIconPaywall).
Finally, be sure to click **Publish** at the top of the editor to push your changes live
## Create a campaign for the other paywall to show
Create a new [campaign](/docs/dashboard/dashboard-campaigns/campaigns) specifically for this purpose, here — it's called "Custom Placement Example":
## Add the placement
In your new campaign, [add a new placement](/docs/dashboard/dashboard-campaigns/campaigns-placements#adding-a-placement) that matches the name of your custom action you added in step one. For us, that's `showIconPaywall`:
## Choose a paywall to show
Finally, choose a paywall that should present by **clicking** on the **Paywalls** button at the top:
### Use Deep Links
## Setup Deep Links
You'll need [deep links](/docs/sdk/quickstart/in-app-paywall-previews) set up for your app. This is how Superwall
will query parameters and later launch your desired paywall.
## Trigger the deep link from an existing paywall
Choose the paywall you want to open another paywall from. Then, click the element (a button, text, etc.) that should open the new paywall:1) In its component properties on the right-hand side, add a **Tap Behavior**.
2) Set its **Action** to **Open Url**.
3) For the URL, use your deep link scheme from step one, and then append a parameter which will represent which other paywall to present. This is specific to your app, but here — `offer` is the key and `icons` is the value. Your resulting URL should be constructed like this: `deepLinkScheme://?someKey=someValue`.
4) Set its **Type** to **Deep Link**.
5) Click **Done**.Here's what it should look like (again, with your own values here):
Finally, be sure to click **Publish** at the top of the editor to push your changes live.
## Create a campaign for the other paywall to show
Create a new [campaign](/docs/dashboard/dashboard-campaigns/campaigns) specifically for this purpose, here — it's called "Deeplink Example":
## Add the placement
In your new campaign, [add a placement](/docs/dashboard/dashboard-campaigns/campaigns-placements#adding-a-placement) for the `deepLink_open` standard placement:
## Edit the audience filter
Edit the default audience's filter to match `params.[whatever-you-named-the-parameter]`. Recall that in our example, the parameter was `offer` and the value was `icons`. So here, we'd type `params.offer` and **click** the **+** button:
Superwall will ask what type of new parameter this is — choose **Placement** and enter the parameter name once more (i.e. "offer"). Click **Save**:
Finally, choose the **is** operator and type in the value of your parameter (in our case, "icons"). Then, **click** the **+ Add Filter** button. Here's what it should look like:
## Choose a paywall to show
Finally, choose a paywall that should present by **clicking** on the **Paywalls** button at the top:
### Test Opens
After following the steps above for either method, be sure to test out your presentation. Open the relevant paywall on a device and tap on whichever button should trigger the logic. The currently presented paywall should dismiss, and then immediately after — the other paywall will show.