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.

Yes, with specifics. Recurr operates outside the app binary: email and owned channels reach the subscriber, checkout happens on web, and the app continues granting access through the existing entitlement system. See Apple compliance and Google Play compliance for the policy posture.
The framework is designed to stay in the conservative out-of-app lane: no in-app links to web pricing, no in-app migration messaging, no SDK, and no app release. No vendor can guarantee platform enforcement behavior, but the migration avoids the app-binary surfaces that typically create review risk.
The pilot is built to answer that with data. Each pilot wave runs against a matched IAP holdout - same tenure, plan, engagement, and geo - so churn impact is measurable. The migration does not scale until retention and payback clear the agreed gates.
For apps with a centralized entitlement source, initial integration is typically 2-4 engineering hours: entitlement access, Stripe Connect, DNS for branded checkout, and webhook subscriptions. Ongoing involvement is usually 1-2 hours per week during active migration. No SDK, no app release, no migration build on your roadmap.
StoreKit-only apps with no centralized entitlement source are not a current fit. Recurr can integrate with RevenueCat, Adapty, or a custom backend, but it does not currently add a new mobile SDK or replace a StoreKit-only entitlement architecture.
No. Migration runs in waves on selected cohorts. Subscribers who do not respond stay on IAP, untouched. The framework’s job is to move the cohorts where the economics, retention signal, and user experience justify scaling.
Your current entitlement system continues to work. Recurr writes web subscription state into the same system alongside existing Apple and Google receipts. The app’s runtime entitlement check is unchanged.
Migration creates the rails for pricing control, cleaner attribution, payment recovery, and lifecycle work. Recurr’s current offer focuses on migration, billing, entitlement sync, cohort operations, and reporting. Broader self-serve lifecycle modules are roadmap and partner-scoped.
Apple private relay can work when the relay address is deliverable and stable for the subscriber. Identity continuity is checked during the Migration Review because each app’s account and entitlement setup can differ.
Yes. The Stripe Connect account is in your company’s name, web subscriptions settle to your Stripe account, and subscriber data is exportable. The annual commitment runs to its term; after that, you can exit and continue with your own Stripe and entitlement setup.
The work is densest while subscribers are actively migrating: cohort design, wave operations, observability, gating decisions, and campaign operations. After each migrated subscriber has been on web for 12 months, the Recurr fee moves to the standard 2% platform rate.
Founder plus finance lead is ideal. Tech can join if there are integration questions, but the call works best with the people who understand the economics and can decide whether to pursue a pilot.
Then no pilot slot is offered. The Migration Review is a real qualifier: fit profile, timing, technical readiness, and migration risk all matter. If the path is not credible, the process stops before any paid commitment.
Recurr is a managed migration platform, not a raw billing tool or a strategy-only consultant. The closest comparison depends on what you are optimizing for: speed of migration, low engineering lift, cohort analysis, retention safety, or long-term control. The Migration Review is the right place to compare alternatives against your app’s constraints.
Questions not on this list? Reply to any Recurr email or send to matt@recurr.dev. Common questions land here as patterns emerge.