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

Frequently asked questions about web checkout.

### How does restoring memberships work when you've purchased via web checkout?

When the user taps on the restore link in the paywall, we'll do the normal restore flow for on-device subscriptions. However, if you've enabled web checkout and the restored
entitlements don't match the entitlements belonging to the products on the paywall, we'll present an alert asking the user if they'd like to check for purchases on the web. This will
take them out of your app to the [plan management screen](/docs/web-checkout/web-checkout-managing-memberships) where they can get a redemption link to restore their purchases.

### Does Superwall email customers after checkout?

Yes. By default, Superwall emails the address used during checkout with instructions and a redemption link to activate the purchase in your app. The email is sent from `Your app name <support+your-app-name@superwall.app>` with the subject `Your activation link from your app name`.

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

To turn these off, use the "Disable Superwall Emails" setting in your Stripe app settings — see [how to disable the activation link email](/docs/support/web-checkout/3969573187-how-do-i-disable-the-activation-link-email-for-web-checkout).

### Do customers who use Sign in with Apple Hide My Email receive web checkout emails?

Yes. If customers check out with an Apple private relay address, such as `abc123@privaterelay.appleid.com`, register Superwall as an allowed email source in Apple Developer.

Superwall sends web checkout emails from your app-specific Superwall address, such as `support+your-app-name@superwall.app`. These emails include activation and subscription management links. Apple can reject those emails for Hide My Email customers unless `superwall.app` is registered as an email source for Sign in with Apple.

Configure this before launching web checkout:

1. Go to [Apple Developer Services Configuration](https://developer.apple.com/account/resources/services/configure).
2. Open **Configure Sign in with Apple for Email Communication**.
3. Add `superwall.app` as an email source. If you prefer to authorize a specific sender, add your app's Superwall sender address, such as `support+your-app-name@superwall.app`.

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/sign-in-with-apple-email-sources.png)

Once registered, Apple will allow emails from Superwall to be delivered to private relay addresses.

For Apple's requirements, see [Configure private email relay service](https://developer.apple.com/help/account/capabilities/configure-private-email-relay-service).

> **Warning:** If you skip this step, customers who use **Hide My Email** may not receive web checkout emails
> from Superwall. If customers already checked out before the email source was registered, ask them
> to request a new link from your `https://{your-domain}.superwall.app/manage` page after the sender
> is configured.

### What happens if a user taps the redemption link multiple times or shares it?

Redemption codes are single-use and tied to a specific device. Once a code has been redeemed, it cannot be used again on a different device.

However, users can visit the manage page and request a new redemption link. This generates a new code that can be used to activate access on another device.

#### Without accounts (`identify` not called)

If you're not using accounts with Superwall (i.e. you never call `identify`), we allow up to **five active devices** per user. When a sixth device redeems a code, the **first device** to have redeemed a code will automatically lose access. This helps prevent abuse while still supporting reasonable multi-device usage.

#### With accounts (`identify` called)

If you are using accounts with Superwall (i.e. you call `identify` with an `appUserId` when someone logs in), then entitlements are tied to the user ID, not the individual device.

* If two different `appUserIds` redeem codes, **only the most recently identified user will retain access**.
* If the **same `appUserId` is used across multiple devices**, all those devices will **automatically share access** without needing to redeem again.

This system ensures flexibility while protecting against unauthorized sharing of redemption codes.

### How do I associate a web checkout purchase with a user in my app?

The short answer — use Superwall's [user identification APIs](/docs/sdk/quickstart/user-management#identified-users). When you configure Superwall, or a user signs in or out, you can always associate their login status to Superwall's SDK:

```swift
Superwall.shared.identify(userId: user.id)
```

This will ensure that the user is associated with the web checkout purchase.

### A user paid on the web and can't access their purchase in the app. What should I do?

Direct them to your app's plan management page so they can retrieve their redemption link or manage billing. For example: `http://yourapp.superwall.app/manage`

### Can I sell lifetime or consumable products through Stripe?

Yes. Create a Stripe one-time price, import it into Superwall, and add it to a web paywall. For lifetime access, attach the entitlement the product should unlock. For consumables, usually leave the product without an entitlement and use `CustomerInfo.nonSubscriptions` to credit the user's account after purchase.

Learn more in [Stripe One-Time Purchases](/docs/web-checkout/web-checkout-stripe-one-time-purchases).

### When should I use Redirect mode instead of Redeem mode?

Use **Redirect mode** when you need to:

* Show a custom success or onboarding page after purchase
* Perform additional verification or collect more information before granting access
* Integrate with your own deep linking or authentication infrastructure
* Track conversions in your own analytics before redemption

Use **Redeem mode** (the default) when:

* You want Superwall to handle the entire redemption flow automatically
* You don't need custom post-purchase logic
* You want the simplest integration

Most apps should use Redeem mode. You can always switch between modes in your [Application Settings](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings#post-purchase-behavior).

### What data is passed to my redirect URL in Redirect mode?

When using Redirect mode, the following query parameters are automatically appended to your custom URL:

**Standard parameters**:

* `app_user_id` - The user's identifier from your app (if you called `identify`)
* `email` - The user's email address from checkout
* `stripe_subscription_id` - The Stripe subscription ID, or the Stripe Checkout session ID for one-time purchases

**Custom parameters**: Any placement parameters you set when creating the web checkout link will also be included.

**Example redirect**:

```
https://yourapp.com/success?
  app_user_id=user_123&
  email=user@example.com&
  stripe_subscription_id=sub_1234567890&
  campaign_id=summer_sale
```

You can use this data to verify the purchase, link it to your user account, or perform custom onboarding. Learn more about [post-checkout redirecting](/docs/sdk/guides/web-checkout/post-checkout-redirecting).