A self-hosted, open-source RevenueCat alternative

Control your own purchase infrastructure, share none of your revenue, and depend on no commercial service. Keep the Purchases SDK you already use: change one URL, not your purchase code.

// Before configure()
Purchases.proxyURL = URL(string: "https://purchases.example.com")
Purchases.configure(withAPIKey: "appl_…")

One line. Same SDK, same purchase code.

Charts
  
Who it's for

For app developers who'd rather run it themselves

openpurr works with the official, unmodified SDKs. Switching starts with changing one URL, not rewriting your purchase code.

Your data, your servers

Purchase records, entitlements and store credentials live in a database you run, query, back up and export. No outside service sits between your app and your customers.

No revenue share

No percentage of revenue and no per-transaction fees. The Lite edition is designed to fit Cloudflare's free plan, so a small app can run it for nothing.

No vendor to depend on

It's open source under Apache 2.0. Read the code, change it, and move it between Cloudflare and your own cloud.

How it works

Your server sits where the vendor used to

Your app keeps the open-source Purchases SDK it already ships with. The SDK talks to openpurr. openpurr talks to the stores, keeps the subscription state, and tells your backend what changed.

Your app
Purchases SDKOfficial, unmodified, MIT licensediOS, Android, Flutter or React Native
openpurrOn Cloudflare Workers or your own cloud
App StoreServer API and notifications
Google PlayDeveloper API and RTDN
Your backendSigned webhooks
  1. Deploy

    Run openpurr Lite on your own Cloudflare account. A guided setup, pnpm run setup, creates the database, deploys both Workers and your owner account.

  2. Point the SDK

    Set the proxy URL before configure. Use a custom domain you own so you can move later.

  3. Connect the stores

    Add your store credentials and notification URLs. The setup check, openpurr doctor, verifies them and says how to fix anything that's missing.

What it does

The subscription backend, without the extras you don't use

Purchases

Validates StoreKit 2 transactions and Google Play purchases, and returns the CustomerInfo and entitlements the SDK expects.

Store notifications

Receives App Store Server Notifications V2 and Google Play Real-time Developer Notifications, so renewals, refunds and grace periods stay current.

Webhooks

Sends RevenueCat-shaped events to your backend, signed with HMAC-SHA256 and retried for about 72 hours.

Charts

16 charts: revenue, MRR and ARR, MRR and subscription movement, active and paid subscriptions, subscription status, churn, trials and trial conversion, new customers, refunds and refund rate, and one-time purchases. Filter by app, store, product and environment, with revenue converted to USD.

Auth and audit

SDK keys and secret keys, operator sign-in with optional authenticator codes, roles, access tokens and an audit log.

MCP server and Claude skills

Ask an AI assistant why a customer does or doesn't have an entitlement, look up purchases, or get walked through App Store and Play Console setup.

Two editions

Start small, move up without an app update

Both editions pass the same conformance suite. If your app points at a custom domain you own, moving from Lite to Standard needs no app release.

Lite

For indie apps

$0 on Cloudflare's free plan

  • TypeScript on Cloudflare Workers and D1
  • Lightweight and cheap to run
  • Usage alerts before you hit free-plan limits

Standard

Coming soon

Your cloud bill nothing more

  • Go and Postgres in containers
  • GCP or AWS
  • For larger portfolios of apps
Being upfront

It may not be for you yet

If you need paywall builders, A/B experiments, third-party analytics integrations or a support contract, commercial platforms offer those today.

Out of scope for now

PaywallsAd eventsCustomer CenterVirtual currenciesWeb billingAmazonAnalytics integrations

Roadmap

Where it's headed

The order is firm, but there are no dates. If something matters to you, say so in an issue.

In progress

Lite

  • Latest release: 0.2.0
  • Designed for Cloudflare's free plan
  • App Store and Google Play
  • Webhooks, dashboard and admin
  • Several apps in one deployment
  • MCP server, CLI and Claude skills
  • Next: device testing, then 1.0
Planned

Standard

  • Go and Postgres in containers
  • GCP first, then AWS
  • Same conformance suite as Lite
  • Move from Lite with no app update
Your call

Shaped by the community

  • Verified end-user identity
  • Standard extras for larger teams
  • Whatever you ask for in issues

Read the full roadmap →

FAQ

openpurr as a RevenueCat alternative

What changes when you run your own subscription backend, and what doesn't.

What is openpurr?

openpurr is an open-source, self-hosted alternative to RevenueCat. It's a backend for in-app purchases and subscriptions that works with the official RevenueCat Purchases SDK. It validates App Store and Google Play purchases, tracks entitlements, receives store notifications, sends webhooks to your backend, and charts your core subscription metrics, all on infrastructure you control.

How is openpurr different from RevenueCat?

RevenueCat is a hosted commercial service that charges a share of revenue above a free tier. openpurr is software you run yourself: your purchase records, entitlements and store credentials live in your own database, and there's no revenue share or per-transaction fee. RevenueCat offers more features today, such as paywalls, experiments and analytics integrations. openpurr focuses on the core subscription backend.

Do I have to rewrite my purchase code to switch from RevenueCat?

No. openpurr works with the official, unmodified Purchases SDK. You set the SDK's proxy URL to your openpurr server before calling configure, and the rest of your purchase code stays the same. Point it at a custom domain you own so you can move servers later without an app update.

How do I move my existing customers from RevenueCat?

Import them. Ask RevenueCat for a migration export, and openpurr import fetches each customer's purchases from Apple and Google and gives them to the same app user IDs. The new version of your app also sends each customer's purchases once, and both backends stay up to date while people update, so nobody loses access. How to migrate →

Which platforms and stores does openpurr support?

The Purchases SDK for iOS, Android, Flutter and React Native, with purchases from the App Store and Google Play. Amazon and web billing are out of scope for now.

How much does openpurr cost?

openpurr is free and open source under the Apache 2.0 license. You pay only for the infrastructure it runs on. The Lite edition is designed to run on Cloudflare's free plan, so a small app can run it for nothing. The Standard edition runs in containers on your own cloud, so its cost is your cloud bill.

Where is my data stored?

In your own database. The Lite edition uses Cloudflare D1 in your Cloudflare account. The Standard edition uses Postgres on GCP or AWS. You can query, back up and export it, and no outside service sits between your app and your customers.

Does openpurr send webhooks like RevenueCat does?

Yes. openpurr sends RevenueCat-shaped events to your backend, signed with HMAC-SHA256 and retried for about 72 hours, so existing webhook handlers need few or no changes.

What doesn't openpurr do that RevenueCat does?

Paywalls, third-party analytics integrations, Customer Center, virtual currencies, web billing, Amazon, ad events and a commercial support contract are out of scope for now. Price experiments are on the roadmap. If you need those today, a commercial platform is a better fit.

Is openpurr ready for production?

Not yet. openpurr is early: the Lite edition is in progress and the Standard edition is coming later. Follow the roadmap on GitHub, and open an issue if something matters to you.

Is openpurr affiliated with RevenueCat?

No. openpurr is an independent open-source project, not affiliated with or endorsed by RevenueCat, Inc. It works with RevenueCat's official Purchases SDK, which is MIT licensed.

Help shape it

The most useful help right now is feedback: wrong assumptions about the SDKs or the stores, and real-world edge cases in renewals, refunds and grace periods.