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

# App2Web

Link U.S. customers from iOS paywalls to Safari for Stripe checkout.

For customers on the United States App Store storefront, you can add calls to action in your iOS paywalls that open Stripe checkout outside of your app in Safari or the user's default browser.

Do not present Stripe Checkout inside your iOS app using an in-app browser, `SFSafariViewController`, `WKWebView`, or another embedded web view. For external purchase links, the checkout flow should leave the app and open in the external browser.

> **Note:** Apple's App Review Guidelines allow United States storefront apps to include buttons, external links, or calls to action for purchase methods other than in-app purchase. Review [Guideline 3.1.1(a)](https://developer.apple.com/app-store/review/guidelines/#business) before submitting your app.

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

## Configure Web Checkout

First, follow the [web checkout setup guide](/docs/web-checkout#getting-setup) to create a Stripe app and configure your web checkout settings. Specifically, you'll need to complete the first three steps. This includes installing the [Superwall Stripe app](https://marketplace.stripe.com/apps/superwall), setting up your app's settings, and adding your Superwall web paywall domain to Stripe if you want Apple Pay to appear in checkout.

## Add a Stripe product to an iOS paywall

Select a paywall and add a Stripe product to it. This lets users start an external browser checkout flow from the paywall. Stripe products are prepended with "stripe" in the product selector:
![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/web-checkout-select-product.png)

## Create a campaign for U.S. customers

Since the policy applies to customers on the United States storefront, create a campaign filter that matches those customers. Use `storeFrontCountryCode` equals `USA`, like this:> **Note:** For App Review, explain that U.S. storefront customers can tap a paywall call to action that opens an external browser for Stripe checkout. Non-U.S. storefront customers should continue using Apple in-app purchase unless another regional policy applies.

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

## Respond to Checkout

From there, the flow works the same way as web checkout. Once the payment succeeds in the external browser, the [Superwall delegate](/docs/sdk/guides/using-superwall-delegate) functions `willRedeemLink()` and `didRedeemLink(result:)` will be called when the user returns through the deep link. You can use these functions to show any specific UI as described in our [Post-Checkout Redirecting](/docs/sdk/guides/web-checkout/post-checkout-redirecting) docs.Additionally, entitlement and subscription status will update automatically. For lifetime one-time products, the linked entitlement becomes active without an expiration. For consumables, inspect `CustomerInfo.nonSubscriptions` and grant the purchased quantity in your own system. If you're using a `PurchaseController`, refer to [the docs here](/docs/sdk/guides/web-checkout/linking-membership-to-iOS-app#using-a-purchasecontroller).

If you need to test checkout, learn how [here](/docs/web-checkout/web-checkout-testing-purchases).

### Apple Pay

App2Web checkout opens from your iOS paywall into the Superwall-hosted Stripe checkout page. If you want Apple Pay to appear there, add your `*.superwall.app` web paywall domain to Stripe's payment method domains before testing or launching.

See [Apple Pay domain setup](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings#apple-pay-domain-setup) for the full setup steps.

### Localized checkout prices

App2Web supports [Stripe Adaptive Pricing](/docs/web-checkout/web-checkout-adaptive-pricing) for the external Stripe checkout step. Enable Adaptive Pricing in Stripe, then users who leave the app for checkout can see localized currency based on their location.

Keep the campaign filter aligned with Apple's external purchase rules. Adaptive Pricing changes the currency shown during Stripe checkout; it does not change which users should be eligible to see an external purchase link in your app.

### Prefill customer information

When starting checkout from an iOS paywall (App2Web), you can prefill customer information in two ways:

#### Email

Stripe will automatically prefill the email field if you set the user's `email` as a [User Attribute](/docs/sdk/quickstart/setting-user-properties) in your app before initiating checkout.

#### Stripe Customer ID

If you already have a Stripe customer ID for your user, you can set it as the `stripe_customer_id` user attribute. This will associate the checkout session with the existing Stripe customer, automatically prefilling their saved information and payment methods:

```swift
Superwall.shared.setUserAttributes([
    "email": user.email,
    "stripe_customer_id": user.stripeCustomerId
])
```

> **Note:** When both `stripe_customer_id` and `email` are provided, the Stripe customer ID takes precedence. The checkout session will use the existing customer's information rather than creating a new customer.