Hi @steven-tey, Currently, the Next.js SaaS template supports multi-tenancy, allowing subdomains like demo.vercel.pub and app1.vercel.pub etc to function seamlessly. However, subdomains such as app.vercel.pub are not supported because the app subdomain is proxied to the app folder inside the app directory.

This creates two key challenges:

Blocked Subdomains: Subdomains like app are inherently unavailable due to the application's routing configuration.So, i guess, we need to main a reserved list and exclude them as well while creating sites or in create-site api

Future Reserved Subdomains: There is a possibility of requiring certain subdomains to be reserved for internal use (e.g., admin, partners, etc.) or new features in the future. However, these subdomains could potentially be claimed by users, creating conflicts. How would we solved that ?

Questions

• Are there other strategies to handle subdomain conflicts without impacting the user experience?