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

# Superwall

The shared instance of Superwall that provides access to all SDK features.

> **Note:** You must call [`configure()`](/docs/android/sdk-reference/configure) before accessing `Superwall.instance`, otherwise your app will crash.

## Purpose

Provides access to the configured Superwall instance after calling [`configure()`](/docs/android/sdk-reference/configure).

## Signature

```kotlin
companion object {
    val instance: Superwall
}
```

```java
// Java
public static Superwall getInstance()
```

## Parameters

This is a companion object property with no parameters.

## Returns / State

Returns the shared `Superwall` instance that was configured via [`configure()`](/docs/android/sdk-reference/configure).

## Usage

Configure first (typically in Application class):

```kotlin
class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        Superwall.configure(
            application = this,
            apiKey = "pk_your_api_key"
        )
    }
}
```

Then access throughout your app:

```kotlin
Superwall.instance.register("feature_access") {
    // Feature code here
}
```

Set user identity and attributes:

```kotlin
Superwall.instance.identify("user123")

Superwall.instance.setUserAttributes(mapOf(
    "plan" to "premium",
    "signUpDate" to System.currentTimeMillis()
))
```

Reset the user:

```kotlin
Superwall.instance.reset()
```

> **Note:** Avoid calling `Superwall.instance.reset()` repeatedly. Resetting rotates the anonymous user ID, clears local paywall assignments, and requires the SDK to re-download configuration state. Only trigger a reset when a user explicitly logs out or you intentionally need to forget their identity. See [User Management](/docs/android/quickstart/user-management) for more guidance.

Set delegate:

```kotlin
Superwall.instance.delegate = this
```

Consume a purchase (2.6.2+):

```kotlin
// Using coroutines
lifecycleScope.launch {
    val result = Superwall.instance.consume(purchaseToken)
    result.fold(
        onSuccess = { token ->
            println("Purchase consumed: $token")
        },
        onFailure = { error ->
            println("Failed to consume: ${error.message}")
        }
    )
}

// Using callback
Superwall.instance.consume(purchaseToken) { result ->
    result.fold(
        onSuccess = { token ->
            println("Purchase consumed: $token")
        },
        onFailure = { error ->
            println("Failed to consume: ${error.message}")
        }
    )
}
```

Show an alert over the current paywall (2.5.3+):

```kotlin
Superwall.instance.showAlert(
    title = "Important Notice",
    message = "Your subscription will renew soon",
    actionTitle = "View Details",
    closeActionTitle = "Dismiss",
    action = {
        // Handle action button tap
        navigateToSubscriptionSettings()
    },
    onClose = {
        // Handle close/dismiss
        println("Alert dismissed")
    }
)
```

Set integration attributes for analytics (2.5.3+):

```kotlin
import com.superwall.sdk.models.attribution.AttributionProvider

Superwall.instance.setIntegrationAttributes(
    mapOf(
        AttributionProvider.ADJUST to "adjust_user_id_123",
        AttributionProvider.MIXPANEL to "mixpanel_distinct_id_456",
        AttributionProvider.META to "meta_user_id_789",
        AttributionProvider.GOOGLE_ADS to "google_ads_id_101",
        AttributionProvider.GOOGLE_APP_SET to "google_app_set_id_202",
        AttributionProvider.APPSTACK to "appstack_user_id_303"
    )
)
```

## Observe customer info (2.6.6+)

Superwall now exposes purchase history and entitlement snapshots via a `StateFlow<CustomerInfo>`. Each emission contains merged device, web, and external purchase controller data so you can react to subscription changes without wiring up your own polling layer.

```kotlin
lifecycleScope.launch {
  Superwall.instance.customerInfo.collect { info ->
    val activeProductIds = info.activeSubscriptionProductIds
    val activeEntitlementIds = info.entitlements
      .filter { it.isActive }
      .map { it.id }

    updateUi(
      subscriptions = activeProductIds,
      entitlements = activeEntitlementIds
    )
  }
}
```

Need an immediate snapshot (for example during cold start)? Call `Superwall.instance.getCustomerInfo()` to synchronously read the latest cached value, or wire both together:

```kotlin
val cachedInfo = Superwall.instance.getCustomerInfo()
render(cachedInfo)

lifecycleScope.launch {
  Superwall.instance.customerInfo.collect { render(it) }
}
```

Pair the flow with [`SuperwallDelegate.customerInfoDidChange(from:to:)`](/docs/android/sdk-reference/SuperwallDelegate#customerinfodidchangefrom-customerinfo-to-customerinfo) when you need to mirror changes into analytics.

Java usage:

```java
// Access the instance
Superwall.getInstance().register("feature_access", () -> {
    // Feature code here
});

// Set user identity
Superwall.getInstance().identify("user123");
```