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

# Multiple Choice

Capture user selections with multiple choice elements for branching, personalization, and data collection.

The multiple choice element presents a set of options for users to select from. It is commonly used in onboarding flows to gather preferences, capture survey responses, or enable [branching](/docs/dashboard/dashboard-creating-flows/linking-pages) based on user input.

### Adding a multiple choice element

To add a multiple choice element:

1. In the left sidebar, click **+** to add a new element.
2. Choose **Multiple Choice** under the "Onboarding" header.

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/component_add_mc.jpg)

A multiple choice component has configuration options to add items, randomize ordering, and more. Select it from the sidebar, and you'll see these options on the right sidebar:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/comps_mc_props.jpg)

### Selection mode

You can configure whether users select one option or multiple:

* **Single-select:** Users pick one option. The selection replaces any previous choice.
* **Multi-select:** Users can pick multiple options. All selections are stored.

### Randomize order

Enable **Randomize order** to shuffle the options each time the element appears. This is useful for surveys where you want to reduce selection bias from item ordering.

### Items

Each choice has two parts:

* **Label:** The text users see (e.g., "Grow subscriptions").
* **Value:** The internal value stored when selected (e.g., `goal_grow`).

Keep values short and consistent. Use lowercase letters and underscores for readability (e.g., `preferred_plan`, `user_goal`).

To add more choices, click **+ Add** in the component editor. You can reorder choices by dragging them.

### Using selections

Any multiple choice item is available as a variable. You can view variables either from the left side [variables](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-variables) menu, or via the floating toolbar. Either case, it's exposed via **Element -> Multiple Choice**.

Two variables are available for each multiple choice element:

* **`selectedValue`:** The programmatic value of the selected choice (e.g., `goal_grow`). Use this for routing conditions, storing as user attributes, or any logic that depends on a stable internal value.
* **`selectedLabel`:** The display label of the selected choice (e.g., "Grow subscriptions"). This is useful for showing the user's selection back to them in text on a later page. If localization is active, `selectedLabel` returns the translated label for the user's locale.

When a user makes a selection, these variables can be used in several ways:

* **Routing conditions:** Branch the flow based on what the user selected. See [branching](/docs/dashboard/dashboard-creating-flows/linking-pages#branching).
* **User attributes:** Store the selection as a user attribute for later personalization or analytics.
* **Dynamic values:** Reference the selection in text elsewhere on the page or in later pages.

### Using selections for branching

Multiple choice is the primary way to enable conditional branching in flows. After a user selects an option, you can route them to different pages based on their choice.

For example, if you ask "What is your primary goal?" with options like "Grow subscriptions" and "Reduce churn," you can send each group to a tailored page.

See [Linking Pages](/docs/dashboard/dashboard-creating-flows/linking-pages) for detailed branching setup.

### Localization

Multiple choice labels can be localized just like text elements. When you add a language in the [localization panel](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-localization), choice labels are included alongside your other translatable strings. This means:

* **AI Localize** translates choice labels automatically with the rest of your text.
* **CSV export/import** includes choice labels as rows, so your translation workflow covers them.
* **Missing translation filters** account for choice labels, so you can spot untranslated options.
* **Outdated detection** flags choice labels when the base text changes after translation.

When a user makes a selection while localization is active, the `selectedLabel` variable returns the translated text for their locale.

> **Tip:** Multiple choice elements work in both standalone paywalls and multi-page flows. In flows, they unlock branching. In paywalls, they can capture preferences before purchase.