Skip to content
Back to tools
PaywallsMonetization

Superwall

Subscription infrastructure is free; Indie is $0 to $10,000 MAR, then 1%; paid plans start at $49 per month plus 1%.

Best for

  • Remote paywall experiments without an app release
  • Billing only on paywall-attributed revenue
  • Running Superwall next to an existing purchase backend

Not good for

  • A simple Apple-only app that can ship a StoreKit 2 paywall in code
  • Teams that need auth, a database, or file storage from the same vendor
  • Builders who will not iterate on paywalls remotely

Pros and cons

Pros

  • The paywall 1% is billed on Superwall-attributed revenue only, so subscriptions that never hit a Superwall paywall are not on that meter (checked Aug 21, 2026).
  • Subscription infrastructure — entitlements, purchase APIs, webhooks, and SQL access — is free at any scale, so you can adopt that layer without a revenue-based fee.
  • The Indie plan includes paywalls, campaigns, audiences, and templates at $0 until $10,000 MAR, which is the band a solo app actually occupies.
  • Registering placements in code instead of hardcoding paywall views keeps monetization changes on the dashboard, so you can iterate without an app release.
  • It can run alongside an existing purchase backend, so you do not have to rip out what you already have to start testing paywalls.

Cons

  • Moving paywall behavior into remote config means an outage or misconfiguration there affects what users see, so you need a sensible fallback.
  • Localization, collaborators, and surveys sit on Startup at $49 per month plus 1% of MAR, so those features are not part of the $0 Indie band.
  • Startup and Scale do not show the $10,000 free MAR band on their cards, so the monthly fee plus 1% is the published price once you leave Indie (checked Aug 21, 2026).
  • It is a focused paywall tool, not a general backend, so data storage, auth, and non-purchase features stay your responsibility.
  • Attribution-based pricing is harder to forecast than a flat fee, because cost depends on how much revenue the paywalls convert.

Short answer

Superwall pricing is two layers, and they do not share a meter. Subscription infrastructure — entitlements, purchase APIs, webhooks, and SQL access — is free at any scale. The paywall product on the Indie plan is $0 up to $10,000 in monthly attributed revenue (MAR), then 1% of total MAR; Startup is $49 per month plus 1% of MAR, and Scale is $199 per month plus 1% of MAR (checked Aug 21, 2026). That 1% is billed on revenue that flowed through a Superwall-rendered paywall, not on every subscription the app tracks.

The revenue base most people get wrong

RevenueCat bills 1% of monthly tracked revenue (MTR) once you reach $2,500. MTR is the revenue RevenueCat tracks that month in USD before the store cut: paid subscriptions, renewals, and one-time purchases (RevenueCat pricing, checked Aug 21, 2026). Superwall's paywall product bills 1% only on paywall-attributed revenue: subscriptions purchased outside a Superwall paywall, and imported or pre-integration users, are not part of that meter (Superwall pricing, checked Aug 21, 2026).

That is the decision, not the headline percentage. Both vendors publish a 1% rate. The difference is the revenue base. If half of a $50,000 month never touches a Superwall paywall, Superwall's own worked example bills 1% of $25,000 and leaves the other $25,000 unmetered. If RevenueCat tracked that same $50,000 month, its MTR meter would include the full amount.

Use Superwall when you want that attributed meter and you will change paywalls without waiting on App Store review. Use RevenueCat when purchase truth, receipt handling, and all-tracked revenue reporting are the job that must be right first. The two-way version of that choice is Superwall vs RevenueCat.

Superwall pricing

Four public plans sit on top of the free infrastructure layer.

Superwall plans (checked Aug 21, 2026)

PlanPriceWhat is included
Indie$0 per month up to $10,000 MAR, then 1% of total MARCharts, webhooks, integrations, the IAP SDK, paywalls, campaigns, audiences, and templates
Startup$49 per month plus 1% of MAREverything in Indie plus surveys, localization, AI-powered localization, and collaborators
Scale$199 per month plus 1% of MAREverything in Startup plus a dedicated account manager, Demand Score, refund protection, transaction abandon, AI audience generation, and saved snippets
EnterpriseCustom flat-rate pricingEverything in Scale plus implementation support, a dedicated Slack channel, monthly syncs, SSO, a custom SLA, and a signed contract

Two facts on that table are easy to misread, so they are worth stating in Superwall's own terms.

