# 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/ # Superwall Skill Give AI coding agents up-to-date Superwall docs, API access, and step-by-step SDK integration guides using the Superwall Skill. The [Superwall Skill](https://github.com/superwall/skills) is a set of [Agent Skills](https://agentskills.io) that give AI coding agents everything they need to work with Superwall. It has access to live documentation, API access, dashboard information, and guided SDK integration flows for every platform. > **Note:** This is different from [Superwall Agents](/docs/agents), which is the Superwall AI workspace for chats, analysis, automations, webhooks, and hosted machine work. The Superwall Skill is for giving AI coding agents Superwall docs, API access, and SDK guidance. The Skill can perform all of the tasks the [Superwall MCP](/docs/dashboard/guides/superwall-mcp) can, and is recommended when you are working in an external coding agent. > **Tip:** The Skill can also connect to a live paywall editor session. Open **AI Chat** in the paywall editor, expand the agent connection panel, choose **Skill**, install the Skill if needed, then paste the pairing-code prompt into your agent. See [Editor MCP](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-mcp) for the full flow. ## Installation Install with the [skills.sh](https://skills.sh) CLI. This works with any agent that supports skills, including Claude Code, Cursor, and Codex. Install all skills (recommended): ```bash npx skills add superwall/skills ``` Or install individual skills: ```bash # General skill (docs, API, dashboard links) npx skills add superwall/skills --skill superwall # Platform-specific quickstart npx skills add superwall/skills --skill superwall-ios-quickstart npx skills add superwall/skills --skill superwall-android-quickstart npx skills add superwall/skills --skill superwall-flutter-quickstart npx skills add superwall/skills --skill superwall-expo-quickstart ``` ## What's included The Superwall Skill is made up of a general-purpose skill and platform-specific quickstart skills. ### General skill The `superwall` skill gives agents access to: * **Live documentation**: Agents fetch docs on demand from `llms.txt` and per-page markdown endpoints, so they always have the latest information. * **API access**: A bundled `sw-api.sh` helper wraps the Superwall V2 API. Agents can list projects, inspect applications, and manage resources directly from the terminal. * **Dashboard links**: URL patterns for every dashboard page, so agents can link you to the right place (settings, campaigns, paywalls, users, and more). * **SDK source cloning**: Agents can clone SDK repos locally to trace internal behavior when debugging. * **Webhook and integration catalog**: Fetched live from the Superwall integrations endpoint. * **Editor pairing**: Agents can attach to the paywall currently open in the editor when you provide the pairing code from the editor's agent connection panel. ### Platform quickstart skills Each quickstart skill walks the agent through a full SDK integration, step by step: | Skill | Platform | | ------------------------------ | ------------------------- | | `superwall-ios-quickstart` | iOS (Swift / Objective-C) | | `superwall-android-quickstart` | Android (Kotlin / Java) | | `superwall-flutter-quickstart` | Flutter | | `superwall-expo-quickstart` | Expo | Every quickstart follows the same flow: 1. **Install**: Installs the SDK dependency. 2. **Configure**: Ensures Superwall is ready at app launch. 3. **User management**: Identify users on sign-in, reset on logout. 4. **Feature gating**: Register placements and present paywalls. 5. **Subscription tracking**: Observe subscription status changes. 6. **User properties**: Set custom attributes for audience targeting. 7. **Paywall previews**: Sset up deep links for on-device previews. The agent reads bundled reference docs for each step, inspects your project, and implements minimal, production-safe changes before moving on to the next step. ## API access The general skill includes a bash helper (`sw-api.sh`) that wraps the Superwall REST API V2. It requires a `SUPERWALL_API_KEY` environment variable. That's an org-scoped bearer token you can generate from [API Keys settings](https://superwall.com/select-application?pathname=/applications/\:app/settings/api-keys). ```bash # List all available API routes (no API key needed) sw-api.sh --help # Show the full spec for a specific route sw-api.sh --help /v2/projects # List all projects sw-api.sh /v2/projects # Get a specific project sw-api.sh /v2/projects/{id} # Create a project sw-api.sh -m POST -d '{"name":"My Project"}' /v2/projects ``` The `--help` flag fetches the live OpenAPI spec, so the route reference is always current. ### Data hierarchy Superwall organizes data as **Organization → Projects → Applications**. Each application has a `platform` (ios, android, flutter, react\_native, web), a `bundle_id`, and a `public_api_key` used for SDK initialization. The org-scoped `SUPERWALL_API_KEY` is separate, it's used for API calls. ## Quick start Ask your AI agent to integrate Superwall into your app. The agent will: 1. Detect your platform from the project structure (e.g., `Package.swift` → iOS, `pubspec.yaml` → Flutter). 2. Determine your purchase controller path, whether you're using Superwall's default purchase handling, RevenueCat, or a custom setup. 3. Walk through the quickstart steps, implementing each one in your codebase. If you've installed the general skill with an API key, the agent can also look up your projects and applications to find the right `public_api_key` for SDK configuration. ## Related * [Superwall Agents](/docs/agents): For experiment analysis with connected Superwall tooling, automations, webhooks, and hosted machines. * [Superwall MCP](/docs/dashboard/guides/superwall-mcp): For managing your Superwall account from AI tools. * [Editor MCP](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-mcp): For connecting external agents to the paywall currently open in the editor. * [AI Chat Builder](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-ai-chat): For using Superwall's built-in editor chat to build and refine paywalls. * [Vibe Coding](/docs/sdk/guides/vibe-coding): All the AI tools available for working with Superwall listed in one place.