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

# Stripe Setup

Connect Superwall to Stripe using the official Stripe app and configure your settings.

Once you've created a [Stripe app](/docs/web-checkout/web-checkout-creating-an-app), you'll need to connect it with Stripe and fill in a few settings. This is a one-time setup that connects Superwall to Stripe. The easiest way to get started is to click on the link in your overview page, which will take you to your app's [Settings](/docs/dashboard/dashboard-settings/overview-settings) page:

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

### Application settings

Fill out metadata about your iOS app in this section.

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

1. **Icon:** An icon to represent your app, we recommend using the same one that your iOS app does. This will appear on the checkout and subscription management pages.

2. **Application Name:** The name of your app, we recommend using the same name as your iOS app.

3. **Support URL:** A URL to your support page. This will be shown on the checkout and subscription management pages.

4. **Support Email:** An email you provide customers for support questions and general reach out

5. **Redeemable on Desktop:** If your app is an iPad app on Mac, enable this option so that users can redeem products on their Mac. If you aren't using iPads Apps on the Mac, you can disable this. If this is disabled, Superwall enforces redemption on an iOS device.

Once you've filled out this information, **click** on the **Update Application** button.

### Post-Purchase Behavior

Configure what happens after a user completes a purchase on the web:

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

**Redeem (Default)**: Superwall manages the entire redemption flow. Users are automatically deep linked to your app with a redemption code, with fallback to the App Store/Play Store if the app isn't installed. This is recommended for most apps.

**Redirect**: Redirect users to your own custom URL with purchase information passed as query parameters. Use this when you need to:

* Show a custom success or onboarding page
* Perform additional verification or actions before redemption
* Integrate with your own deep linking infrastructure

When using Redirect mode, you'll need to provide a **Redirect URL** (must start with `https://`). Purchase data will be appended as query parameters:

* `app_user_id` - User's app identifier
* `email` - User's email address
* `stripe_subscription_id` - Stripe subscription ID, or Stripe Checkout session ID for one-time purchases
* Any custom placement parameters you've set

Learn more about [post-checkout redirecting](/docs/sdk/guides/web-checkout/post-checkout-redirecting).

> **Note:** This application setting is the default for Web Checkout purchases. A web checkout paywall
> can override it for a specific purchase button with a **Redeem Purchase** after-purchase
> action. See [Redeem Purchase for web checkout](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements#redeem-purchase-for-web-checkout).

### Web Paywall Domain

This is the domain your paywalls will be shown from. This was set when the Stripe app was created, and cannot be changed.

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

### Apple Pay domain setup

If you want Apple Pay to appear in Stripe Checkout, add your Superwall web paywall domain as a Stripe payment method domain. Stripe requires the exact domain that hosts checkout to be registered before domain-based payment methods such as Apple Pay can appear.

For a Superwall web checkout app, register the domain shown in **Web Paywall Domain**. For example, if your Superwall checkout links use `https://caffeinepal.superwall.app`, register `caffeinepal.superwall.app` in Stripe.

> **Note:** Register the Superwall subdomain only. Do not include `https://`, a path, or the root
> `superwall.app` domain.

## Open payment settings in Stripe

In Stripe, open **Settings**, then select **Payments**.
![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe-settings-payments.png)

## Open payment method domains

In the Payments settings, open **Payment method domains**.
![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe-payment-method-domains.jpg)

## Add your Superwall domain

Click **Add a new domain**, enter your Superwall web paywall domain, then save it.
![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe-add-superwall-domain.jpg)

After Stripe validates the domain, it should appear as enabled. Apple Pay may still be hidden if the customer is not using a supported device, browser, card, country, or currency.

> **Tip:** Stripe settings are mode-specific. If you use sandbox checkout, repeat this setup with **Test mode**
> enabled in Stripe. Then repeat it again in live mode before launching.

For more details, see Stripe's [payment method domain registration docs](https://docs.stripe.com/payments/payment-methods/pmd-registration).

### Stripe Live Configuration

To connect Stripe with Superwall, you'll use the official Superwall Stripe app:

#### Step 1: Visit the Stripe Marketplace

Visit the [Superwall app on Stripe Marketplace](https://marketplace.stripe.com/apps/superwall):

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

#### Step 2: Install the App

Click **Install app** to begin the authorization flow:

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

#### Step 3: Continue Installation

Click **Continue** to proceed with the installation:

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

#### Step 4: Generate API Keys

Click **Generate keys** to create your API keys:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe/step-4-generate-key.png)

#### Step 5: Confirm Key Generation

Click **Generate keys** again to confirm:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe/step-5-generate-key-2.png)

#### Step 6: Copy Your Keys

After installation, you'll receive a **Publishable Key** and a **Restricted Secret Key** with the proper permissions already configured. Copy both keys:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe/step-6-copy-keys.png)

#### Step 7: Configure Superwall

Paste the keys into the corresponding fields in Superwall:

* **Publishable Key**: Your Stripe publishable key from the app
* **Secret Key**: The restricted secret key provided by the app

Then **click** on **Update Configuration** to save your changes.

This section should say "Configured" at the top right if setup was successful:

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

### Adaptive Pricing

If you want web checkout customers to pay in their local currency, enable [Stripe Adaptive Pricing](/docs/web-checkout/web-checkout-adaptive-pricing) in Stripe's payment settings after connecting your Stripe keys. Adaptive Pricing is configured in Stripe separately for live and sandbox mode.

### Stripe Sandbox Configuration

> **Note:** The Superwall Stripe app provides both live and test mode keys. Make sure you're in the correct mode in your Stripe dashboard when copying keys.

For sandbox/test mode, switch to **Test mode** in your Stripe dashboard (toggle in the top-right corner), then follow these steps:

#### Step 1: Access the Superwall App

Navigate to the Superwall app in your Stripe dashboard. If already installed, find it under **Apps**:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe-test/step-1-install-page.png)

#### Step 2: Install in Test Mode

If you haven't installed the app in test mode yet, click **Install app**:

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

#### Step 3: Continue Installation

Click **Continue** to proceed:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe-test/step-3-continue.png)

#### Step 4: Reveal Your API Keys

Click **Reveal test key** to view your test mode API keys:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe-test/step-4-reveal-api-key.png)

#### Step 5: Copy Your Test Keys

Copy both the **Publishable Key** and **Secret Key**:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/stripe-test/step-5-copy-api-key.png)

#### Step 6: Configure Superwall

Paste both keys into the Sandbox Configuration fields in Superwall, then **click** on the **Update Configuration** button.

This section should say "Configured" at the top right if setup was successful.

### iOS configuration

Superwall uses the details here to handle deep links back to your app after a purchase occurs. **All of this information is required.**

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

1. **Apple Custom URL Scheme:** Add your app's custom URL scheme. If you haven't set on up, read [here for instructions](/docs/sdk/quickstart/in-app-paywall-previews).
2. **Apple App ID:** Your iOS app's ID. If you're unsure of your app's ID, you find it in **[App Store Connect](https://appstoreconnect.apple.com) -> Select your App -> General -> App Information -> Apple ID**:

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

3. **Bundle ID:** Your iOS app's bundle ID. You can find this in Xcode -> Targets -> General -> Identity -> Bundle Identifier.
4. **Team ID:** The team ID that your iOS app belongs to. To find this, visit **[Apple Developer](https://developer.apple.com) -> Account -> Membership details -> Team ID**. It's obscured here, but it'll be where the arrow points in the image below:

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

### Confirm setup

Once you've filled out all of these fields, you should see **Configured** for each section:

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

Next, you'll need to create some products in Stripe.