# 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/ # Connect an Agent with MCP Connect Claude Code, Codex, Cursor, or another MCP-compatible agent to the paywall currently open in the Superwall editor. Editor MCP lets an external AI agent control the paywall currently open in your browser. Use it when you want to keep working in Claude Code, Codex, Cursor, or another MCP-compatible agent while giving that agent live access to the editor. ![Editor MCP connection panel showing install options and a pairing code](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/paywall-editor-agent-connect.jpg) > **Note:** Editor MCP is different from the [Superwall MCP](/docs/dashboard/guides/superwall-mcp). The Superwall MCP manages account resources such as projects, applications, campaigns, products, and paywalls. Editor MCP controls the one paywall editor session open in your browser. ## Connect an agent 1. Open the paywall you want the agent to edit. 2. Open **AI Chat** in the editor sidebar. 3. Click the agent connection pill. 4. Choose **Skill** or **MCP**. 5. Copy the install command shown in the editor. 6. Paste the pairing prompt into your agent. If you choose **Skill**, the editor shows: ```bash npx skills add superwall/skills ``` Then paste the generated prompt into your agent: ```txt Connect to the Superwall editor using the skill with pairing code: XXXX-XXXX-XXXX ``` If you choose **MCP**, select your client first. The editor generates the right command or configuration for Claude Code, Codex, Cursor, or another MCP client. Use the command shown in the editor because it includes the correct Editor MCP URL for your environment. The MCP prompt looks like this: ```txt Connect to the superwall-editor MCP with pairing code: XXXX-XXXX-XXXX ``` ## Connected state After the agent attaches, the connection pill shows the connected client and tool activity. For example, this is what it looks like when an agent uses the pairing code to connect to the editor: ![Example agent connecting to the Superwall editor over MCP](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/ai_mcp_claude_connecting.jpg) After the connection completes, the editor shows the attached client and recent tool activity. ![Editor MCP connection panel showing a connected agent and tool activity](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/paywall-editor-agent-connected.jpg) The editor keeps the browser session open while the page is open. From the connection panel you can: * **Disconnect Agent:** Release the current agent while keeping the editor session available for another pairing. * **End Session:** Close the browser editor session and invalidate the pairing code. Only one external controller can be attached to an editor session at a time. Disconnect the current agent before attaching a different one. ## What agents can do Attached agents receive the editor's live tool list. The exact list can change as the editor evolves, but today agents can: * **Inspect and edit the paywall:** Agents can read the current paywall, selected elements, children, navigation pages, computed styles, and screenshots. They can then update text, styles, names, node order, hierarchy, or write native paywall HTML directly into the editor. * **Work with content and resources:** Agents can upload image and video assets, create and edit products, manage style tokens, and update variables, variable values, and dynamic values. They can also add localization languages, run AI localization, and configure trial-started notifications. * **Configure behavior and advanced flows:** Agents can add or clear tap behaviors such as purchase, restore, close, open URL, set state, select product, navigate page, request permission, request callback, scroll, focus input, delay, animation, and haptics. They can also edit routes, transitions, branches, advanced native elements, and use search or find/replace to make broader changes. ## Session limits Editor MCP uses pairing codes and session tokens rather than your account-level MCP OAuth flow. | Limit | Behavior | | ----------------------- | -------------------------------------------------------------------------------------- | | Pairing code lifetime | Pairing codes expire after 10 minutes. | | Editor session lifetime | Browser editor sessions expire after 24 hours. | | Tool timeout | Tool calls time out after 30 seconds. | | Browser reconnect | The browser has a short reconnect window if the page refreshes or briefly disconnects. | | Failed pair attempts | Too many wrong pairing codes end the session. | If a pairing code expires, open the connection panel again and use the new code. ## Troubleshooting ### The agent cannot attach Check that the paywall editor tab is still open, the pairing code has not expired, and the agent is using the prompt from the current connection panel. ### The session says another controller is connected Only one controller can be attached. Click **Disconnect Agent**, then attach the new agent with the latest pairing code. ### Tool calls fail after a browser refresh Wait a moment for the editor to reconnect. If calls still fail, end the session and create a new connection from the editor. ### The agent edited the wrong thing Use the editor's undo and history tools to review or roll back changes. Select the exact element you want changed before sending the next prompt so the agent receives that selection as context. ## Related * [AI Chat Builder](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-ai-chat): Use Superwall's built-in chat builder inside the editor. * [Superwall MCP](/docs/dashboard/guides/superwall-mcp): Manage account resources from external AI tools. * [Superwall Skill](/docs/dashboard/guides/superwall-skill): Give coding agents Superwall docs, API helpers, and SDK integration guidance.