Indie developers just want server-side receipt validation and subscription state sync, but are pushed into a full platform SDK and revenue-share pricing.
Indie iOS and Android developers
Flat tiers by MAU or validation volume starting at $9–29/mo; avoid revenue-share pricing
RevenueCat is powerful but requires its SDK, gates the free tier by monthly tracked revenue (roughly $2.5k), and locks subscription data inside its platform — too heavy for developers who only want server-side validation.
A server-only mobile subscription backend: send an App Store or Google Play receipt/transaction ID, receive current subscription state, and get webhooks — no client SDK required.
Mobile subscriptions involve StoreKit 2 / App Store Server API, Google Play Developer API, renewals, refunds, grace periods and cross-platform sync — easy to get wrong in-house. RevenueCat-style platforms require SDK integration and price by tracked revenue, which is overkill for developers who only need validation plus state sync.
One-to-three person indie mobile teams shipping subscription apps with their own backend (Node, Django, Supabase) who do not want a third-party SDK owning subscription logic.
Subscription apps keep growing, and RevenueCat's SDK lock-in and revenue-based pricing are recurring complaints on Reddit and Indie Hackers. "I just want to validate a receipt, not integrate an SDK" is a specific, frequent request.
Flat tiers by MAU or validation volume starting at $9–29/mo, explicitly no revenue share — the clearest pricing differentiator versus incumbents. Exact numbers need research.
Medium. Key challenges: Apple App Store Server API (JWS verification, key management), Google Play Developer API service-account auth, the subscription state machine (renewal, refund, grace period, upgrade/downgrade), and reliable idempotent webhooks.