RevenueCat Alternative: Affiliateo vs RevenueCat and Adapty

Jamal Brooks·8 min read

Key Takeaways

  • •As of November 2026, RevenueCat is free up to $2,500 in monthly tracked revenue and then 1% of what you track; Adapty is free under $5,000 a month and then 1% of monthly tracked revenue.
  • •Affiliateo connects to the App Store and Google Play directly and shows revenue the RevenueCat way: MRR, ARR, active trials, churn, trial conversion and customers as people.
  • •Affiliateo does not build or A/B test paywalls, run the purchase flow or manage entitlements, so your app keeps its StoreKit or Play Billing code and its own purchase check.
  • •Affiliateo adds an affiliate program with one device-routed link and free app access for affiliates, and charges 1% only on app sales an affiliate brought you.
  • •Affiliateo also works alongside RevenueCat and Adapty, so you can keep your purchase SDK and add affiliates and revenue by source.

The short answer

If you are looking for a RevenueCat alternative, the first thing to know is what RevenueCat actually does for you. It does two jobs:

  • On the phone: an SDK that runs purchases, checks who has paid (entitlements), and shows paywalls you can design and A/B test.

  • On the server: it listens to the App Store and Google Play, keeps every subscription's state, and turns it into charts like MRR, churn and trial conversion.


Affiliateo replaces much of the server job. It connects to the App Store and Google Play directly, reads every sale, renewal and refund, and shows revenue and customers the way RevenueCat does: MRR, ARR, active trials, churn and more. It also adds things RevenueCat is not built for: an affiliate program, free app access for affiliates, and revenue split by where each customer came from.

Affiliateo does not replace the phone job. It has no paywall builder, no paywall A/B tests, and no entitlement system. Your app still makes the purchase with StoreKit or Google Play Billing, and still decides who gets the paid features. Affiliateo's own docs say to pick RevenueCat if you want "entitlement caching, paywall A/B testing" or other RevenueCat-specific features.

And you don't have to choose. Affiliateo also works with RevenueCat and Adapty, side by side.

RevenueCat pricing and Adapty pricing

Here is what each charges as of November 2026, from their own pricing pages.

RevenueCatAdapty
FreeUp to $2,500 in monthly tracked revenueWhile you earn under $5,000 a month
Paid1% of what you track once you pass $2,5001% of monthly tracked revenue after you pass $5,000
IncludesPaywall editor, A/B testing with remote config, charts, integrationsPurchase infrastructure, paywall builder, A/B tests, revenue analytics
EnterpriseCustom pricingCustom pricing

RevenueCat also lists Growth Tools (paywalls, web-to-app funnels and A/B/n testing) for teams that bring their own infrastructure, priced at 1% of tracked revenue on the conversions those tools drive. Adapty sells paid add-ons, such as Refund Saver at 0.2% of monthly revenue.

Both are fair prices for what they do. The question is whether you use all of it.

What Affiliateo replaces today

Direct App Store and Google Play connections

Affiliateo connects to both stores without a third party in the middle.

Apple App Store. Affiliateo uses Apple's App Store Server Notifications V2 and the App Store Server API, with your In-App Purchase key. With Apple's Server URL pointed at Affiliateo, sales show up within seconds. Without it, Affiliateo reads Apple's notification history every hour, so sales still arrive within about an hour. Refunds are recorded, and a Family Sharing revocation is treated the same as a refund.

Google Play Billing. Google Play Billing is Google's system for selling one-time products and subscriptions in Android apps. Affiliateo connects through the Google Play Developer API with a service account. Google's real-time developer notifications (through Pub/Sub) are optional. With them, sales show up within seconds. Without them, Affiliateo checks each subscription with Google when its period ends, reads refunds daily, and finds a new purchase when your app reports it with the SDK's purchase call. Either way it records renewals, trials that turn paid or end unpaid, failed payments, cancellations, expiries and pauses.

How a purchase is matched to a person. Your app passes a tag with each purchase: StoreKit's appAccountToken on iOS, or Play Billing's obfuscatedAccountId on Android. The store stamps it on the sale, every renewal and every refund. The tag can be the one Affiliateo's SDK hands out, or your own account id if you pass that same id to the SDK's identify call at sign-in. On Apple, your own id has to be a UUID.

Revenue charts, the RevenueCat way

The Revenue app shows six cards: active trials, active subscriptions, MRR, revenue over 28 days, new customers and active customers. You can view all apps or one, and filter by source: affiliate, ad or organic.

The charts include:

  • ARR

  • Paid subscriptions and active subscriptions movement

  • Churn

  • The trial conversion funnel and conversion to paying

  • Downloads, download to trial, trial to paid and download to paid


A Conversions page adds ARPU, ARPPU, refund rate, month 2 and year 2 renewal, median time to trial and to first payment, and realized LTV by month. You can break it down by plan, store, country, source or campaign. Every sale, renewal, trial, refund and subscription change is in a transactions list.

If you want to sanity-check your churn numbers, try our churn calculator.

Customers as people, not devices

A customer in Affiliateo is a person. When your app and website call identify with the same user id, their phones and browsers become one customer. You can look anyone up by any id: Affiliateo's, your app's own user id, a RevenueCat id, or a Stripe or store id. Each customer shows devices, last seen, attribution, subscriptions, spend, history and your own note.

Sales sent to ad networks

