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

# Using RevenueCat

Handle a deep link in your app and use the delegate methods to link web checkouts with RevenueCat in Flutter.

After purchasing from a web paywall, the user will be redirected to your app by a deep link to redeem their purchase on device. Please follow our [Post-Checkout Redirecting](/docs/flutter/guides/web-checkout/post-checkout-redirecting) guide to handle this user experience.

> **Note:** If you're using Superwall to handle purchases, then you don't need to do anything here.

> **Warning:** You only need to use a `PurchaseController` if you want end-to-end control of the purchasing pipeline. The recommended way to use RevenueCat with Superwall is by putting it in observer mode.

If you're using your own `PurchaseController`, you should follow our [Redeeming In-App](/docs/flutter/guides/web-checkout/linking-membership-to-iOS-app) guide.

### Using a PurchaseController with RevenueCat

If you're using RevenueCat, you'll need to follow [steps 1 to 4 in their guide](https://www.revenuecat.com/docs/web/integrations/stripe) to set up Stripe with RevenueCat. Then, you'll need to
associate the RevenueCat customer with the Stripe subscription IDs returned from redeeming the code. You can do this by extracting the ids from the `RedemptionResult` and sending them to RevenueCat's API
by using the `didRedeemLink()` delegate method:

> **Warning:** This flow is for Stripe subscriptions. Stripe one-time purchases can return Stripe Checkout session IDs through the same legacy `stripeSubscriptionIds` field, but those IDs are not Stripe subscription IDs. Handle one-time purchases with Superwall entitlements or your own backend instead of sending those IDs to RevenueCat's Stripe subscription endpoint.

```dart
import 'package:superwallkit_flutter/superwallkit_flutter.dart';
import 'package:purchases_flutter/purchases_flutter.dart';
import 'package:http/http.dart' as http;
import 'dart:convert';

class MySuperwallDelegate extends SuperwallDelegate {
  // The user tapped on a deep link to redeem a code
  @override
  void willRedeemLink() {
    print('[!] willRedeemLink');
    // Optionally show a loading indicator here
  }

  // Superwall received a redemption result and validated the purchase with Stripe.
  @override
  void didRedeemLink(RedemptionResult result) async {
    print('[!] didRedeemLink: $result');
    // Send Stripe IDs to RevenueCat to link purchases to the customer

    if (result is! RedemptionResultSuccess) {
      return;
    }

    final storeIdentifiers = result.redemptionInfo.purchaserInfo.storeIdentifiers;
    if (storeIdentifiers is! StripeStoreIdentifiers) {
      return;
    }

    // Get a list of Stripe subscription ids tied to the customer
    final stripeSubscriptionIds = storeIdentifiers.subscriptionIds;
    if (stripeSubscriptionIds.isEmpty) {
      return;
    }

    const revenueCatStripePublicAPIKey = 'strp.....'; // replace with your RevenueCat Stripe Public API Key
    final appUserId = await Purchases.appUserID;

    // In the background, send requests to RevenueCat
    for (final stripeSubscriptionId in stripeSubscriptionIds) {
        try {
          final url = Uri.parse('https://api.revenuecat.com/v1/receipts');
          final response = await http.post(
            url,
            headers: {
              'Content-Type': 'application/json',
              'Accept': 'application/json',
              'X-Platform': 'stripe',
              'Authorization': 'Bearer $revenueCatStripePublicAPIKey',
            },
            body: jsonEncode({
              'app_user_id': appUserId,
              'fetch_token': stripeSubscriptionId,
            }),
          );

          if (response.statusCode != 200) {
            throw Exception(
              'RevenueCat responded with ${response.statusCode}: ${response.body}',
            );
          }

          final json = jsonDecode(response.body);
          print('[!] Success: linked $stripeSubscriptionId to user $appUserId: $json');
        } catch (error) {
          print('[!] Error: unable to link $stripeSubscriptionId to user $appUserId: $error');
        }
    }

    // After all network calls complete, invalidate the cache
    try {
      final customerInfo = await Purchases.getCustomerInfo();
      
      /// If you're using Purchases.customerInfoStream, or keeping Superwall Entitlements in sync
      /// via RevenueCat's PurchasesDelegate methods, you don't need to do anything here. Those methods will be
      /// called automatically when this call fetches the most up to date customer info, ignoring any local caches.
      
      /// Otherwise, if you're manually calling Purchases.getCustomerInfo to keep Superwall's entitlements
      /// in sync, you should use the newly updated customer info here to do so.
      
      /// You could always access web entitlements here as well
      /// final webEntitlements = Superwall.shared.entitlements?.web;
      
      // Perform UI updates, like letting the user know their subscription was redeemed
      print('[!] Customer info updated after redemption');
    } catch (error) {
      print('[!] Error fetching customer info: $error');
    }
  }
}
```

> **Note:** The example throws when RevenueCat responds with an error so you can add retries, alerts, or custom
> UI. Adapt the error-handling strategy to your networking and logging requirements.

Set up the delegate when configuring Superwall:

```dart
void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  
  await Superwall.configure('pk_your_api_key');
  
  // Set the delegate
  Superwall.shared.setDelegate(MySuperwallDelegate());
  
  runApp(MyApp());
}
```

> **Warning:** If you call `logIn` from RevenueCat's SDK, then you need to call the logic you've implemented
> inside `didRedeemLink()` again. For example, that means if `logIn` was invoked from
> RevenueCat, you'd either abstract out this logic above into a function to call again, or simply
> call this function directly.

The web entitlements will be returned along with other existing entitlements in the `CustomerInfo` object accessible via RevenueCat's SDK.

If you're logging in and out of RevenueCat, make sure to resend the Stripe subscription IDs to RevenueCat's endpoint after logging in.

### Alternative implementation using async/await properly

Here's a cleaner implementation that properly handles async operations:

```dart
class MySuperwallDelegate extends SuperwallDelegate {
  @override
  void willRedeemLink() {
    print('[!] willRedeemLink');
    // Show loading indicator
  }

  @override
  void didRedeemLink(RedemptionResult result) {
    // Don't use async here directly, spawn a separate task
    _handleRedemption(result);
  }
  
  Future<void> _handleRedemption(RedemptionResult result) async {
    if (result is! RedemptionResultSuccess) {
      print('[!] Redemption did not succeed');
      return;
    }

    final storeIdentifiers = result.redemptionInfo.purchaserInfo.storeIdentifiers;
    if (storeIdentifiers is! StripeStoreIdentifiers) {
      print('[!] Redemption did not come from Stripe');
      return;
    }

    final stripeSubscriptionIds = storeIdentifiers.subscriptionIds;
    if (stripeSubscriptionIds.isEmpty) {
      print('[!] No Stripe subscription IDs found');
      return;
    }

    const revenueCatStripePublicAPIKey = 'strp.....';
    final appUserId = await Purchases.appUserID;

    // Link each subscription to RevenueCat
    await Future.wait(
      stripeSubscriptionIds.map((stripeSubscriptionId) async {
        try {
          await _linkSubscriptionToRevenueCat(
            stripeSubscriptionId,
            appUserId,
            revenueCatStripePublicAPIKey,
          );
        } catch (e) {
          print('[!] Failed to link $stripeSubscriptionId: $e');
        }
      }),
    );

    // Refresh customer info
    try {
      await Purchases.getCustomerInfo();
      print('[!] Successfully refreshed customer info');
    } catch (e) {
      print('[!] Failed to refresh customer info: $e');
    }
  }
  
  Future<void> _linkSubscriptionToRevenueCat(
    String stripeSubscriptionId,
    String appUserId,
    String apiKey,
  ) async {
    final url = Uri.parse('https://api.revenuecat.com/v1/receipts');
    final response = await http.post(
      url,
      headers: {
        'Content-Type': 'application/json',
        'Accept': 'application/json',
        'X-Platform': 'stripe',
        'Authorization': 'Bearer $apiKey',
      },
      body: jsonEncode({
        'app_user_id': appUserId,
        'fetch_token': stripeSubscriptionId,
      }),
    );

    if (response.statusCode != 200) {
      throw Exception(
        'RevenueCat responded with ${response.statusCode}: ${response.body}',
      );
    }

    print('[!] Successfully linked $stripeSubscriptionId to $appUserId');
  }
}
```

Remember to add the `http` package to your `pubspec.yaml`:

```yaml
dependencies:
  http: ^1.1.0
  purchases_flutter: ^6.0.0
  superwallkit_flutter: ^2.4.12
```