Skip to main content

Documentation Index

Fetch the complete documentation index at: https://recurr.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Recurr is built for growth-stage subscription apps where moving billing off Apple and Google moves the P&L meaningfully.

​
The fit profile

Subscription model

Subscription business on iOS or Google Play. Lifetime / pay-once apps don’t get the recurring margin lift that drives the economics.

$1M+ ARR

Below this level, recovered margin is small in absolute terms and the operational complexity of running a migration outweighs the lift.

Material IAP exposure

If most subscription revenue already runs on web, Recurr is additive but not transformative. Migration is the wedge for apps still primarily on app-store rails.

Reachable subscribers

You can email most of your subscriber base. Apple Sign In counts — private relay forwards mail to the user. Most apps at this scale have an account system; reachability is rarely the blocker.

​
Strong indicators

  • Investing in paid acquisition. Recovered margin funds the next cohort.
  • Pricing flexibility wanted. Regional offers, trials, plan tests — all unblocked on web.
  • Older subscriber cohorts. RevenueCat’s 2026 State of Subscription Apps puts ~69% of category revenue in pre-2020 cohorts, which often have the most-mature mix.
  • Founder + finance attention available. Migration is operationally light on your team but does want decision-grade input from someone with full numbers.

​
Likely poor fit

  • Pre-revenue or sub-$1M ARR — the absolute numbers don’t justify the work.
  • Heavy non-IAP revenue mix already.
  • StoreKit-only setup with no centralized entitlement source or backend Recurr can write into.
  • No reliable owned contact path for the subscriber cohorts you would want to migrate.
Not sure if you fit? The 60-second audit tells you the dollar magnitude on your specific numbers — that’s usually a faster signal than the bullet list above.