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

# Priority Placements

Preload your most important campaign's paywalls before the rest of your app's campaigns.

By default, Superwall's SDK preloads every paywall attached to your campaigns when the app launches. For most apps, this works seamlessly. But if you have a paywall that needs to appear *immediately* — like an onboarding paywall shown right at first launch — you can tell the SDK to preload that campaign's paywalls first.

That's what **Priority Placements** do. This feature is also referred to as **prioritized placements** or **prioritized campaign preloading**. When you mark a campaign as prioritized, the SDK fetches and caches that campaign's paywalls before anything else. Other campaign paywalls are still preloaded afterward in the background.

> **Note:** Only **one campaign per app** can be prioritized at a time. If you prioritize a new campaign, the previously prioritized one is automatically deprioritized.

## When to use it

Prioritizing a campaign is most useful when:

* **You show a paywall on first launch or during onboarding** — the paywall needs to be ready the moment the user hits the placement, with zero loading delay.
* **A placement is triggered very early in a session** — such as `session_start` or `app_open` — and you want to guarantee the paywall appears instantly.
* **You have many campaigns** and want to ensure one specific campaign's paywalls take precedence during preloading.

If your app only has a few campaigns, preloading happens quickly enough that you likely won't need this. It's most impactful when you have several campaigns and want to control the order they load.

## How to prioritize a campaign

In the campaign editor, look for the **flag icon** next to the **Placements** header:

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

Click the flag to prioritize the campaign. The flag turns green to indicate the campaign is now prioritized. The dashboard describes this action as prioritizing campaign preloading.

To deprioritize, click the green flag again — it will revert to its default state.

### Switching between campaigns

If another campaign is already prioritized and you click the flag on a different campaign, a confirmation dialog will appear:

> **Switch prioritized campaign?**
> "\[Other campaign name]" is currently prioritized. Only one campaign can be prioritized at a time. Switching will deprioritize it.

Confirm to switch, or cancel to keep the current priority.

## How it works under the hood

When the SDK fetches its configuration and sees a prioritized campaign:

1. **Phase 1 — Prioritized preload:** The SDK identifies all paywalls belonging to the prioritized campaign and preloads them first.
2. **Phase 2 — Remaining preload:** After a 5-second delay, the SDK preloads all remaining campaign paywalls in the background.

This two-phase approach ensures the most important paywalls are cached and ready before others, without skipping preloading for the rest of your campaigns. The prioritized campaign's paywalls will be ready to present with no loading time, while other paywalls continue loading in the background.

> **Tip:** Prioritization only affects *preload order* — it does not change how placements, audiences, or experiments work. Your campaign logic stays exactly the same.

## SDK version requirements

Priority Placements require the following minimum SDK versions:

| SDK          | Minimum version     | Notes                                                                                                       |
| ------------ | ------------------- | ----------------------------------------------------------------------------------------------------------- |
| iOS          | **4.14.0**          | Full support.                                                                                               |
| Android      | **2.7.10**          | Full support.                                                                                               |
| Flutter      | **2.4.12**          | Full support via bundled iOS SDK 4.14.2 and Android SDK 2.7.11. iOS-only support started in Flutter 2.4.11. |
| Expo         | **1.0.11**          | Full support via bundled iOS SDK 4.14.1 and Android SDK 2.7.11. iOS-only support started in Expo 1.0.8.     |
| React Native | *Not yet supported* | The current React Native SDK bundles native SDK versions that predate prioritized campaign preloading.      |

> **Note:** Priority Placements are fully backward-compatible. Older SDK versions ignore the prioritization flag and preload all paywalls in the default order.