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

# Article-Style Paywalls: Inline with Additional Plans

Embed an inline paywall in a scrollable article and optionally present a second full-screen paywall for additional plans.

Article-style paywalls let you keep readers in the flow of a long-form page while still prompting for upgrade options. You can place an inline paywall inside a scroll view, then present a second, full-screen paywall when users tap “see more plans.”

This pattern is common in paid media and magazine apps: a portion of the article is readable, the rest is blurred or gated, and a footer paywall offers an inline purchase with a “see more plans” option that opens a full-screen paywall. Check out this working example:

<div className="flex justify-center">
  
![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/article-vid-example.gif)

</div>

This guide will show you how to build this example by explaining the APIs involved, and then a full code sample. There’s also a live working example in [CaffeinePal](https://github.com/superwall/CaffeinePal/tree/using-superwall-sdk). Look at the `RecipesView` to see it in action.

## Key APIs

Use `getPaywall()` to fetch a paywall you can embed inline, and configure it with a placement so you can control which paywall variant shows from the dashboard. For more on presenting paywalls in custom presentations, check out our [blog post](https://superwall.com/blog/custom-paywall-presentation-in-ios-with-the-superwall-sdk/).

For the second paywall, trigger a custom action from the inline paywall and call `getPaywall()` again to present the full-screen option.

> **Warning:** You're responsible for removing embedded paywall views when users move on. Reusing the same `PaywallViewController` or `PaywallView` instance elsewhere can cause a crash. For UIKit, avoid mixing `register()` and `getPaywall()` when you embed paywalls.

## Presenting a second paywall

To get the inline paywall to trigger a second, full-screen paywall, create a custom action in the paywall editor in the embedded paywall. In this example, a custom action called "showFromLine" is triggered from the "or, view all plans" button:

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

Then, respond to that action in your [`SuperwallDelegate`](/docs/ios/sdk-reference/SuperwallDelegate) to retrieve the second paywall and present it. In the code below, our second paywall is normally triggered via the `showAllPlansPaywall` placement that was setup in the Superwall dashboard within a campaign:

```swift
extension MyAppLogic: SuperwallDelegate, PaywallViewControllerDelegate {
    // Custom action comes in
    func handleCustomPaywallAction(withName name: String) {
        if name == "showFromInline" {
            Task {
                await presentAllPlansPaywall()
            }
        }
    }

    // MARK: PaywallViewControllerDelegate

    func paywall(
        _ paywall: PaywallViewController,
        didFinishWith result: PaywallResult,
        shouldDismiss: Bool
    ) {
        if shouldDismiss {
            paywall.dismiss(animated: true)
        }
    }

    func paywall(
        _ paywall: PaywallViewController,
        loadingStateDidChange loadingState: PaywallLoadingState
    ) {
        // Handle loading state changes if needed
    }

    // MARK: Custom Paywall Presentation

    private func presentAllPlansPaywall() async {
        do {
            let paywallViewController = try await Superwall.shared.getPaywall(
                forPlacement: "showAllPlansPaywall",
                delegate: self
            )

            guard let windowScene = UIApplication.shared.connectedScenes.first as? UIWindowScene,
                  let rootViewController = windowScene.windows.first?.rootViewController else {
                return
            }

            var topController = rootViewController
            while let presented = topController.presentedViewController {
                topController = presented
            }

            topController.present(paywallViewController, animated: true)
        } catch let reason as PaywallSkippedReason {
            print("Paywall skipped: \(reason)")
        } catch {
            print("Error presenting paywall: \(error)")
        }
    }
}
```

This keeps the inline paywall embedded while you intentionally present the next paywall. The entire flow looks like this:

**In your dashboard**

1. Have a paywall setup for your "footer" or bottom paywall.
2. Add a custom action to it to present a second paywall over it.
3. Make sure both paywalls are active in a campaign, and remember the placements used to trigger them

**In your code**

1. Use `getPaywall` and `PaywallView` to embed the first paywall in your scrollview.
2. Users can purchase from there, or tap another button to present a second paywall.
3. Handle a custom action fired from a "View all plans" or similar button in a `SuperwallDelegate`.
4. Use `PaywallViewControllerDelegate` to manage presentation of the second one.

Here's some code to model your approach, showing the first paywall as either an overlay at the bottom or inline with scrolled content:

```swift
enum PaywallEmbedMode {
  case overlay
  case inline
}

struct ArticlePaywallDemoView: View {
  let mode: PaywallEmbedMode
  let placement: String = "getPaywallTest"

  var body: some View {
    ScrollView {
      VStack(alignment: .leading) {
        Text("How to embed a Superwall paywall alongside your own content")
          .font(.title)
        Text("By Superwall").font(.caption)
        Text("...article content...")
          .padding(.vertical, 16)

        if mode == .inline {
          paywallContent
        }
      }
      .padding()
      .overlay(alignment: .bottom) {
        if mode == .overlay {
          paywallContent
        }
      }
    }
  }

  private var paywallContent: some View {
    PaywallView(placement: placement)
      .frame(maxWidth: .infinity)
      .frame(height: 300)
  }
}
```

If you need to remove the paywall, remove the `PaywallView` from the view hierarchy and recreate it when you need to show it again.