# 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/ # Why Are Users Still Seeing a Removed Paywall? Troubleshoot why some users continue to see a paywall that you have removed from all campaigns, and learn how to reset sticky assignments. ## Symptoms * A user purchases through or sees a paywall that no longer exists in any active campaign. * You replaced an old paywall with a new one, but some users still see the old version. * 100% of users should be seeing a new paywall, yet reports of the old paywall persist. ## Cause Superwall uses **sticky assignments** to ensure consistent user experiences during experiments. When a user is first assigned to a paywall variant, that assignment is stored on the server and persists indefinitely. This means: * Removing a paywall from a campaign does not automatically clear existing assignments. * Users who were previously assigned to the old paywall will continue to see it, even if it is no longer attached to any audience. * Changing presentation percentages or swapping paywalls only affects **new users** who have not yet been assigned. This behavior is intentional. It preserves experiment integrity and allows you to keep existing users on old pricing while testing new pricing with new users. However, it can be surprising when you want all users to see a new paywall immediately. > **Note:** Calling `Superwall.shared.reset()` clears on-device data but does **not** clear server-side assignments. The old assignment will be restored the next time the user triggers the placement. ## Solution To force all previously-assigned users onto your new paywall, you need to reset the assignments in the dashboard. ### Open the campaignGo to **Campaigns** in the Superwall dashboard and select the campaign where the old paywall was previously configured.### Navigate to the audience's experimentClick the **Paywalls** tab for the relevant audience. You should see the old paywall variant listed, possibly with a count of assigned users still shown next to it.### Reset the assignmentsClick the **refresh icon** next to the assignment count for the old paywall variant. This clears all stored assignments for that variant, forcing those users to be reassigned based on your current campaign configuration the next time they trigger the placement. > **Warning:** Resetting assignments also resets the experiment stats for that audience. If you need to preserve metrics, consider setting the old paywall's presentation percentage to 0% instead of resetting, then allowing new assignments to naturally flow to the new paywall. ## Preventing This in the Future When replacing a paywall in a campaign, keep these points in mind: * **Swap, then reset.** After adding the new paywall and removing the old one, reset assignments so existing users are reassigned. * **Use presentation percentages.** If you want a gradual rollout, set the old paywall to 0% and the new one to 100%. New users will see the new paywall, but existing users will keep their current assignment until you reset. * **Remove vs. reset.** Removing a paywall from an audience does not reset its assignments. You must explicitly reset assignments to clear them.