Subscription Analytics Software

RevenueCat Review: Pricing, SDKs and Paywalls

Research-based RevenueCat review of purchase SDKs, entitlements, paywalls, experiments, subscription analytics, web billing and limitations.

By Vishal SinghReviewed by Surabhi SinghPublished November 19, 2026· Updated Nov 19, 2026
RevenueCat review featured image
Research-based score
4.6
Research-based score
Features and capabilities4.9

Unified in-app subscription backend, configurable paywalls, experimentation, attribution integrations and extensive mobile charts.

Usability and implementation4.5

Good SDK and documentation ecosystem; store setup and entitlement migration still require engineering.

Pricing and value transparency4.5

Clear $2,500 free threshold and 1% full-MTR fee; store commissions and growth-tool structures need care.

Integrations, security and trust4.6

Large developer ecosystem, official SDKs and matched user reviews; no Toollers security audit.

Scored by Surabhi Singh

How this review was prepared: This is a research-based comparison of published vendor documentation and attributed third-party feedback. Toollers has not documented hands-on use of this product. Confirm current features, terms and pricing with the vendor before buying.

RevenueCat is a mobile-first platform for managing in-app purchases, subscriptions and premium access across supported stores and web billing systems. Its SDK, entitlement model, analytics and paywalls reduce the custom systems an app team must maintain.

Quick verdict

RevenueCat's strongest documented fit is mobile app purchase and entitlement infrastructure, paired with analytics, paywalls and experiments. Its 1% gross MTR model is easy to calculate but may matter at scale. We did not test an account.

Key takeaways

  • Cross-platform purchases SDK
  • Entitlements simplify access checks
  • Offerings and remote paywalls
  • Experiments and subscriber metrics
  • Web billing options
  • Pro free to $2,500 MTR, then 1%
  • No hands-on test
RevenueCat logo
RevenueCat Tested

Cross-platform in-app purchase infrastructure, subscription analytics, paywalls and app monetization.

Best for: iOS, Android, Flutter, React Native and cross-platform app teams managing in-app subscriptions, paywall experimentation and revenue analytics.

4.6
Research-based
Features and capabilities4.9
Usability and implementation4.5
Pricing and value transparency4.5
Integrations, security and trust4.6
Key features
  • Refund state updates
  • Multi-app portfolio management
  • App MRR analytics
  • Google Play Billing subscription tracking
  • Web-to-app funnels
Pros
  • Free access to the complete core feature set until $2,500 in Monthly Tracked Revenue.
  • Unifies app-store purchase validation and entitlements across supported platforms.
  • Includes paywall configuration, experiments, webhooks and detailed app subscription charts.
Cons
  • 1% is calculated on full pre-commission, pre-tax MTR after the free threshold, not just the excess.
  • App Store and Play Store commissions, payment-provider fees and taxes are separate.
Free plan
Scenario or planPublished RevenueCat feeBilling basisImportant qualification
Pro, $2,400 MTR$0Under $2,500 MTR thresholdFull feature scope described by vendor
Pro, $2,600 MTR$26 for billing cycle1% of full $2,600 MTRVendor's own worked example
Pro, $5,000 MTR$50 for billing cycle1% of full tracked gross amountIllustrative arithmetic, not an account quote
Pro, $20,000 MTR$200 for billing cycle1% of full tracked gross amountBefore marketplace commission and taxes
EnterpriseCustom quoteNegotiated tracking and service termsVolume discounts, dedicated support, SLAs
Standalone Growth ToolsConfirm conversion-based termsDepends on tool and configurationNot the same comparison basis as Pro MTR

Testing methodology

This is a research-based editorial review. We assessed the vendor documentation and attributed external user-review patterns cited below. Toollers has not documented hands-on testing for this product; confirm current plan terms and fit in a trial or demo.

Feature Breakdown

Purchase SDK

store integration and restoration

Entitlements

customer access state

Offerings

remote package presentation

Paywalls

remote design and delivery

Experiments

test subscription offers

Charts

churn, trials, MRR and retention

Customer Center

in-app self-service

Webhooks and exports

downstream event data

Pros

  • Broad SDK support
  • App-store entitlement abstraction
  • Integrated paywalls and experiments
  • Subscription analytics included
  • Web purchase pathways

Cons

  • SDK integration still needs engineering
  • Fees grow with gross tracked revenue
  • Platform dependency
  • Store-specific management restrictions
  • Migration requires careful identity mapping

Who should use this

  • iOS or Android subscription app
  • Flutter and React Native development team
  • Mobile growth team experimenting with paywalls
  • Product offering mobile and web premium access

