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

# How do I migrate to Superwall from another provider?

Guide for migrating from Adapty, Qonversion, Glassfy, or other subscription SDKs to Superwall

# How do I migrate to Superwall from another subscription provider?

If you're currently using a subscription management provider like Adapty, Qonversion, Glassfy, or another SDK and want to migrate to Superwall, here's what you need to know.

## Will My Existing Subscribers Keep Their Access?

**Yes.** Superwall reads subscription status directly from the device's App Store (iOS) or Google Play (Android) records. This means:

* Existing subscribers are automatically recognized when you switch SDKs
* No manual migration of subscription data is required
* Users won't experience any interruption to their access

When a user opens your app with the new Superwall SDK, their active subscriptions are detected automatically, regardless of which SDK was used to originally make the purchase.

## What Gets Migrated Automatically

| Data                                             | Migrated?                             |
| ------------------------------------------------ | ------------------------------------- |
| Active subscription status                       | ✅ Yes - read directly from the device |
| Entitlement access                               | ✅ Yes - based on active subscriptions |
| Cross-device sync (same Apple ID/Google account) | ✅ Yes                                 |

## What Does NOT Migrate

| Data                                     | Migrated?                               |
| ---------------------------------------- | --------------------------------------- |
| Historical analytics and metrics         | ❌ No                                    |
| Paywall designs and configurations       | ❌ No - must be recreated in Superwall   |
| A/B test history and experiment data     | ❌ No                                    |
| Custom user attributes from previous SDK | ❌ No - must be re-set via Superwall SDK |

## Re-setting Custom User Attributes

Superwall reads subscription state directly from Apple and Google, so transaction history does not need to be migrated. Your own user metadata can be added as user attributes. The original transaction ID is a stable key that bridges a returning subscriber back to their record in your backend.

The flow:

### Read the original transaction ID on deviceOn iOS, use StoreKit 2's `Transaction.currentEntitlements` and read `transaction.originalID`. On Android, use the Play Billing `purchaseToken`.```swift
import StoreKit

func fetchOriginalTransactionID() async -> String? {
  for await result in Transaction.currentEntitlements {
    guard case .verified(let transaction) = result else { continue }
    return String(transaction.originalID)
  }
  return nil
}
```### Look up the user in your backendSend the original transaction ID to your backend, which returns a stable `userId` and any metadata you want exposed to Superwall (plan tier, signup date, referrer, etc.).### Identify, then set attributesCall `identify` first so the attributes attach to the right user.```swift
Superwall.shared.identify(userId: userId)
Superwall.shared.setUserAttributes([
  "plan_tier": "pro",
  "signup_date": "2024-01-15",
  "referrer": "appstore_search"
])
```

> **Note:** `setUserAttributes` merges with existing attributes rather than replacing them. Pass `nil` for a key to remove it.

> **Warning:** A few things to watch for:- Always call `identify` before `setUserAttributes`, otherwise attributes attach to the anonymous user.
> - On a fresh install before a restore, `currentEntitlements` may be empty.
> - Sandbox and production original transaction IDs differ.
> - With Family Sharing, the original transaction ID belongs to the original purchaser, not the family member.

Run this on app launch (after StoreKit hydrates), after a successful purchase, and after a restore. It is safe to call every launch since `identify` is idempotent.

## Migration Steps

1. Remove your current subscription SDK from your project
2. Follow the [Superwall installation guide](/docs/getting-started-with-our-sdks) for your platform

## Troubleshooting

### Subscription status not detected

If an existing subscriber isn't being recognized:

1. Have them tap "Restore Purchases" on any paywall
2. Ensure they're signed into the same App Store/Google Play account used for the original purchase
3. Check that the subscription hasn't expired