What do people most often ask about RevenueDot?

RevenueDot is an open-source (AGPL-3.0) backend for in-app purchases and subscriptions, with an SDK for every platform. Apps that already ship the RevenueCat SDK can keep it and change one line. Start for free on RevenueDot Cloud. The answers below say what exists on 2026-10-05.

RevenueDot is the open-source RevenueCat alternative: the first release is v2026.10.03, it has run in production beside RevenueCat since 2026-10-02, and RevenueDot Cloud Pro is free until your apps make $10,000 a month, then 0.5% of revenue above that, never more than $999 a month; Enterprise is custom. The server is AGPL-3.0 and the SDKs are MIT.

Is RevenueDot an open-source RevenueCat alternative?#

Yes. RevenueDot implements the API that the RevenueCat SDKs call, so an app keeps its purchase code and points the SDK at RevenueDot Cloud with one setting, the proxy URL. The server code is on GitHub. RevenueDot is not affiliated with RevenueCat.

Can I self-host RevenueCat?#

No. RevenueCat's backend is a hosted service; only its SDKs are open source (purchases-ios license). The easiest way to get an open-source backend for the RevenueCat SDK is RevenueDot Cloud. If your company requires its own server, RevenueDot's server also runs on Docker and Postgres: see Self-hosting.

Do I have to change my app?#

A new app installs the RevenueDot SDK for its platform and passes its app key to configure; on RevenueDot Cloud nothing else is needed. An app that already ships the RevenueCat SDK changes one line, plus one setting on most platforms:

1. Set the SDK's proxy URL before you configure the SDK: https://api.revenuedot.app on RevenueDot Cloud, or your own server's URL.
2. Turn off the SDK's response-signature check, because RevenueDot cannot sign with RevenueCat's key. See signature verification.

// Point the SDK at RevenueDot Cloud; nothing else in the app changes.
Purchases.proxyURL = URL(string: "https://api.revenuedot.app")!

Every platform's version of this line is in the SDK guides.

How is RevenueDot different from RevenueCat?#

• It costs less. RevenueDot Cloud Pro costs $0 until your apps make $10,000 a month, then 0.5% of revenue above $10,000, never more than $999 a month. RevenueCat charges 1% of all tracked revenue once it passes $2,500 a month (pricing).
• The server is open source under AGPL-3.0, so you can read the code that decides who gets access.
• It is catching up feature by feature. Paywalls, experiments, targeting, the charts, Customer Center and virtual currencies are built; What differs lists what is still missing next to RevenueCat (features).
• It is newer. RevenueCat has a longer track record as a hosted service.

What does it cost?#

RevenueDot Cloud has two plans:

• Pro costs $0 until your apps make $10,000 a month, then 0.5% of revenue above $10,000, never more than $999 a month. It includes every feature, unlimited apps, projects and teammates, organizations, custom roles, single sign-on and email support.
• Enterprise has custom pricing from $50,000 a year. It adds SCIM, long audit retention, compliance exports, a 99.9% uptime SLA, 1-hour support for purchase problems and a commercial licence to self-host. Contact sales.

Building and testing are free, no card needed. Add a card when you go live; Pro costs $0 until your apps make $10,000 a month. After your first live sale you have 14 days to start Pro on the Billing page; your app keeps working either way. See Cloud billing and which plan has which feature. RevenueCat's Pro plan is free up to $2,500 in monthly tracked revenue and then charges 1% of tracked revenue (pricing).

Which licenses apply?#

• The server and dashboard are AGPL-3.0.
• The SDK forks keep RevenueCat's MIT license, with RevenueDot's copyright line added for the changes.
• The importer CLI package, the MCP server and the agent skills are MIT.
• The ee/ folder (RevenueDot Enterprise) is under the RevenueDot Enterprise License.

Details are in LICENSING.md. If you change the server and let other people use it over a network, AGPL-3.0 asks you to offer them your changed source.

Which stores are supported?#

Receipts are accepted today for four app types:

RevenueCat Billing (rcb_) apps can be created, but their receipts answer HTTP 400 with code 7662. Paddle, Roku and Samsung Galaxy Store apps work: see Paddle, Roku and Galaxy Store, and Projects and apps.

Is it production-ready?#

Yes, for the App Store, Stripe and the Test Store today. A real App Store sandbox purchase ran end to end on a physical iPhone on 2026-10-02: Apple's purchase sheet, Apple's notification into RevenueDot, an INITIAL_PURCHASE webhook, access unlocked in the app. A production app has run RevenueDot and RevenueCat side by side since 2026-10-02, with RevenueDot processing its live store notifications and forwarding each one to RevenueCat. Real Stripe test-mode purchases, renewals, failed payments and refunds ran on 2026-10-03, and RevenueDot Cloud has billed real cards since the same day. Google Play, Amazon, Paddle, Roku and Galaxy Store are built and tested against copies of each store's API; their first real purchases are next. The first tagged release is v2026.10.03. Switch safely with the dual run: RevenueDot forwards every store notification to RevenueCat until your numbers match. See Known issues.