Who should avoid this

  • Business only seeking general SaaS MRR charts
  • Team unable to maintain an SDK integration
  • Company expecting RevenueCat to waive app-store fees
  • Buyer requiring tested uptime figures from this review

Expert tip

Before adopting, test one sandbox subscription through purchase, renewal, restore, cancellation and refund; then verify the same customer entitlement across sign-in states. Review MTR independently from MRR.

This is a documentation-based editorial review; Toollers did not install the SDK, transact with a store, run an experiment or measure uptime.

See the RevenueCat Toollers product profile for the verified.

What RevenueCat does

RevenueCat sits between an application's purchase flow and the billing services that process transactions. Its Purchases SDK provides a common interface for purchase state and subscription access while its backend tracks lifecycle changes.

The core use case is a consumer or business app selling subscriptions, premium unlocks or other supported in-app products. The developer retains responsibility for defining products and complying with each marketplace's policies.

RevenueCat also serves product and growth teams. Charts show subscription performance; remotely configured paywalls and experiments allow the team to change how products are presented without maintaining an entirely separate experimentation service.

Web billing support extends the model beyond native stores. It can bring supported web subscription activity into a customer view alongside mobile purchases, but the checkout engine and rules still matter.

How we researched this review

We reviewed RevenueCat's official pricing, SDK installation, entitlement, Offerings, Charts, experiment, Customer Center, web billing, webhook and billing-account documentation on November 7, 2026.

We did not access a paid account, ship a test build, verify purchase receipts, interview users, run a retention experiment, inspect customer records, benchmark latency or speak with a sales representative.

The Toollers catalog contains a research-based rating and a tested-status field, but no independent tester record accompanies it. This review does not present a numeric score as a firsthand finding.

Judgments about likely fit, complexity and tradeoffs are editorial interpretations of product scope. They are not controlled comparisons or evidence of a particular conversion uplift.

Purchase SDK and store integrations

RevenueCat's SDK helps an app interact with subscription purchase services without building a separate complete receipt-verification and lifecycle abstraction for each operating system.

Official installation guides cover native iOS and Android, React Native, Expo, Flutter, Kotlin Multiplatform, Cordova, Capacitor, Unity and other platforms. Exact SDK functionality depends on platform and version.

The SDK does not eliminate app-store configuration. Developers must create the products in the relevant console, connect credentials, test sandbox flows and verify the desired product identifiers in RevenueCat.

The practical value is a standardized way to request products, initiate purchases, restore purchases and inspect customer entitlement information. An app still needs to respond safely to network failures and unavailable stores.

Entitlements: the access-control model

An entitlement represents a feature or access level, such as premium content or an ad-free experience. Products grant entitlements according to the purchase and subscription state reported through RevenueCat.

That lets the app ask whether a user has access without writing a separate store-specific rule for every premium screen. The logic is easier to maintain when subscriptions change duration or storefront.

Access must still be handled carefully when the device is offline, a customer signs in with another account or a transaction is refunded. Identity mapping and entitlement reconciliation are operational responsibilities.

We did not verify how this model behaves under a production outage. The documentation explains the intended functionality, not actual uptime under every failure mode.

Offerings and remote product presentation

Offerings group packages that the app can show to a customer. RevenueCat documents how teams can define a current Offering and retrieve it through the SDK at runtime.

Remote Offerings can simplify campaign changes and pricing presentations. The store remains the authority for product and price configuration; changing an Offering does not automatically change every store-side price.

The vendor explains that Offerings are optional for basic use, but they underpin features such as Paywalls, Targeting and Experiments. Their product-to-entitlement mappings need a controlled release process.

For a team with separate monthly and annual packages, a documented naming system can prevent the wrong product from being attached to a high-traffic paywall.

Paywall builder and presentation workflow

RevenueCat describes tools for building and remotely updating paywalls. Designers and growth teams can experiment with copy, imagery and layout without repeatedly asking engineers to hard-code every screen.

SDK support, available components and rendered behavior may differ by platform. A paywall preview is not proof that the exact production app version handles every device size, language and accessibility requirement.

Teams should test whether cancellation terms, free-trial disclosures and regional pricing remain visible. These are business and compliance requirements, not optional creative details.

The editor can shorten an iteration loop, but it cannot by itself establish which design will convert better. Conversion requires properly recorded impressions, purchase events and representative traffic.

Experiments and audience targeting

RevenueCat Experiments lets teams compare different Offerings, including subscription packages, trial lengths and paywall arrangements. The company documents targeting rules for presenting different Offerings to defined audiences.

An experiment must assign users consistently and measure the outcome over an appropriate subscription lifecycle. An initial trial signup is not the same as a retained subscriber or realized revenue months later.

