# 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/ # How Flows are Structured Understand the key concepts of a Flow: the navigation element, pages, routes, and branching. A Flow is a collection of pages connected by routes. Unlike single paywalls, the order of pages in the sidebar doesn't determine the flow. The connections (i.e. *routes*) you create do. The Navigation element is what makes a paywall opt into becoming a Flow. To understand flows, you only need to be aware of these core concepts to get started: 1. **Navigation Component:** The base component which contains your flow. 2. **Pages:** The content of your flow, each one is housed within a central navigation component. 3. **Routes:** The user-defined ordering of how users progress through a flow. 4. **Branches:** A way to dynamically decide which route to take. > **Note:** Not all flows need to use branches. If your flow is a linear journey, then they aren't required. ### The Navigation element The Navigation element is what turns a paywall into a Flow. Without it, you have a standard paywall. With it, you unlock the Canvas view and the ability to connect pages together. ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_create_nav.jpg) To add it: 1. In the left sidebar, click **+** to add a new element. 2. Choose **Navigation** under the "Base Elements" header. Once added, you'll see your paywall appear in the Canvas view, ready to be connected to other pages. ### Pages Each page in a Flow is built the same way you build a paywall. Once you have a navigation element, adding pages to it enables the Flow editing capabilities: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_creating_pages.png) > **Tip:** A "page" here is any content you add, such a stack, into the navigation element. Each top level container creates a page in your flow. You can add elements, style them, and configure actions just like you would with any paywall. * A Flow can have as many pages as you need. * Pages that aren't connected to the flow are labeled "unlinked". * Each page can have its own products, styling, and behavior. Once you add one or more pages, the "Flow" button the floating toolbar will become active: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_create_flow_on.jpg) ### Routes Routes are the connections between pages. You create them by linking one page to another in the Canvas view. To begin, you'll **click** and **drag** from the starting point of the flow to the first page you want to use: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_creating_first_route.gif) * Each route defines how users move from one page to the next. * Routes can have different animation styles (push, fade, etc.). * The first page in your flow connects to the "flow entry point". You can control any routes animation style by clicking on it: ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_create_animation.jpg) ### Branching Routes themselves can be conditional. If you need to show different pages based on user input or attributes, you can by creating a branch. Any *route* can become a *branch*. For example: * If a user selected "Grow subscriptions" in a multiple choice element, go to Page A. * Otherwise, go to Page B. Branching is configured in the route settings, not on buttons or CTAs. This keeps your flow logic centralized and easier to maintain. ### The floating toolbar The floating toolbar has been updated to support Flows. You'll find new controls for: 1. Switching between Device view and Canvas view. 2. Fitting the viewport to fit the entire flow canvas. 3. Editing branches. 4. Toggling the mini-map. ![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/flows_create_tb.jpg) For more details, see [The Canvas](/docs/dashboard/dashboard-creating-flows/the-canvas).