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

# Stacks

From a component standpoint, stacks are the foundation of every layout. Most components and snippets will start with a stack. Under the hood, they mimic a flexbox layout.

> **Tip:** If you are new to CSS Flexbox, try out this interactive [tool](https://flexbox.help). Or, simply change the properties in the editor to see realtime changes.

### Stack Specific Properties

Stacks have unique properties:

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

* **Axis**: Determines the arrangement of items within the stack.
  1. `Horizontal`: Items are arranged left to right.
  2. `Vertical`: Items are arranged top to bottom.
  3. `Layered`: Items are stacked on top of each other.

* **Vertical**: Controls the vertical alignment of the items within the stack.
  1. `Top`: Aligns items to the top of the container.
  2. `Center`: Aligns items vertically in the center of the container.
  3. `Bottom`: Aligns items to the bottom of the container.
  4. `Stretch`: Stretches items to fill the vertical space of the container.
  5. `Baseline`: Aligns items according to their baseline.

* **Horizontal**: Controls the horizontal alignment of the items within the stack.
  1. `Left`: Aligns items to the left of the container.
  2. `Center`: Aligns items horizontally in the center of the container.
  3. `Right`: Aligns items to the right of the container.
  4. `Fill Equally`: Distributes items evenly across the container, filling the space equally.
  5. `Space Evenly`: Distributes items with equal space around them.
  6. `Space Around`: Distributes items with space around them, with half-size space on the edges.
  7. `Space Between`: Distributes items with space only between them, with no space at the edges.

* **Spacing**: Defines the amount of space between items within the stack, measured in pixels by default.

* **Wrap**: Specifies how items within the stack should behave when they exceed the container's width.
  1. `Don't Wrap`: Items remain in a single line and do not wrap onto a new line.
  2. `Wrap`: Items wrap onto the next line when they exceed the container's width.
  3. `Wrap Reverse`: Items wrap onto the previous line in reverse order.

* **Scroll**: Determines the scrolling behavior of the stack.
  1. `None`: Disables scrolling within the stack.
  2. `Normal`: Enables standard scrolling behavior.
  3. `Paging`: Enables paginated scrolling, allowing users to swipe through pages of items. See "Creating Carousels" below.
  4. `Infinite`: Endless scrolling, items clone and repeat themselves once they reach the end.

* **Snap Position**: Defines the position at which items snap into place during paging. Only relevant if `Scroll` is set to `Paging`.
  1. `Start`: Items snap to the start of the container.
  2. `Center`: Items snap to the center of the container.
  3. `End`: Items snap to the end of the container.

* **Auto Paging**: Controls whether a carousel's contents should automatically page between items. Only relevant if `Scroll` is set to `Paging`.
  1. `Disabled`: Auto paging is turned off, and items page via user interaction.
  2. `Enabled`: Auto paging is turned on and items will automatically page according to the paging delay.

* **Paging Delay**: The duration to automatically advance the slides. Only relevant if `Scroll` is set to `Paging` and `Auto Paging` is set to `Enabled`.

* **Infinite Scroll Speed**: The amount of pixels per frame that the carousel should advance. Only relevant if `Scroll` is set to `Infinite`.

To see how to use stacks for common designs, check out these pages:

* [Carousel](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-carousel-component)
* [Autoscrolling](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-autoscroll-component)
* [Slides](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-slides-component)
* [Navigation](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-navigation-component)