Product teams should write down the hypothesis, audience, primary metric and stopping rule before a test starts. Otherwise random variation can be mistaken for a durable commercial result.

No Toollers experiment was run. We cannot report a measured lift or claim one paywall template outperformed another for a real app.

Subscriber analytics and MRR reporting

RevenueCat Charts covers active subscriptions, revenue, churn, trials, conversion rates, monthly recurring revenue, customer cohorts and retention. Its documentation also describes newer chart variants and metric definitions.

These reports help teams separate acquisition issues from retention issues. High trial starts with weak trial-to-paid conversion call for a different investigation from strong initial conversion followed by early churn.

MRR is a normalized recurring metric. RevenueCat's billing fee uses Monthly Tracked Revenue, which includes tracked purchases and renewals and is not interchangeable with MRR.

Teams using external BI tools should reconcile chart definitions, refunds, currencies and timing before comparing dashboards. RevenueCat's own chart documentation notes differences among metric versions and event dates.

Customer profiles and subscription support

The dashboard can show customer subscription history and current entitlements. This helps support staff investigate a complaint about premium access without reading raw receipt logs.

The Customer Center is an in-app self-service component for managing subscriptions and contacting support. The official help page lists cancellation flows, purchase restores and feedback prompts as possible actions.

The page also identifies iOS-only actions such as certain refund requests or subscription-plan changes. Teams should not assume every iOS management option exists on Android or the web.

Customer support still needs escalation paths for store-side refunds, identity conflicts and special account cases. Some actions are handled by the original store rather than RevenueCat.

Web subscriptions and revenue consolidation

RevenueCat's web documentation describes billing-engine choices including RevenueCat Billing, Stripe Billing and Paddle Billing. Supported web purchase links, SDK and funnels vary by integration path.

This can be useful when a product sells through both an app and a website and wants consistent subscription access. The engineering team must still map web buyers to app identities.

Apple and Google determine which storefronts allow alternative payment flows and how they may be presented. App-store policies can change, so a marketing funnel needs jurisdiction-specific review.

RevenueCat does not make a separate payment processor's charges disappear. Web billing economics need both purchase infrastructure and checkout fees included in a total-cost estimate.

Webhooks and business-system connections

RevenueCat can send subscription events to a server using webhooks. This supports actions such as updating an internal customer record or notifying a support workflow of a billing issue.

Its current documentation describes typical delivery delays and retry behavior, while noting that cancellations may arrive later than many other event types. A critical workflow needs idempotency and retry handling.

Treat a webhook as an external event message rather than absolute proof that every downstream action occurred. The receiving service must verify authenticity and manage duplicate deliveries or temporary unavailability.

Scheduled Data Exports can deliver transaction and other feeds to storage or email. Those exports are useful for analysis, though a finance team may still need independent reconciliation with its store settlements.

Security and account administration

Purchase state is commercially sensitive, and customer identifiers may be personal data. Teams should assess the vendor's current security terms, roles, data retention and destination controls before sending production events.

The minimum secure implementation uses appropriate API keys, validates incoming events, limits who can change paywalls and tests role permissions. Those controls belong in an implementation checklist.

We did not inspect any RevenueCat environment or independently audit security controls. Official technical documentation supports the available integration patterns, not a certification of our own testing.

The company also documents restrictions after overdue billing. An app should assign clear ownership of billing alerts to prevent an administrative issue from interrupting reporting and experimentation.

Supported frameworks and app maintenance

The number of SDK options is a strength for teams with several platforms. It can reduce the difference between iOS, Android and cross-platform subscription handling.

That variety also creates a version-management task. Some features require particular SDK versions, and platform-specific APIs may remain different even when the backend is shared.

RevenueCat's installation documentation describes changing package-distribution requirements for Apple platforms during 2026. Teams should verify the current supported installation route before locking a new mobile release.

An implementation plan should include dependency updates, sandbox tests, regression cases, subscription restore testing and an emergency feature-access path. No service removes the need for those checks.

Check RevenueCat pricing and billing rules

RevenueCat pricing

RevenueCat pricing and value assessment

Public Pro pricing is free up to $2,500 MTR and 1% of the full tracked amount above the threshold. The fee is measured before app-store commission and taxes and includes eligible one-time purchases.

For example, $2,600 MTR results in a $26 charge under the vendor's stated example. The platform fee is separate from Apple, Google or web-payment charges.

The pricing page advertises the full feature set on Pro. Enterprise has negotiated terms for high volume, dedicated support and complex tracking requirements, without a public fixed amount.

This can suit an early-stage app that wants purchase infrastructure and growth tools under a variable spend model. Cost rises with tracked revenue even if the app needs only a small portion of the feature set.