Who owns the data?#

On RevenueDot Cloud, RevenueDot stores your customers, purchases, receipts and events for you, and you can read all of them through the dashboard and the REST API. You can download everything a project owns as one archive at any time: see Move projects and export everything. A server you run yourself keeps its data in your own Postgres: see Backups.

Does it support StoreKit 2?#

Yes. The server verifies StoreKit 2 signed transactions (JWS) against Apple's certificate chain. It also accepts StoreKit 1 app receipts, but only when the app's App Store in-app purchase key is set, because an unsigned receipt could be forged. See Connect the App Store.

Does it support Expo?#

Yes. Install the RevenueDot SDK for React Native, @revenuedot/react-native-purchases, through an npm alias, so your code imports react-native-purchases. An app that ships RevenueCat's react-native-purchases can keep it and call Purchases.setProxyURL before configure. Test Store purchases work in Expo Go and on the web today. See the React Native guide.

Does it support current Google Play Billing?#

The server reads subscriptions through the Play Developer API (subscriptionsv2) and acknowledges purchases, which Google requires within 3 days (Google docs). Which Play Billing Library your app uses is decided by the Android SDK version you ship, whether it is the RevenueDot SDK or RevenueCat's. See Connect Google Play.

Do I need a RevenueDot SDK?#

A new app installs the RevenueDot SDK for its platform; it is released for every platform (2026-10-02) and needs no RevenueCat account. An app that already ships the RevenueCat SDK can keep it in proxy mode. The RevenueDot SDKs (MIT) also close gaps proxy mode cannot fix, such as response signing and Android diagnostics going to RevenueCat's servers. See Connect your app and the SDK guides.

Can I keep my RevenueCat API keys?#

Yes. The importer can copy your existing public app keys, so apps already in your users' hands keep working when they switch to your server. See The importer.

Can I migrate without losing subscribers?#

That is the design goal. Import customers and their current access, forward store notifications so RevenueCat and RevenueDot both stay current, compare them, then ship an app update with the proxy URL. See Migrate from RevenueCat. The importer is not on npm yet; run it from source.

Do webhooks look the same as RevenueCat's?#

Yes, same body shape and the same X-RevenueCat-Webhook-Signature style of header, with the same retry schedule of 5, 10, 20, 40 and 80 minutes (RevenueCat webhooks). Some event types are accepted in filters but never sent yet. See Webhooks.

Does it have a dashboard?#

Yes. On RevenueDot Cloud it is at app.revenuedot.app/login. It has overview metrics, customers, catalog, webhooks, API keys and setup health.

Can I test without an App Store or Google Play account?#

Yes, with the Test Store: create a test_store app and use its test_ key. See Test Store.

What happens to paywalls, experiments and Customer Center?#

They work with the stock SDKs: build paywalls in the paywall editor, run experiments with up to four variants, and set up the Customer Center. The importer does not copy RevenueCat's paywalls, targeting rules or experiments, so you recreate them in RevenueDot.

Does the web SDK work?#

purchases-js works with Test Store (test_) keys against RevenueDot. RevenueCat Billing (rcb_) and Paddle purchases do not. For real payments on the web, use RevenueDot's hosted checkout on your Stripe account (web billing), or post purchases from your own Stripe checkout from your backend (Stripe guide). With the stock SDK, turn off analytics events (flags: { collectAnalyticsEvents: false }), because the stock SDK sends them to RevenueCat. See the web guide.

Can I sell my app's subscription on the web?#

Yes, on your own Stripe account. Connect Stripe with a restricted key, add a web config, and let RevenueDot create your web products in Stripe. Then share a purchase link for an offering, or publish a multi-step funnel. Buyers pay on Stripe Checkout, and the purchase gives the same entitlements as an in-app purchase. See Sell on the web with Stripe.

How does a web purchase reach the app?#

Two ways. If the checkout knew the buyer's app user id (a purchase link with ?app_user_id=, or the iOS paywall's web checkout), the purchase is on that user at once: customerInfo shows it the next time the app asks. Otherwise the buyer gets a redemption link, on the success page and by email. It opens your app with <scheme>://redeem_web_purchase?redemption_token=…, and your app passes it to Purchases.shared.redeemWebPurchase(...). The web purchase then moves to the app's user. See Redemption links.

Can AI agents set it up?#

Yes. The hosted MCP server is live at https://mcp.revenuedot.app/mcp: your client signs in with OAuth, or sends a secret key. It has 17 tools for the catalog, customers, access grants, webhooks and import status (revenuedot/mcp). The local version is on npm: npx -y @revenuedot/mcp. Agent skills for Claude Code, Codex and Cursor are in revenuedot/agent-skills.

Where do I report a bug?#

Open an issue on GitHub. Report security problems privately through the repository's Security tab, or email security@revenuedot.app.

Related#

• What is RevenueDot?
• Known issues
• Blog: Introducing RevenueDot