Superwall vs RevenueCat: what each costs and what each does

Superwall vs RevenueCat: what each costs at $1k to $50k a month

• RevenueCat: free under $2,500 of monthly tracked revenue, then 1% of all of it. At $2,500 the fee applies to all $2,500, so it's $25. (RevenueCat pricing)
• Superwall infrastructure: free at any scale on Superwall's published pricing (4 Nov 2026). Superwall's pricing page lists entitlement and purchase APIs, webhook delivery, the Query API and historical subscription imports under it. (Superwall pricing)
• Superwall paywalls, Indie plan: free up to $10k of monthly attributed revenue (MAR), then 1% of all of it. At $10,001 the fee applies to all $10,001, so it's about $100.

Superwall defines MAR as revenue attributed to a Superwall paywall (Superwall FAQ). RevenueCat bills tracked revenue, which is all revenue it sees. So the two bases differ.

Scroll sideways for all columns

Monthly revenue	RevenueCat (paywalls, experiments, webhooks included)	Superwall, no Superwall paywalls	Superwall Indie, paywalls on 50% of revenue	Superwall Indie, paywalls on all revenue
$1,000	$0	$0	$0	$0
$5,000	$50	$0	$0	$0
$10,000	$100	$0	$0	$0
$50,000	$500	$0	$250	$500

• RevenueCat at $1,000: under $2,500, so $0. At $5,000: 1% x $5,000 = $50. At $10,000: $100. At $50,000: $500.
• Superwall, no paywalls: $0 at every level, because infrastructure has no fee.
• Superwall Indie, 50% on paywalls: paywall revenue is $500, $2,500, $5,000 and $25,000. The first three are at or under $10,000, so $0. At $25,000: 1% x $25,000 = $250.
• Superwall Indie, all revenue on paywalls: $1,000, $5,000 and $10,000 are at or under $10,000, so $0. At $50,000: 1% x $50,000 = $500.

Superwall's pricing page also lists Startup ($49 a month plus 1% of MAR) and Scale ($199 a month plus 1% of MAR). Assumes 1% from the first dollar; Superwall's page and FAQ differ on this.

The "no paywalls" column doesn't compare like for like with RevenueCat, whose price includes paywalls and experiments. If you drop them, you pay for another tool or build them. RevenueCat also offers Growth Tools for teams that keep their own purchase infrastructure. Its page says you "only pay on the conversions from the tools you use" at "1% of MTR on what you track", and gives no threshold (RevenueCat pricing).

With Superwall Indie paywalls on all revenue, the fee equals RevenueCat's at $50,000 and is lower at $5,000 and $10,000.

What each one does

From official pages, checked 4 Nov 2026. Where a page doesn't say, the cell says so.

Scroll sideways for all columns