Strengths supported by published features

A standardized entitlement layer simplifies the product architecture for apps spanning multiple billing systems. The SDK library and documentation also cover widely used native and cross-platform development frameworks.

The same product family offers subscriber analytics, paywall iteration, targeting, experiments and customer support tools. Integration between these areas may reduce the coordination required across separate vendors.

The published free allowance reduces the initial platform fee for a new app. It is possible to explore a complete set of product features before tracked revenue grows beyond the threshold.

Webhooks, exports and third-party integrations give teams ways to use subscription events in other systems. Actual integration work varies with the app's code and data needs.

Tradeoffs and areas to evaluate

RevenueCat introduces a platform dependency for premium access and transaction interpretation. A critical app should design carefully for outages, bad identifiers and missed events, even if the vendor supplies retries.

The pricing model is based on gross tracked activity rather than net payouts. Apps with significant store commissions, refunds or thin margins should calculate the bill on the correct base.

Advanced paywall experiments require credible measurement and enough relevant traffic. A tiny app may not gain useful statistical evidence from several simultaneous variants.

Moving away later can involve replacing SDK calls, reconstructing customer entitlements and validating imported transaction history. There is a real migration cost beyond subscription fees.

Who should use RevenueCat?

Native iOS and Android developers with subscriptions are a direct fit. Cross-platform teams using Flutter or React Native may benefit from a common purchase and entitlement backend.

Mobile growth teams that regularly update paywalls, test subscription offers and monitor trial conversion should evaluate the product's integrated experimentation and analytics tools.

Companies with app-and-web membership access can consider RevenueCat's supported web integrations, provided they verify payment policies, identity mapping and checkout economics.

The most relevant buyer usually has someone who can own product configuration and SDK maintenance. A nontechnical website business without app-store purchases may need a different category of billing software.

Who may prefer another solution?

Teams that primarily need SaaS MRR reporting across existing Stripe or Chargebee contracts may find ChartMogul or ProfitWell Metrics closer to their job than a mobile purchase SDK.

An app that wants a paywall design engine while keeping its existing purchase backend should compare Superwall or Purchasely, including their integration and attribution rules.

Apps with substantial tracked purchase volume should compare annual total cost and ask about Enterprise pricing. The free threshold alone does not describe the bill at scale.

An experienced engineering team can build directly on StoreKit and Google Play Billing APIs. That avoids an additional platform fee but transfers implementation, reliability and reporting work back to the app team.

An evidence-based evaluation checklist

In a controlled development environment, configure one subscription, one non-subscription purchase and a test entitlement. Verify expected access during purchase, renewal, restore, expiration and refund scenarios.

Map an anonymous app user to web and mobile purchases where relevant. Confirm that account switching does not unintentionally grant or remove the wrong person's premium rights.

Reproduce a paywall experiment with a test audience and verify which events are recorded. Then inspect the revenue definitions and export format before relying on dashboard totals.

The checks above are recommendations, not tests performed by Toollers. We did not confirm a particular latency, conversion result or support response.

Official product documentation checked November 7, 2026. Draft only, with no authenticated purchase, firsthand test or vendor quote.:

Explore RevenueCat's current product details

Visit RevenueCat

Frequently asked questions

What is RevenueCat used for?
It provides purchase SDKs, entitlements, subscription lifecycle tracking, analytics, paywalls and experiments for supported mobile and web subscription workflows.
Does RevenueCat process app-store payments?
Apple and Google remain the underlying marketplace billing systems. RevenueCat standardizes purchase state and related app services.
Does it work with Flutter and React Native?
Yes, RevenueCat publishes SDK installation guides for Flutter, React Native and native platforms. Verify feature support and versions.
Can it test paywalls?
Yes. RevenueCat documents remote Paywalls, Offerings, audience targeting and experiments. Results depend on correct event measurement.
Does it support web subscriptions?
Its documentation describes RevenueCat Billing, Stripe Billing, Paddle Billing and supported web purchase paths, subject to configuration and store rules.
Is RevenueCat free forever?
The published Pro fee is zero while MTR remains within the $2,500 allowance, but pricing policies and contracts may change.
Did Toollers test RevenueCat?
No verified firsthand product testing is documented for this article. Findings come from official pricing and technical documentation.
Is RevenueCat a replacement for ChartMogul?
Not directly. RevenueCat manages app purchases and entitlements; ChartMogul focuses on subscription analytics and revenue CRM.

Sources

Written by

Vishal Singh

Author

Toollers editorial contributor. Biography and credentials pending confirmation.

Reviewed by Surabhi Singh