RevenueCat alternative

The open-source RevenueCat alternative, free until $10K a month

The best open-source RevenueCat alternative is RevenueDot. It is an AGPL-3.0 backend that the stock RevenueCat SDKs already talk to, so you change one URL and keep your app code. RevenueDot Cloud is free until your app makes $10K a month, then 0.5% of revenue above that, never more than $999 a month. It has no SOC 2 report and no years of live traffic yet. For a hosted option with a different SDK, look at Adapty, Qonversion or Superwall.

Free until your app makes $10,000 a month, then 0.5% of revenue above that, never more than $999 a month. See every alternative

The one lineSwift
Purchases.proxyURL = URL(string: "https://api.revenuedot.app")!
Purchases.configure(withAPIKey: "appl_...")  // unchanged
RevenueDot dashboard overview with MRR, active subscriptions, trials, revenue and recent transactions
The RevenueDot dashboard, captured from the running app with demo data.

Keep the RevenueCat SDK

Set one proxy URL. Offerings, purchases, restores and CustomerInfo code stays as it is, and so do your webhooks and REST calls.

Free until $10K a month

RevenueCat charges 1% of all tracked revenue from $2,500. RevenueDot Cloud is free until your app makes $10K a month, with a cap of $999 a month above that.

Open source, AGPL-3.0

Read the server and dashboard code on GitHub. The SDK forks, CLI and MCP server are MIT.

The features you pay RevenueCat for

43 charts, paywalls with a visual editor, experiments, web checkout, 36 integrations, Refund Control and win-back, in one dashboard.

Why teams leave RevenueCat

Three reasons come up again and again: the bill, who owns the data, and how hard it is to leave.

  • The cost cliff. RevenueCat is free to $2,500 monthly tracked revenue, then charges 1% of all of it, before the stores take their cut. That is $500 a month at $50,000 and $10,000 at $1,000,000. Its pricing FAQ gives $25 for $2,500, and a staff reply confirms the 1% covers the whole amount.
  • Data ownership. Your subscribers' purchase history sits in RevenueCat's hosted service. You can pull it through the REST API and scheduled exports, but it is not in a database you run. RevenueCat's security page names no hosting region.
  • Lock-in. The SDK, the entitlement model, the webhook shapes and your paywalls all point at one vendor. Adapty's migration guide notes that Google purchase tokens come from RevenueCat support, and that promotional entitlements and refund history do not move.
RevenueCat pricing: the Pro card says 'Pay nothing for up to $2,500 in monthly tracked revenue. Then pay 1% of what you track once you hit $2,500 in MTR.'
RevenueCat pricing page, captured 4 Oct 2026: Free to $2,500 monthly tracked revenue, then 1% of what you track. Source ↗ · Full page ↗
RevenueCat community thread: staff reply 'We won't start charging you until you hit 2500 in MTR, but pricing will still be 1% of your whole MTR, so $25.'
RevenueCat community thread, captured 4 Oct 2026: Staff reply: 1% of the whole MTR once you reach $2,500. Source ↗ · Full page ↗
RevenueCat GDPR page: RevenueCat is a processor of end-user data; no hosting region is named.
RevenueCat GDPR page, captured 4 Oct 2026: GDPR processor; no hosting region named. Source ↗ · Full page ↗
Adapty migration guide from RevenueCat: promotional or manually granted entitlements import as profiles without transactions; refund and billing-issue history is not carried over verbatim.
Adapty docs page, captured 4 Oct 2026: Promotional entitlements and refund history do not come across. Source ↗ · Full page ↗

How RevenueDot keeps the RevenueCat SDK

RevenueDot is a server that answers the same API the RevenueCat SDKs call, so your app keeps the SDK and talks to a different host. The SDKs have a proxy URL setting built for this. RevenueDot also publishes hard forks of all ten SDKs that default to its host and verify its response signatures.

One line on iOSSwift
// Before Purchases.configure
Purchases.proxyURL = URL(string: "https://api.revenuedot.app")!
Purchases.configure(withAPIKey: "appl_...")

Migration

Moving from RevenueCat takes an afternoon of setup and one release

