Infrastructure - Recurr

Recurr’s infrastructure supports the operating layer around the customer’s payment rail.

Infrastructure areas

Area	Purpose
Application hosting	Customer docs, migration hub, subscriber surfaces, and internal tooling
Database	Program, cohort, subscriber, event, and reporting state
Email	Migration, lifecycle, and transactional messaging
Analytics	Funnel, cohort, and product analytics
Error monitoring	Runtime errors, failed jobs, and operational alerting
Payment rail integrations	Stripe by default; Paddle scoped by early access

Principle

Recurr should process only the data needed to operate migration, reporting, and Oikos motions. The customer’s payment rail remains the source of truth for payments. The customer’s access model remains the source of truth for app access.

During diligence

Customer security teams can request:

Infrastructure overview
Data-flow summary
Subprocessor list
DPA
Incident response posture
Retention and deletion posture