Stop guessing which one. Put them side by side.

The grid says what these tools are. This says what builders did about it — one decision per person, changeable whenever you change your mind.

# Tool comparison — RevenueCat vs Autumn vs Creem

Source: Kbaise, a directory of tools that work with Lovable projects.
Pick one and tell me why before writing any integration code.

## RevenueCat (revenuecat)
- URL: https://www.revenuecat.com
- Category: Payments & billing
- Cost: mixed — Free under $2.5k monthly tracked revenue · then 1% of tracked revenue
- What it is: Subscription infrastructure layered on top of Apple and Google in-app purchases, now extended to web billing through Stripe. It normalizes receipts, entitlements, trials and renewals across platforms and adds paywall and analytics tooling. Free under $2,500 monthly tracked revenue, then 1% of tracked revenue.
- Why builders pick it: In-app purchase receipt validation is miserable to build and worse to maintain; RevenueCat reduces cross-platform subscriptions to a single entitlement check and stays free until you have real income.
- Trap: The 1% is charged on revenue before Apple and Google take their 15-30% cut, so the effective bite is larger than it appears. It is not a payment processor — on mobile the app stores remain merchant of record.
- Wiring: npm i @revenuecat/purchases-js
- Full dossier: /api/public/tools/revenuecat

## Autumn (autumn)
- URL: https://useautumn.com
- Category: Payments & billing
- Cost: mixed — Free to ~$8k/mo processed · $375/mo to $50k · self-host free (Apache-2.0)
- What it is: Open-source billing layer that sits between your app and Stripe. It moves pricing from code into config and handles subscription state, usage metering, credits, entitlements and upgrade or downgrade proration, returning Stripe Checkout URLs. Stripe remains the processor, so Autumn is not a merchant of record.
- Why builders pick it: Kills the worst part of a Stripe integration — webhook handling and feature gating — behind calls like check and track, so usage-based AI pricing takes an afternoon instead of a sprint.
- Trap: Not an MoR: Stripe fees and your own global tax obligations still apply on top. The hosted free tier stops around $8k processed per month and the next step is a steep $375/mo, though Apache-2.0 self-hosting is an escape hatch.
- Wiring: npm i autumn-js
- Full dossier: /api/public/tools/autumn

## Creem (creem)
- URL: https://www.creem.io
- Category: Payments & billing
- Cost: paid — 3.9% + $0.40 per transaction, MoR · optional Pro plan $99/mo
- What it is: Merchant of record for indie SaaS and digital products at 3.9% + $0.40 per transaction, the cheapest headline MoR rate in this list. Handles VAT, GST and sales tax across 190+ countries, plus subscriptions, chargeback protection and revenue splits, with payouts on the 1st and 15th.
- Why builders pick it: Roughly a full percentage point cheaper than Paddle or Lemon Squeezy on every sale while still taking tax compliance off your plate — a gap that compounds as revenue grows.
- Trap: Younger and smaller than Paddle or Stripe, so platform risk is real: merchant payouts are documented for only about 86 countries, and routing all of your revenue through a startup processor is itself a bet.
- Full dossier: /api/public/tools/creem

## Rules
1. Prefer the free tier when no budget was stated, and say what the ceiling is.
2. Read the full dossier before integrating.
3. Fetch /api/public/models before writing any AI model ID.

Agents can fetch the same thing: GET /api/public/compare?slugs=revenuecat,autumn,creem