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

# Paywall Not Showing

## Issue

Any unexpected paywall presentation behavior, including:

* Paywall is not showing when it should
* Paywall is showing when it shouldn't
* Paywall is showing but loading indefinitely

## Debugging Steps

### Check your subscription status logic.

> **Info:** This only applies if you're using a PurchaseController. If you're using Superwall to handle all purchase logic (the default) you can skip this

* Important: When using a `PurchaseController` (such as with RevenueCat), the subscription status starts as `.unknown` by default. Your app must manually set it to either `.active()` or `.inactive()` on app launch - the SDK will not automatically determine this for you. Paywalls will not show if the subscription status is unknown

### Test device considerations.

If you’ve previously purchased a subscription, the paywall won’t show again. On iOS, if you’re using a local StoreKit config file, delete and reinstall the app to reset the device’s subscription state.

When basic app deletion doesn't resolve test subscription persistence, consider the following:

* Cross-account subscription persistence: Test subscription status persists at the device level even when switching between different app accounts within the same app. If you've made a test purchase on one account, it affects paywall presentation for all accounts on that device.

* Hidden test purchases: Test purchases made through StoreKit may not appear in your iPhone's standard Settings > Apple ID > Subscriptions list, making them impossible to cancel manually. This is normal behavior for sandbox/test purchases.

* Alternative reset methods: For production App Store testing when app deletion isn't sufficient, use a different physical device or fresh simulator instance that hasn't made the test purchase.

### Review your campaign configuration.

Confirm your placement name is spelled correctly and that all necessary properties are passed to match the audience filter. Also check for any holdout groups that might block the paywall.

If you've recently updated your campaign, make sure to quit and re-open your app to fetch the latest configuration

### Specific Campaign Configuration Considerations

Be aware of the default entitlement settings for new campaigns. By default, campaigns are set to "For Unsubscribed Users Only" in the entitlements section. If you want to test paywalls while having an active subscription, change the entitlement dropdown to "For All Users."

When encountering console errors, specifically "Skipped paywall presentation: no\_rule\_match," it indicates the user doesn't match the audience filters for that placement. This helps distinguish between configuration issues versus subscription status problems.

For `noAudienceMatch` errors, systematically verify that your audience configuration includes the current user's specific attributes, subscription status, and any custom properties you're tracking.

### Verify product configuration.

If your paywall references unavailable or invalid product identifiers, you’ll see a console error. When using a StoreKit file, be sure to add your products before testing paywall presentation.

## Paywall Loading Indefinitely

Your paywall shows a white screen with gray placeholder boxes that never finish loading. This typically occurs on iOS when using Apple's `WKAppBoundDomains` feature in your app's `Info.plist`.

### Cause

WKAppBoundDomains is an iOS 14+ privacy feature that restricts WebView capabilities. When enabled, it disables WebView message handlers that Superwall requires for bridge communication between the native SDK and the paywall content. You may see this warning in the WebView console:

```
[Warning] [WebKit] Unable to send message - WebKit message handler not available.
```

### Solution

Remove the `WKAppBoundDomains` key from your app's `Info.plist` file:

```
<!-- Remove this section -->
<key>WKAppBoundDomains</key>
<array>
    <string>example.com</string>
</array>
```

After removing this configuration, rebuild and relaunch your app. The paywall should now load correctly. If you require WKAppBoundDomains for other parts of your app, please contact Superwall support to discuss alternative integration options.