Affiliateo can send each app's first payments to Meta, TikTok and Snapchat as app events, so app campaigns can aim at people who pay instead of people who install. You can send purchases, trial starts or both. Renewals and refunds are not sent. Google is not on this list, because Google Play or Firebase carry its app conversions, and Apple Ads takes no conversions.

Affiliates and free access

This is the part RevenueCat and Adapty don't do. Affiliateo runs an affiliate program for your app:

  • Each affiliate gets one link. iPhones open your App Store page, Android phones open Google Play, and everyone else goes to your website.

  • Commissions on App Store and Google Play sales can go up to 70%, because the stores take up to 30%.

  • You can give an affiliate free access to your paid app for 1 week, 1 month, 3 months, 1 year or forever, or give it to every affiliate who joins. It ends by itself, nothing renews, and nobody is charged.


On RevenueCat apps, free access is given as a promotional entitlement in your own RevenueCat project. On App Store, Google Play, Adapty and Stripe apps, your app adds two SDK calls and unlocks while Affiliateo says access is active. See the mobile app affiliate program page and the affiliate docs for setup.

What Affiliateo does not do

Be clear about this before you remove anything from your app.

  • No paywalls. Affiliateo does not build, host or A/B test paywalls. Your paywall is your own code.

  • No purchase flow. Your app calls StoreKit or Google Play Billing itself and passes the tag. Affiliateo reads the result from the stores.

  • No entitlements. Affiliateo does not tell your app who has paid. Its docs say to keep the purchase check you already have. Free access for affiliates is an extra check next to it, not a replacement.

  • No single cross-store SDK for purchases. The native connections are separate: Apple native covers iOS only and Google Play native covers Android only. RevenueCat covers both stores in one integration.

  • One Apple Server URL per app. Apple allows one Server URL per environment per app. If your own backend already uses it, you either forward Apple's notifications to Affiliateo (the docs call it a roughly 20-line proxy) or accept hourly updates.

  • Google needs a Cloud project. You create a service account in Google Cloud. RevenueCat is easier if you don't want to manage that.

  • An Adapty caveat. A website purchase that only Adapty reports is recorded, but its refund is not taken back.


If paywall experiments are how you grow, keep RevenueCat or Adapty. That is not a weakness to hide. It is a different product.

Using Affiliateo with RevenueCat or Adapty

Most teams keep their purchase SDK and add Affiliateo next to it.

With RevenueCat. You paste a RevenueCat V2 secret key into Affiliateo, and Affiliateo creates a webhook in your RevenueCat project. Its docs say it never calls subscriber, customer, entitlement, offering or receipt endpoints. The key is only used to install and verify that webhook. If you also connect Apple directly, you paste Affiliateo's URL into RevenueCat's forwarding field, and RevenueCat passes every notification on unchanged, so both keep working. On Google Play, you pick the Pub/Sub topic RevenueCat already made, and both hear every notification.

With Adapty. Adapty is one of the supported mobile providers, next to RevenueCat, the App Store, Google Play and Stripe. You connect it from the dashboard.

With a website too. If you sell on the web through Stripe or Paddle as well, connect that account directly, so refunds and renewals are exact. A website purchase reported by both is counted once.

Pricing compared

Affiliateo does not charge a percentage of all your app revenue. Apps open to affiliates need no plan. Affiliateo takes a 1% platform fee on app sales an affiliate brought you, and sales nobody referred are free. Apps without affiliates that want Live Chat, tracking and funnels pick a monthly plan instead. The fees page has the details.

Here is an example. Say your app tracks $20,000 a month, and affiliates brought in $2,000 of it.

Monthly cost
RevenueCat1% of what you track: $200
Affiliateo1% of the $2,000 affiliates brought: $20

Adapty's paid plan is also 1% of monthly tracked revenue once you pass $5,000 a month. If you keep RevenueCat or Adapty and add Affiliateo, you pay both. Affiliateo's docs say RevenueCat pricing applies independently.

Store fees don't change

No tool changes what Apple and Google keep. As of November 2026:

  • Google Play lists a 15% service fee on auto-renewing subscriptions. In Australia, the EEA, Japan, the UK and the US, that is split as 10% plus a 5% billing fee. Rates for other products depend on your tier and region, so check Google's service fee page.

  • Apple's App Store Small Business Program gives a reduced 15% commission to developers who made up to $1M in proceeds the year before, and to new developers.


Which setup fits you

  • You rely on paywall experiments and remote config: keep RevenueCat or Adapty. Add Affiliateo if you want affiliates and revenue split by source.

  • You already have your own StoreKit and Play Billing code and your own paywall: connect Affiliateo to the stores directly. You get revenue charts, customers and affiliates with no third party in your payment path.

  • You are starting from zero on both iOS and Android: a purchase SDK like RevenueCat saves you real work. You can add Affiliateo on top later without changing your purchase code.

  • Affiliates or creators are a growth channel for you: Affiliateo is built for that part, whichever purchase setup you keep.


Before you remove any SDK, list what your app calls today. If it calls anything that checks access or shows a paywall, that code needs a replacement, and Affiliateo is not it.

revenuecat alternativerevenuecat pricingadaptygoogle play billingapp subscriptions

Written by Jamal Brooks

Jamal is a product engineer at Affiliateo who writes about payments, integrations, and technical best practices.

Frequently Asked Questions

Related Articles