The work is an import, a side-by-side run and a release. The app change is one line.

  1. 01

    Import your project

    Create a free Cloud account, then run npx revenuedot import --from-revenuecat with a read-only RevenueCat secret key. It copies apps, SDK keys, products, offerings, customers and history. Use --dry-run first.

  2. 02

    Run both side by side

    Point App Store and Google Play server notifications at RevenueDot, which forwards each one to RevenueCat so both stay current.

  3. 03

    Ship the one-line change

    Set the proxy URL in your next release, watch the dashboard fill, and turn RevenueCat off when most active users have updated.

Terminal output of 'npx revenuedot import --from-revenuecat --dry-run': the catalog it would create (apps, products, entitlements, offerings, packages, SDK keys kept), 14 customers read with their subscriptions and purchases, and the store credentials to re-enter because RevenueCat cannot export them.
The real output of the importer's dry run against a RevenueCat project copy, rendered as a terminal window.

The importer from RevenueCat: read the guide →

What is different from RevenueCat

  • Younger. RevenueDot launched in 2026. RevenueCat has years of live traffic.
  • No SOC 2 yet. RevenueCat publishes SOC 2 Type II. RevenueDot has no certification yet.
  • Newest stores not proven live. RevenueDot supports the same stores, but its Paddle, Roku and Galaxy Store support has only run against copies of those stores' APIs.
  • Single-screen paywalls. RevenueDot's paywall editor builds single-screen paywalls; multi-step flows are not built yet.

See it

The features you pay RevenueCat for, in RevenueDot

Real captures of the dashboard with example data, not mockups. Every feature below is in the open-source server today.

14-second silent tour of the RevenueDot dashboard: Overview, MRR chart, paywall editor and experiment results.

RevenueDot: Paywalls and the editor

The paywall editor with the Trial timeline template open: the phone preview switches from light to dark and back while the layers and their properties stay in view.
Recorded from the real RevenueDot dashboard with example data; silent.

Paywalls and the editor: read the guide →

RevenueDot: 43 charts

The MRR chart with its weekly, monthly and yearly range, then the Trial Conversion Funnel chart with its counts of new customers, trials started and converted, picked from the chart list.
Recorded from the real RevenueDot dashboard with example data; silent.

43 charts: read the guide →

RevenueDot: Experiments with results

The results of the 'Annual plan first on the paywall' experiment: customers in the control and the treatment, conversion to paying and revenue per customer, with the treatment's lift.
Recorded from the real RevenueDot dashboard with example data; silent.

Experiments with results: read the guide →

RevenueDot: Web checkout and purchase links

On the hosted purchase page: switching between the Annual and Monthly plans, opening the discount code field, typing SPRING20 and applying it.
Recorded from the real hosted purchase page with example products; silent.

Web checkout and purchase links: read the guide →

FAQ

RevenueCat alternative: questions people ask

What is the best open-source alternative to RevenueCat?

RevenueDot. Its server and dashboard are AGPL-3.0, its SDK forks are MIT, and it works with the stock RevenueCat SDKs, so you keep your app code. It runs on RevenueDot Cloud, free until your app makes $10,000 a month. It is newer than RevenueCat and has no SOC 2 report yet.

Is there a free RevenueCat alternative?

Yes. RevenueDot Cloud is free until your app makes $10,000 a month, then 0.5% of the revenue above that, never more than $999 a month. Superwall also offers free subscription infrastructure and bills 1% only on revenue from its own paywalls above $10K a month.

Do I have to change my app to leave RevenueCat?

With RevenueDot, one line: set the SDK's proxy URL before configure. With the stock SDK you also turn off its response-signature check, or you use a RevenueDot SDK fork. With Adapty, Qonversion, Superwall or Apphud you replace the SDK and rewrite your purchase code.

How do I migrate from RevenueCat without losing subscribers?

Import your project with a read-only RevenueCat key, which copies customers, entitlements and history. Then point store notifications at RevenueDot, which forwards them to RevenueCat so both stay current, and ship the proxy change. Current access is imported, so no subscriber loses access on switch day.

Is RevenueDot as reliable as RevenueCat?

Not yet proven. RevenueCat has years of live purchase traffic and a SOC 2 Type II report. RevenueDot launched in 2026. Running both side by side during a migration lets you compare them before you switch.

Get started

Switch from RevenueCat without losing a subscriber.

Start for free on RevenueDot Cloud, import your RevenueCat project with one command, and change one line in your app. Pro costs $0 until your apps make $10,000 a month.

Already have an account? Sign in