Skip to main content
Recurr is designed to avoid a migration build inside the mobile app. The integration sits around the app: payment rail, web surfaces, subscriber identity, access continuity, analytics, and reporting.

Typical integration areas

No app release as the default

The migration path is designed to run through owned channels and web surfaces. That means no SDK and no app release for the migration itself in the standard path. Some customers may still choose to add app-side improvements later, but they are not the starting requirement for Nostos.

What your team actually does

Most customer work is approval, access, and DNS. Recurr handles configuration, mapping, testing, and operational setup.

Typical customer inputs

Before the pilot, Recurr usually needs:
  • A technical owner
  • Access to the relevant systems or exports
  • Payment rail and domain approvals
  • Subscriber identity and access-state context
  • Analytics and cohort signal context
  • Support and escalation policy inputs

What Recurr operates

Recurr operates the migration workflow, subscriber surfaces, cohort reporting, and Oikos motions. For the signal layer, see Analytics and subscriber signals.