# Recurr

> App-to-web subscriber migration for mobile apps. Move IAP subscribers to web rails, recover margin, free up cash flow, and gain a direct subscriber relationship.

## Docs

- [Apple - App Store guidelines and out-of-app comms](https://recurr.dev/docs/compliance/apple.md): How Recurr keeps migration outside the app binary and aligned with Apple's current out-of-app communication rules.
- [EU Digital Markets Act](https://recurr.dev/docs/compliance/eu-dma.md): What the DMA means for app-store billing in the EU, and how the migration framework operates inside it.
- [Google Play — out-of-billing communication](https://recurr.dev/docs/compliance/google-play.md): Google's stance on developer-to-user communication about external subscription options.
- [FAQs](https://recurr.dev/docs/faqs.md): Common questions from prospects and customers. Updated as patterns emerge.
- [For finance](https://recurr.dev/docs/for-your-role/finance.md): The finance lens on migration: net-of-fees math, cash-flow timing, payback, and what to model before pilot reservation.
- [For founders](https://recurr.dev/docs/for-your-role/founders.md): What migration looks like from the seat that owns the decision: ROI, risk, time-to-decide, and what happens during the engagement.
- [For growth](https://recurr.dev/docs/for-your-role/growth.md): What migration unlocks for growth: pricing flexibility, regional offers, paid acquisition economics, and the lifecycle foundation web rails create.
- [For tech](https://recurr.dev/docs/for-your-role/tech.md): The CTO / engineering-lead lens: integration surface, ongoing burden, security model, and store-policy compliance.
- [Multi-axis cohort selection](https://recurr.dev/docs/framework/cohort-selection.md): Five dimensions used to scope each migration wave: tenure, geo, engagement, renewal window, and plan.
- [Matched IAP holdouts](https://recurr.dev/docs/framework/matched-iap-holdouts.md): How the framework measures migration impact: a matched comparison cohort kept on IAP, sized to detect churn deltas without slowing the rollout.
- [Operational safeguards](https://recurr.dev/docs/framework/operational-safeguards.md): The mechanics most teams don't think about until they're mid-cutover. Each one is the difference between a clean migration and a churn spike.
- [Pilots and waves](https://recurr.dev/docs/framework/pilots-and-waves.md): Why migration runs in waves, what the pilot wave is doing, and how each wave gates the next.
- [What is app-to-web subscriber migration?](https://recurr.dev/docs/getting-started/app-to-web-subscriber-migration.md): How mobile subscription apps move existing app-store subscribers onto web billing while preserving app access, entitlement state, and user experience.
- [Glossary](https://recurr.dev/docs/getting-started/glossary.md): Plain-English definitions for the migration, billing, pricing, and cohort terms used across Recurr's docs.
- [How it works](https://recurr.dev/docs/getting-started/how-it-works.md): Audit → Migration Review → Pilot → Full migration. Wave-by-wave, gated on retention and payback.
- [Model assumptions](https://recurr.dev/docs/getting-started/model-assumptions.md): The assumptions behind Recurr's public audit and docs: store fee rate, web-billing cost, migration cases, settlement timing, and what gets refined later.
- [Who it's for](https://recurr.dev/docs/getting-started/who-its-for.md): The fit profile for migration: $1M+ ARR subscription apps with material IAP exposure.
- [Branded checkout + DNS](https://recurr.dev/docs/integration/branded-checkout.md): Subscribers go through your branded subdomain on web checkout — same design, same domain, same trust signals.
- [Entitlements sync](https://recurr.dev/docs/integration/entitlements-sync.md): How Recurr connects to your existing entitlement source so the app's existing subscription check continues to work.
- [Identity continuity](https://recurr.dev/docs/integration/identity-continuity.md): Apple and Google Sign In are first-class on the web checkout. Subscribers continue with the same identity provider they used in-app.
- [What you actually integrate](https://recurr.dev/docs/integration/no-sdk.md): No SDK, no app release, no migration build on your roadmap. Here's the actual integration surface.
- [Stripe Connect](https://recurr.dev/docs/integration/stripe-connect.md): Web payments settle directly to your Stripe account. Recurr's platform fee is taken as an application fee on each charge.
- [Welcome to Recurr](https://recurr.dev/docs/introduction.md): App-to-web subscriber migration for mobile apps. Move IAP subscribers to web rails - recover margin, free up cash flow, gain a direct subscriber relationship.
- [App-store fees, in plain terms](https://recurr.dev/docs/opportunity/app-store-fees.md): What Apple and Google actually charge — the schedule, the qualifying conditions, and what your blended rate ends up looking like.
- [The cash-flow injection](https://recurr.dev/docs/opportunity/cash-flow-injection.md): The store-to-web settlement timing difference creates a one-time working-capital release during migration.
- [How the margin compounds](https://recurr.dev/docs/opportunity/margin-compounding.md): The recovery isn't a one-time event. Every new subscriber acquired post-migration routes through the same lower fee structure from day one.
- [Where the recovery comes from](https://recurr.dev/docs/opportunity/where-recovery-comes-from.md): Net-of-fees math: gross store fee minus web-billing all-in cost equals what reaches your P&L.
- [Compliance posture](https://recurr.dev/docs/trust/compliance-posture.md): Where Recurr stands on SOC 2, GDPR, PCI, and the standard compliance questions enterprise security reviews ask.
- [Data handling](https://recurr.dev/docs/trust/data-handling.md): What subscriber data Recurr processes, how long it's retained, and what's exportable or removable on request.
- [Infrastructure](https://recurr.dev/docs/trust/infrastructure.md): What runs Recurr — hosting, databases, payments, email — and the security posture of each underlying vendor.
- [Portability and reversibility](https://recurr.dev/docs/trust/portability-and-reversibility.md): What you keep if you leave Recurr — your Stripe account, your subscribers, your branded subdomain, the migration outcome. Migration is permanent without making you locked-in.
- [Founder-led delivery](https://recurr.dev/docs/working-with/founder-led-delivery.md): Why migrations today run with the founder in the room from pilot through go-live, and what that means for your engagement.
- [The Migration Analysis](https://recurr.dev/docs/working-with/migration-analysis.md): Post-call decision artifact summarizing the migration economics, pilot scope, risks, and commercial path before pilot reservation.
- [From Migration Review to pilot kickoff](https://recurr.dev/docs/working-with/pilot-path.md): How a buyer moves from audit to Migration Review, Migration Analysis, pilot slot, and kickoff.
- [Pilot reservation](https://recurr.dev/docs/working-with/pilot-reservation.md): How the pilot starts: reservation terms, what's included, the pre-kickoff refund window, and how the fee is treated against migration.
- [Pricing model](https://recurr.dev/docs/working-with/pricing-model.md): How Recurr's platform fees, pilot fee, full migration scope, Stripe processing, and annual commitment fit together.
- [Technical readiness](https://recurr.dev/docs/working-with/technical-readiness.md): The checklist for whether an app can run a Recurr pilot without adding migration work to the product roadmap.

## OpenAPI Specs

- [openapi](https://recurr.dev/docs/api-reference/openapi.json)