Recurr is designed for apps that already have the basic subscription infrastructure needed to support web billing alongside app-store billing.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.
Required for a pilot
Central entitlement source
RevenueCat, Adapty, or a custom backend that can read store subscription state and accept web subscription state.
Subscriber reachability
Email or another owned contact point for the majority of subscribers in the pilot cohort. Apple private relay counts if mail is deliverable.
Stripe readiness
An existing Stripe account or a finance owner who can complete Stripe Connect onboarding.
DNS access
Ability to add a CNAME for branded checkout, such as
subscribe.yourdomain.com.Analytics access
Subscriber-level fields for cohorting: plan, tenure, renewal date, geo, engagement, and lifecycle state where available.
Support owner
A named owner for migration-related subscriber questions during pilot waves.
Not a current fit
StoreKit-only apps with no centralized entitlement source are not a current fit for Recurr. Recurr can integrate with RevenueCat, Adapty, or a custom backend. It does not currently add a new mobile SDK or replace a StoreKit-only entitlement architecture. That may become a future platform direction, but it is not part of the current migration offer.Expected engineering load
For apps that meet the readiness profile:- Initial integration is typically 2-4 engineering hours.
- Active migration review is typically 1-2 hours per week.
- No app release is required.
- No migration build goes onto the product roadmap.