# 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/

# Web Checkout Links

Learn how to use campaigns and placements to present web paywalls using Superwall's web checkout links.

Once you've [created a Stripe app](/docs/web-checkout/web-checkout-creating-an-app), [configured Stripe with Superwall](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings) via the [Superwall Stripe app](https://marketplace.stripe.com/apps/superwall) and have [created Stripe products](/docs/web-checkout/web-checkout-adding-a-stripe-product) — you're ready to configure a campaign to show a web paywall.

> **Note:** Before you proceed, recall that web checkout has all of the advantages of the Superwall platform. If you are unfamiliar with how to create campaigns or what a placement is — we recommend you read through the [introduction](/docs/using-the-dashboard) documentation and [campaigns doc](/docs/dashboard/dashboard-campaigns/campaigns) first.

### Understanding placements in web checkout

There are two primary differences between web checkout and the typical Superwall campaign flow:

1. **Placements become unique URLs** which, in turn, show your paywall. These are called *web checkout links*.
2. **User variables** are not available in audience filtering.

Other than that, everything operates as a normal Superwall campaign would. For example:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/web2app_make_campaign.png)

Here, the placement `black-friday-promo` presents a paywall. If the app's URL in [settings](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings) is `caffeinepal`, then the URL for this placement would be `https://caffeinepal.superwall.app/black-friday-promo`. Visiting that web checkout link presents a paywall:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/web2app_showing_paywall.png)

Conceptually, you can think of these web checkout links performing a similar function as registering a placement does in our mobile SDK:

```swift
Superwall.shared.register(placement:"black-friday-promo") { _ in }
```

This means that you now can use web checkout with all of the same powerful features that Superwall offers, such as A/B testing, paywall targeting and more. Again, these work just like any other campaign would in Superwall. The interface is the same, so now you create placements, start creating audience filters and more:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/web2app_campaigns.png)

Also, remember to create responsive paywalls. Users can view your checkout page on a laptop, phone and other varying sized viewports. For some quick tips, check out this blog post over adapting paywalls to look great on [iPad](https://superwall.com/blog/how-to-create-adaptable-paywalls-for-iphone-and-ipad-using-superwall).

### A note on the `$home` placement

Every campaign has a `$home` placement out of the box. This placement acts a "default" link, and isn't required to be part of the URL as other placements are. For example:

```plaintext
// This works 
https://caffeinepal.superwall.app/$home

// And this also works, even though `$home` isn't in the URL
https://caffeinepal.superwall.app/
```

This is useful so that even if a user visits your web checkout link, and there isn't a placement in the URL — they'll still see a paywall.

### How query string parameters work

You can attach query string parameters to any web checkout link by appending them to the URL:

```html
https://caffeinepal.superwall.app/black-friday-promo?name=jordan
```

This will pass the `name` parameter to the placement, and you can use it in your audience filters. For example, you could create a filter that only shows the paywall if the `name` parameter is equal to `jordan`:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/web2app_qsp_jordan.png)

Or, you could access them in your paywall using the same flow as you would for [placement parameters](/docs/using-placement-parameters):

1. In the paywall editor, add a variable.
2. Make it a `parameter` type. Match the `name` to the query string parameter key (here, that would be `name`).
3. Set the value type, then click **Create**.
4. Now, you can use that variable in your paywall:

This makes it easy to show in your paywall:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/web2app_qsp_var.png)

Then, if the URL is visited, the audience filter matches from above — and we can see the value on the paywall, too:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/web2app_qsp_paywall.png)

Of course, this is a simplistic example — but this is useful for personalization, seasonal events, influencer campaigns and more. Any query string parameter you pass can be used in the paywall, and in audience filters.

### Localized checkout prices

Web checkout links support [Stripe Adaptive Pricing](/docs/web-checkout/web-checkout-adaptive-pricing). When Adaptive Pricing is enabled in Stripe, customers can see localized currency in the Stripe checkout flow based on their location.

This does not change how you build campaigns or placements in Superwall. Create the web checkout link as usual, then let Stripe localize the checkout price when the customer starts payment.

### Automatically populating user emails in checkout flows

> **Tip:** This section is Web2App only (starting from a web link). For App2Web (starting from an iOS paywall), see [App2Web](/docs/web-checkout/web-checkout-direct-stripe-checkout#prefill-email).

There is a special query string parameter you can use to automatically populate the user's email in the checkout flow. This is useful for pre-filling the email field in the checkout form, so that users don't have to enter it manually. Simply add `email` and set the value to the user's email address:

```html
https://caffeinepal.superwall.app/black-friday-promo?email=myemail@yahoo.com
```

When the Stripe checkout flow launches, the email is now filled out automatically:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/web2app_email.jpeg)

### Automatically populating appUserId in checkout flows

There is a set of special query string parameters which will set the appUserId for the subscription. This overrides the default behavior where Superwall will automatically assign an anonymous identifier. You may pass `uid`, `user`, or `app_user_id` to override the default.

```html
https://caffeinepal.superwall.app/black-friday-promo?app_user_id=my-custom-id
```

This identifier will show up in Stripe metadata & webhooks. The app\_user\_id will be put into the `client_reference_id` field on a Stripe Checkout Session and will be included on the subscription metadata under `_sw_app_user_id`