Skip to main content
Subscribers should experience the migration as an update from your product, not a detour through a vendor. Configuration is the work that makes Recurr’s surfaces feel native to your brand.

​
What gets configured

​
Surface mounting

Recurr surfaces can be mounted in a few patterns depending on brand, technical, and SEO requirements. The common path is a branded subdomain:
  • billing.customer.com
  • help.customer.com
  • checkout.customer.com
  • go.customer.com
Some customers prefer a path on the primary domain, such as customer.com/billing or customer.com/help. That usually requires a reverse proxy or edge-routing setup owned by the customer. Subdomains are usually faster to launch and easier to isolate operationally. Path-based mounts can feel more native, but they require more customer-side web infrastructure and coordination.

​
Who approves

The customer approves brand, copy, support policy, offer framing, and any subscriber-facing language. Recurr prepares the surfaces and operates the workflow.

​
What changes over time

During Nostos, configuration is focused on migration. During Oikos, the same brand and surface layer supports the lifecycle motions — acquire, retain, and grow — and keeps carrying migration for each new store cohort that matures.

​
Continue through Oikos

Previous: measurement and reporting

See how Recurr measures migration, lifecycle motions, cohort health, and web-book growth.

Next: subscriber experience performance

See how Recurr keeps subscriber actions fast, clear, and low-friction.