Skip to main content
Recurr helps mobile subscription apps move their app-store book onto direct web billing, then run the surfaces and lifecycle motions that grow the web book from there. Most customers start with Nostos, the managed migration program. Nostos is designed for subscription apps with material App Store or Google Play revenue that want to move subscribers onto a payment rail they own without turning migration into a roadmap project. After migration, the operating layer is Oikos. Oikos runs branded subscriber surfaces, lifecycle motions, cohort reporting, and Kairos decisioning across the connected web book.

​
What Recurr does

Nostos

A managed, cohort-by-cohort migration from app-store billing to direct web billing.

Oikos

The growth platform that runs the connected web book after migration.

Kairos

The decisioning engine that chooses the next approved motion for each subscriber.

Customer-owned payment rail

Stripe is the default rail. Paddle support is available by early-access scoping where merchant-of-record coverage is needed.

​
The commercial model

Recurr charges in stages so the buyer can validate before scaling. Migration fees accrue monthly against payments actually collected, rather than landing as a lump sum. We earn only while a migrated subscriber keeps paying.

​
How to use these docs

Start with what store-to-web subscriber migration means, then read how the program works. Finance teams usually go next to pricing, where recovery comes from, and model assumptions. Technical teams should start with the integration overview and access continuity.

​
Who are you?

Founder or CEO

Strategic case, risk controls, pricing shape, and what the pilot is meant to prove.

Finance

Fee mechanics, cash timing, migration economics, reporting, and model assumptions.

Engineering

Integration surface, access continuity, identity, events, security, and no-app-release path.

Product

Subscriber experience, app-access continuity, policy posture, and product guardrails.

Growth

Migration motion, lifecycle paths, offers, cadence, and web-book growth.

Support

Subscriber questions, cancellation guidance, support macros, and escalation paths.

Legal and procurement

Contracts, data, policy posture, payment rail ownership, and portability.

Data and analytics

Cohort reporting, signal inputs, event streams, LTV model integrity, and exports.
These docs explain the operating model. The Migration Hub applies the model before signing; the Migration Dashboard becomes the Nostos operating surface after kickoff.