Skip to main content
Oikos is onboarded through Nostos. Migration creates or extends the connected web book; Oikos turns on as that web book comes online.
The pilot is designed around your subscriber base, billing and data setup, and the first cohorts needed to validate uptake, retention, and migration economics. Pilot fees start from $5,000, are sized to your book, and are credited in full against migration fees as the program continues.
A subscriber live and renewing on your own web billing. If they stay on the app stores there is no migration fee at all. If they move and then churn early, the fee only ever applied to what they actually paid before they left.
Fees are billed monthly in arrears. For each migrated subscriber we charge 5% of what they actually pay, month by month, across their first twelve months of billed service on web. There is no lump sum and no qualifying threshold.The twelve months belong to the subscriber, not to the program. Cohorts that migrate later — see ascension — start their own twelve months when they move, at the same 5%.
For each subscriber we migrate, their first year on Oikos is included. After that, they roll into the standard 2% web-book rate.
The full Oikos operating layer for your web book: subscriber surfaces, billing and account flows, Kairos decisioning, lifecycle motions, cohort reporting, and the integrations needed to run them. The fee is tied to successful web payments, not seats, usage tiers, or individual campaigns.
Yes. Oikos runs as the operating layer for the connected web book, so the 2% platform fee applies to all web subscriptions connected to Recurr.If you already have web billing, that usually makes you a stronger fit. The work changes from establishing a new rail to extending the rail you already have, then bringing app-store cohorts onto it over time.
Stripe is the default payment rail. In most engagements, the Stripe account is yours and Recurr operates on top of it. Paddle can be scoped where merchant-of-record coverage or existing Paddle infrastructure makes it the better rail.
No. Recurr fits into your stack. For many apps, RevenueCat, Adapty, Stripe, Paddle, Firebase, or a custom backend remains the system that controls access. Recurr integrates with that model so migrated subscribers continue to receive app access.
The migration path is designed to avoid an app release. Recurr operates through owned channels, branded web surfaces, payment rail integration, and your existing access model.
They remain on app-store billing. Migration is operated in cohorts and waves, not as a forced all-or-nothing cutover.
Ascension is the ongoing migration of new store subscribers onto web billing as they mature. Your app keeps acquiring on the stores, so there is always a next cohort — ascension is what keeps the web book from slowly reverting back toward store billing.It is migration, so it is priced as migration: the same flat 5% of what we move, across each of those subscribers’ first twelve months on web. See when the migration fee becomes due.