**MAR is not all subscription revenue.** Superwall's pricing page prices the paywall product on "revenue that flows through a Superwall-rendered paywall — and only that revenue." The Indie card's "1% of total MAR" is 1% of that attributed base once you are above $10,000, not 1% of every App Store dollar.

**Paid plans do not reprint the $10,000 free band.** Indie is the plan that shows "up to $10k MAR, then 1% of total MAR." Startup and Scale list a monthly fee plus 1% of MAR, with no free attributed-revenue band on those cards (checked Aug 21, 2026). Localization, extra collaborators, and surveys sit on Startup, so a solo builder who needs those features pays $49 per month even while attributed revenue is still small.

Prices last checked Aug 21, 2026, from superwall.com/pricing. Confirm current numbers before you commit spend — plan names, monthly fees, and the attributed-revenue threshold can move.

Solo builder read

Stay on Indie while you are iterating on paywalls alone and attributed revenue is under $10,000. The $49 Startup fee is what Superwall charges once you need localization or collaborators.

When Superwall is the wrong choice

Four cases where the fit is poor.

  • **You can ship a StoreKit 2 paywall in code and will not A/B it.** Remote campaigns, audiences, and a dashboard editor are overhead until you have enough traffic to learn from a test. Keep the paywall in the app.
  • **Purchase truth is the job that must be dependable before the next release.** Entitlements, restores, and cross-platform customer state are RevenueCat's center of gravity. Superwall can own infrastructure for free.
  • **You want paywall experiments plus subscription analytics in one paid product.** Adapty sells that bundle. Superwall centers the paywall and keeps infrastructure free; it is narrower on purpose.
  • **You need a backend.** Superwall does not replace auth, a database, or file storage. Those stay your responsibility, or they belong to a backend such as Supabase.

If Superwall is not the fit, read the Superwall alternatives for indie iOS apps page next — that is the decision flow for RevenueCat, Adapty, Qonversion, StoreKit 2, or keeping RevenueCat and adding Superwall only for paywall experiments.

Setup and integration

Superwall's paywall engine renders on iOS, Android, React Native, Flutter, and web, and the Indie plan includes an IAP SDK (checked Aug 21, 2026). On iOS you add the SDK, then present paywalls by registering placements in code rather than hardcoding a paywall view; the paywall itself is configured and updated from the dashboard. The free infrastructure layer can also handle entitlements and purchase state, so you can run Superwall on its own or beside another purchase backend.

Plan for the remote-first model. Because paywalls live in the dashboard, monetization behavior moves out of the codebase, which is convenient and means placement names and audience rules need discipline. You still define products in App Store Connect and test purchases in the sandbox on a device, and paywalls that depend on remote config want a sensible fallback if that config is unavailable.

Frequently asked questions

What does Superwall pricing cost?

On Indie, $0 until $10,000 in monthly attributed revenue, then 1% of total MAR. Startup is $49 per month plus 1% of MAR. Scale is $199 per month plus 1% of MAR. Enterprise is a custom flat rate. Subscription infrastructure stays $0 at any scale (checked Aug 21, 2026). Confirm the live table on Superwall's pricing page.

Does Superwall charge on all subscription revenue?

No. The paywall product is billed on paywall-attributed revenue only. Superwall states that subscriptions purchased outside Superwall, and imported or pre-integration users, are not billed. That is the opposite of RevenueCat's monthly tracked revenue meter, which includes paid subscriptions, renewals, and one-time purchases RevenueCat tracks (both pages checked Aug 21, 2026).

When is Superwall the wrong choice?

When you will not iterate on paywalls remotely, when purchase infrastructure is the risk you need to retire first, when you want Adapty's analytics-plus-paywall bundle, or when you need a general backend. For the wider set of options, use the Superwall alternatives page.

How is Superwall different from RevenueCat?

They lead with different jobs. RevenueCat is purchase infrastructure that later added paywalls. Superwall is a remote paywall product with free infrastructure underneath. Pricing follows that split: RevenueCat bills 1% of MTR once you reach $2,500; Superwall meters attributed paywall revenue, with Indie free to $10,000 MAR (checked Aug 21, 2026). See Superwall vs RevenueCat.

Do I still need App Store Connect and product setup?

Yes. Superwall controls how and when paywalls appear, but you create the products, prices, and subscription groups in App Store Connect and submit them for review yourself.

Alternatives

Related comparisons

Related guides