I’m interested in how others are handling redirect strategies for legacy domains in the SaaS environment.
In private cloud setups, we’ve typically relied on existing edge infrastructure (e.g. Cloudflare, Azure Front Door) to manage legacy domain redirects. However, for clients moving fully to the SaaS model and looking to decommission those services, the approach becomes less clear.
The documentation (https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management#manage-channel-domains-in-xperience-portal) notes that domain limits apply per channel, with the option to request increases via sales.
Given that constraint, what strategies are you using in practice?
- Requesting additional domains purely for redirect handling
- Retaining a third-party service such as Cloudflare
- Using an alternative approach
Interested to hear how others are balancing simplicity, cost, and maintainability here.
Environment
- Execution environment: SaaS