Skip to main content
Recurr should not create a new lock-in problem while solving app-store lock-in. The standard model is that you own the payment rail and Recurr operates on top of it.

​
What you keep

  • Your Stripe account, or scoped Paddle setup where applicable
  • Your subscriber records
  • Your subscription and payment data in the rail
  • Your domain and branded surfaces where configured
  • Your access model and entitlement provider
  • Your data exports and reporting history

​
What changes if you leave

Recurr would stop operating the Oikos layer:
  • Kairos decisioning
  • Migration workflows, including ongoing ascension of new store cohorts
  • Lifecycle motions
  • Recurr-operated subscriber surfaces
  • Cohort reporting and program operations
Your underlying billing rail should continue independently of Recurr.

​
Why the rail matters

Customer-owned Stripe is structurally portable because the billing account is yours. Paddle portability depends on the Paddle model and should be scoped before launch where Paddle is used.

​
What to review in diligence

Legal, procurement, and technical teams should review:
  • Data export scope
  • Access continuity without Recurr-operated motions
  • Domain and sender ownership
  • Payment rail access
  • Subscription record ownership
  • Termination and transition obligations in the agreement