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

# Linking Pages

Connect pages with routes, configure animations, and set up conditional branching.

Linking pages is how you define the path through your flow. You'll connect pages using nodes in the Canvas view, and each connection (route) can have its own animation and conditions.

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

### Creating connections

In Canvas view, you'll see nodes on the edges of each page. These are your connection points.

To link two pages:

1. Click the node on the edge of the source page.
2. Drag to the destination page.
3. Release to create the route.

The first page in your flow should connect to the **flow entry point**, which is the starting node that appears in the Canvas. This marks where users begin:

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

### The edge toolbar

When you click on a route (the line connecting two pages), an edge toolbar appears with several options:

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

1. **Animation:** Choose a transition style for this route (see below).
2. **Add condition:** Opens a help dialog explaining how to set up conditional branching on this route.
3. **Duplicate:** Duplicates the source destination page and then creates a branch between them.
4. **Delete:** Remove the connection between two pages.

### Animation styles

Each route has an animation style that controls how the transition looks when users move between pages.

To change an animation:

1. Click on a route (the line connecting two pages).
2. In the edge toolbar that appears, select an animation style:

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

Available animations:

* **Push**: Slides the new page in from the right.
* **Fade**: Crossfades between pages.
* **Slide**: Smooth horizontal transition, like scrolling through a carousel.
* **Fade & Slide**: Combines a fade with a slide transition.
* **None**: Instant transition with no animation.

### Unlinked pages

Pages that aren't connected to the flow show a label indicating they're unlinked. These pages won't appear in the user's journey until you connect them:

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

Unlinked pages are useful for drafts you're still working on, pages you want to keep but aren't using yet, or testing different versions before connecting them.

### Branching

Routes can be conditional, meaning users can see different pages based on their input or attributes. This is the core of personalized flows. You might change the page that shows next based off a multiple choice answer, or certain component tapped, etc.

To add branching:

1. Connect a route in the Canvas to a page.
2. Then, from the same source page, click and drag to add *another* route to a different destination page.
3. Then, configure the rules from the resulting popup.

In this example, a route is already in place to go from the left-most page to the middle one. Adding another route from the same page to a new page creates a branch. The Flow editor recognizes that the route can now end up in more than one place:

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

For example, if you have a multiple choice element asking about user goals:

* Route 1: If user selected "Grow subscriptions" → Go to Growth Tips page.
* Route 2: If user selected "Reduce churn" → Go to Retention Tips page.
* Default route: Go to General Tips page.

### Editing branch rules

A branch dictates navigation by its *routing conditions*, and these are edited once a branch is made:

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

If you are familiar with [dynamic values](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-dynamic-values), rules are created exactly the same way.

These routing conditions can be based on things like:

* **User attributes:** Properties you've set on the user (e.g., subscription status, country).
* **User input:** Selections from Flow Elements like multiple choice or text entry.
* **Combinations:** Use AND/OR logic to combine multiple conditions.

When building conditions, you can use operators like **equals**, **not equals**, **contains**, and more. Two additional operators are available for checking whether a value exists at all:

* **is empty:** True when the value is not set (null, undefined, or an empty string). Useful for checking if a user hasn't made a selection yet or if an input field was skipped.
* **is not empty:** True when the value has any content. Useful for branching only after a user has provided input.

These operators don't require a comparison value. They check the variable itself.

### Multiple choice branch example

Here's an example using a multiple choice component to create a branch. When choosing a condition, in the popup select **Element** and choose the multiple choice response to dictate the flow (this assumes you have added a multiple choice component on the flow already):

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

Interactive elements that can control routing conditions will be available under the **Element** category when editing the rule. In the screenshot above, it's shown since a multiple choice component is used in the pages involved in the branch. You can see that here:

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

The multiple choice responses will automatically populate in the rule editor too:

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

When you are done, **click** on the **save** button and your branch will be saved. The canvas will update to reflect the branch:

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

To **edit** a branch, simply click on it from within the canvas to bring the rule editor back up.

### Connection warnings

The editor validates your flow connections and shows warnings when it detects potential problems. For example, if a page is connected to the next page but no element on the source page has a "Navigate Page" tap behavior, you'll see a warning indicating that the destination page may be unreachable.

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

If you see a warning, check that the source page has at least one element with a **Navigate Page** tap behavior set to **Next** so users can actually reach the connected page.

### Branching by tapped element

Sometimes you want different buttons on the same page to navigate to different destinations without a traditional condition. For example, a footer with "Continue" and "Skip Setup" buttons where each should go to a different page.

To set this up, use `navigationNode.tappedElement` as the routing condition. This lets you create a route based on which element triggered the "Navigate Page" action:

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

To configure this:

1. Create a branch from your page to multiple destinations.
2. In the rule editor, select **Element** as the condition type.
3. Choose **Navigation.tappedElement** from the dropdown.
4. Set it equal to the specific element that should trigger this route.

This approach is useful when you have multiple navigation buttons on a single page and each should lead somewhere different. The routing condition checks which button was actually tapped rather than relying on stored user input.

> **Tip:** Start simple. Get your basic flow working first, then add branching once you're comfortable with the structure.