Feature	RevenueCat	Superwall
Entitlements	Created in the dashboard under Product catalog, Entitlements tab. Read in the SDK with getCustomerInfo. Docs	Created on the Products page and attached to products. Subscription status is determined by entitlements. Docs
Purchase handling	The import docs say RevenueCat validates receipts sent through its REST API. Docs	Says Superwall: entitlements are synchronized from App Store Server Notifications V2 and Google Real-Time Developer Notifications. Pricing page
Webhooks	Pro plan. POST with JSON, up to 5 retries over about 80 minutes, optional HMAC signing. Docs	Events include initial purchase, renewal, cancellation, billing issue and expiration, from App Store, Play Store and Stripe. Signed with a per-webhook secret. The pages I read don't state a retry schedule. Docs
Integrations	16 listed, including Amplitude, Mixpanel, PostHog, Segment, Braze, Firebase, Slack, Discord. Docs	Listed in the docs: Mixpanel, Amplitude, PostHog, Adjust, Meta Conversion API, Firebase, Slack, Discord, Apple Search Ads and others. Docs
Paywalls	Remote editor, templates, AI editor, single screen or multi-step. iOS 15+, Android 7 (API 24)+, macOS 12+, web via Web Purchase Links. Docs	Editor with templates, flows for multi-step experiences and an AI Chat Builder. Says Superwall: renders on iOS, Android, React Native, Flutter and Web. Docs
Experiments	Tests prices, offers, product mix, paywall layout and Apple retention messages. Up to 4 variants, audience share from 10%. Docs	Paywall A/B tests: two or more paywalls in an audience, a percentage each, optional holdout. The page describes paywall tests and doesn't mention price tests. Docs
Data access	Charts with 40+ metrics (says RevenueCat), a REST API, scheduled CSV or Parquet exports to S3, Google Cloud Storage, Azure or email. Exports are open to accounts signed up after Sept 2023, certain legacy plans and Enterprise. Docs	Query API: SQL over ClickHouse with an organization API key. Limits: 300 seconds, 8 GB memory. Docs
SDK platforms	iOS and Apple platforms, Android, React Native, Expo, Flutter, Kotlin Multiplatform, Cordova, Capacitor, Unity, Web, Roku, Vega. Docs	iOS (15+), Android (minSdk 23), Expo (SDK 53+), Flutter. Kotlin Multiplatform, Unity and Web are labelled beta. React Native is labelled legacy. Capacitor is community-maintained. Docs

What Superwall says about moving from RevenueCat

Superwall's migration guide covers three cases. Everything in this section is Superwall's own account.

• RevenueCat only: remove the RevenueCat SDK, install the Superwall SDK, and change the code that checks purchase status. Entitlement checks move from Purchases.shared.customerInfo() to Superwall.shared.subscriptionStatus.
• Both SDKs with a purchase controller: remove the controller and configure Superwall without it. Superwall then handles purchasing, restoring and entitlements.
• Observer mode: keep RevenueCat in observer mode and install Superwall next to it. Superwall's RevenueCat guide calls this the recommended way to use the two together.

The guide says RevenueCat can show paywalls when an entitlement isn't active, manually, or with custom logic, while Superwall usually uses placements at the call site. It also says RevenueCat currently offers metrics such as LTV and MRR, and suggests keeping RevenueCat in observer mode if you need them.

Superwall's pricing page adds that a coding agent does the SDK swap and ports subscription history, entitlement state and webhook configuration "in under an hour". It also says "Imported & pre-integration users are never billed" and "Subscriptions purchased outside Superwall are free". If that holds, existing subscribers of a migrating app don't count toward MAR.

What switching involves

1. SDK swap. Replace the SDK and rewrite every place your app checks entitlements. Superwall's guide shows the code change.
2. App release. The SDK is compiled into your app, so the change reaches users through a new store release. That is my inference from how SDKs work; neither guide states it.
3. Old versions. Users who haven't updated stay on the old SDK and keep talking to RevenueCat. Superwall's guide doesn't cover this. I read it as a reason to keep RevenueCat running until most users have updated. That is my reading, not documented.
4. Historical data. Superwall says it ports subscription history. No page I read lists which fields move, so ask Superwall before relying on it. RevenueCat documents scheduled exports of transaction data, worth running before you leave.
5. Android billing library. Superwall's Android SDK 2.8.0 raised its minimum to minSdk 23 and moved Google Play Billing to 9.1.0. Its docs say this also upgrades Billing for other libraries in the same app, RevenueCat included, and to confirm those providers support Billing 9 first.

Payback: an illustrative example

This is a made-up case to show the method. The hours and rate are inputs; swap in your own.

Payback in months = (hours x hourly rate) / monthly fee difference. Say the switch costs 40 hours at $75 an hour, which is $3,000. The monthly fee difference is RevenueCat's fee minus the Superwall figure from the first table.

At $1,000 the fee difference is $0, since both are $0. The first column assumes you replace RevenueCat's paywalls and experiments with nothing, or already have them elsewhere. If you pay for another paywall tool, subtract that from the difference.