# 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/ # Request permissions from paywalls Trigger Android runtime permission dialogs directly from a Superwall paywall action. ## Overview Use the **Request permission** action in the paywall editor when you want to gate features behind Android permissions without bouncing users back to native screens. When the user taps the element, the SDK: * Presents the corresponding Android system dialog. * Emits analytics events (`permission_requested`, `permission_granted`, `permission_denied`). * Sends the result back to the paywall so you can branch the UI (for example, swap a checklist item for a success state). ## Add the action in the editor 1. Open your paywall, select the button (or any element) that should prompt the permission, and set its action to **Request permission**. 2. Choose the permission you want to request. You can wire multiple buttons if you need to prime several permissions in a single flow. 3. Republish the paywall. No extra SDK configuration is required beyond having the proper `AndroidManifest.xml` entries. ## Declare the permissions in `AndroidManifest.xml` | Editor option | `permission_type` sent from the paywall | Required manifest entries | Notes | | --------------------- | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- | | Notifications | `notification` | `` (API 33+) | Devices below Android 13 do not require a runtime permission; the SDK reports `granted` immediately. | | Location (Foreground) | `location` | `` | Also covers coarse location because FINE implies COARSE. | | Location (Background) | `background_location` | Foreground entry above **and** `` (API 29+) | The SDK first ensures foreground access, then escalates to background. | | Photos / Images | `read_images` | `` (API 33+) or `READ_EXTERNAL_STORAGE` for older OS versions | Automatically picks the right permission at runtime. | | Videos | `read_video` | `` (API 33+) or `READ_EXTERNAL_STORAGE` pre-33 | | | Contacts | `contacts` | `` | | | Camera | `camera` | `` | | | Microphone | `microphone` | `` | Added in 2.6.8. | If a manifest entry is missing—or the permission is unsupported on the current OS level—the SDK responds with an `unsupported` status so you can show fallback copy. ## Analytics and delegate callbacks Forward the new events through `SuperwallDelegate.handleSuperwallEvent` to keep your analytics platform and feature flags in sync: ```kotlin override fun handleSuperwallEvent(eventInfo: SuperwallEventInfo) { when (val event = eventInfo.event) { is SuperwallEvent.PermissionRequested -> { analytics.track("permission_requested", mapOf( "permission" to event.permissionName, "paywall_id" to event.paywallIdentifier )) } is SuperwallEvent.PermissionGranted -> { FeatureFlags.unlock(event.permissionName) } is SuperwallEvent.PermissionDenied -> { Alerts.showPermissionDeclinedSheet(event.permissionName) } else -> Unit } } ``` You can also log the newer [`customerInfoDidChange`](/docs/android/sdk-reference/SuperwallDelegate#customerinfodidchangefrom-customerinfo-to-customerinfo) callback if the permission subsequently unlocks new paywalls that grant entitlements. ## Status values returned to the paywall The paywall receives a `permission_result` web event with: * `granted` – The system dialog reported success (or no dialog was needed). * `denied` – The user denied the request or previously denied it. * `unsupported` – The platform or manifest doesn't allow the requested permission. Use Liquid or custom Javascript inside the paywall to branch on these statuses—for example, replace a “Grant notification access” button with a checkmark when the result equals `granted`. ## Troubleshooting * Seeing `unsupported`? Double-check the manifest entries above and confirm the permission exists on the device's API level (for example, notification permissions only apply on Android 13+). * Nothing happens when you tap the button? Ensure the action is set to **Request permission** in the released paywall version. * Want to provide next steps after a denial? Listen for `PermissionDenied` in your delegate to deep-link users into Settings or show educational copy.