Skip to main content
Reliability in Recurr means the migration and web-book operating layer behave predictably when real subscribers are involved.

​
Reliability scope

Recurr is responsible for the surfaces and workflows it operates:
  • Migration messaging
  • Branded subscriber surfaces
  • Cohort reporting
  • Oikos lifecycle motions
  • Kairos decisioning
  • Recurr-managed integrations and exports
The payment rail itself remains the customer’s rail. Stripe or Paddle reliability, payout behavior, tax behavior, refunds, and disputes follow the rail and the customer’s setup.

​
Operating posture

Recurr uses controlled rollout because reliability is not just infrastructure uptime. A migration can fail commercially even if every server is up. That is why Nostos uses pilot validation, cohort gates, support monitoring, and holdouts before scale.

​
Incident handling

For Recurr-operated incidents, the response path is:
  1. Detect the issue
  2. Pause affected cohorts or motions where needed
  3. Notify the customer owner
  4. Preserve data and logs
  5. Restore service
  6. Report impact and next steps

​
Customer dependencies

Some reliability risks sit in the customer stack: payment rail configuration, access model behavior, email domain posture, support processes, or analytics destinations. These are reviewed during technical readiness and pilot onboarding.