# 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/ # Query ClickHouse Use the Superwall API to query your organization's ClickHouse-backed analytics data. The ClickHouse query API gives you direct SQL access to the same analytics data Superwall uses for charts and campaign results. Use it when you need flexible reporting, internal dashboards, or ad hoc analysis without maintaining a separate data warehouse. Requests are scoped to your organization and require an organization API key with the `data:read` scope. Superwall provisions a read-only ClickHouse user for your organization on first use, then applies row-level policies so queries only return data for your organization's applications. > **Warning:** Treat `data:read` keys as sensitive. They can query analytics data for your organization, so create dedicated keys, store them in a secret manager, and revoke them when they are no longer needed. ## Endpoint Use either `POST` or `GET`: | Method | Path | SQL location | | ------ | -------------------------------------------------------------------- | --------------------- | | `POST` | `https://api.superwall.com/v2/organizations/{organization_id}/query` | Request body | | `GET` | `https://api.superwall.com/v2/organizations/{organization_id}/query` | `query` URL parameter | `POST` is recommended for most queries because SQL can be long and multiline. ## Authentication 1. Open **Settings > API Keys** in the Superwall dashboard. 2. Create an organization API key. 3. Give the key the `data:read` scope. 4. Copy the token when Superwall shows it. Pass the token as a bearer token: ```bash Authorization: Bearer YOUR_SECRET_TOKEN ``` The token must belong to the organization in the path. A key from another organization cannot query this endpoint. ## Send a query Set your organization ID and API key: ```bash export SUPERWALL_ORG_ID="123" export SUPERWALL_API_KEY="sk_..." ``` Run a query with `POST`: ```bash curl "https://api.superwall.com/v2/organizations/$SUPERWALL_ORG_ID/query" \ --request POST \ --header "Authorization: Bearer $SUPERWALL_API_KEY" \ --data-binary "SELECT count() FROM sw.events_rep" ``` Run a query with `GET`: ```bash curl --get "https://api.superwall.com/v2/organizations/$SUPERWALL_ORG_ID/query" \ --header "Authorization: Bearer $SUPERWALL_API_KEY" \ --data-urlencode "query=SELECT count() FROM sw.events_rep" ``` The response is the raw ClickHouse HTTP response. If you do not specify a format, ClickHouse returns its default text format. Add a `FORMAT` clause when you need JSON: ```bash curl "https://api.superwall.com/v2/organizations/$SUPERWALL_ORG_ID/query" \ --request POST \ --header "Authorization: Bearer $SUPERWALL_API_KEY" \ --data-binary " SELECT name, count() AS events FROM sw.events_rep WHERE ts >= now() - INTERVAL 7 DAY GROUP BY name ORDER BY events DESC LIMIT 20 FORMAT JSONEachRow " ``` ## Use ClickHouse HTTP options The endpoint proxies ClickHouse HTTP requests after Superwall authenticates your organization API key. You can pass standard ClickHouse URL parameters, such as `query`, `database`, or `default_format`, through the query string: ```bash curl --get "https://api.superwall.com/v2/organizations/$SUPERWALL_ORG_ID/query" \ --header "Authorization: Bearer $SUPERWALL_API_KEY" \ --data-urlencode "query=SELECT name, count() FROM events_rep GROUP BY name LIMIT 20" \ --data-urlencode "database=sw" \ --data-urlencode "default_format=JSONEachRow" ``` Superwall does not expose the generated ClickHouse username and password. Authenticate to the Superwall endpoint with your bearer token instead of connecting directly to the ClickHouse cluster. ## Available tables Your read-only user can query the analytics tables Superwall exposes for customer reporting: | Table | Use it for | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------- | | `sw.events_rep` | Raw Superwall events, including event name, metadata, properties, sandbox flag, application ID, and timestamp. | | `sw.events_hr_agg` | Hourly event aggregates. | | `sw.demand_score_events_rep` | Demand Score event data. | | `open_revenue.attributed_events_by_ts_rep` | Revenue and attribution events ordered by event time. | | `open_revenue.paywall_open_events_agg` | Aggregated paywall open events. | | `sw.subscription_status_rep` | Subscription status records. | | `sw.user_attributes_rep` | User attributes set through the SDK or paywall flows. | | `sw.applications_rep` | Application metadata available in ClickHouse. | Use ClickHouse introspection queries to inspect columns before writing a production query: ```sql SHOW TABLES FROM sw; SHOW TABLES FROM open_revenue; DESCRIBE TABLE sw.events_rep; DESCRIBE TABLE open_revenue.attributed_events_by_ts_rep; ``` ## Query JSON properties Some event details are stored in JSON strings such as `props` and `meta`. Use ClickHouse JSON functions to extract them: ```sql SELECT JSONExtractString(props, '$placement_name') AS placement, count() AS opens FROM sw.events_rep WHERE name = 'paywall_open' AND ts >= now() - INTERVAL 30 DAY GROUP BY placement ORDER BY opens DESC LIMIT 20 FORMAT JSONEachRow; ``` ## Limits Queries run as a read-only organization user with ClickHouse settings applied: | Limit | Value | | ---------------------- | ----------- | | Maximum execution time | 300 seconds | | Maximum threads | 4 | | Maximum memory | 8 GB | | Maximum bytes read | 20 GB | If a query times out or uses too much memory, narrow the date range, add filters on `applicationId`, `isSandbox`, or event `name`, and avoid selecting large JSON columns unless you need them. ## Troubleshooting | Status | What to check | | ------ | ------------------------------------------------------------------------------------------------------------------------ | | `401` | The request is missing a bearer token, or the token is invalid or revoked. | | `403` | The API key does not include the `data:read` scope. | | `404` | The requested organization resource could not be found. | | `429` | Too many requests were sent in a short period. Retry later. | | `500` | ClickHouse returned an unexpected error or Superwall could not proxy the request. Check the SQL and try a smaller query. | ## Related * [Access Controls](/docs/dashboard/dashboard-settings/overview-settings-access-controls) * [Charts](/docs/dashboard/charts) * [Superwall Skill](/docs/dashboard/guides/superwall-skill)