Yes, you can absolutely build this! You don't need to create one Vercel project and repo per site. Instead, you can use Vercel's multi-tenant architecture with a single Next.js application that serves multiple sites dynamically based on the domain 1.

How Multi-Tenant Architecture Works

With Vercel's multi-tenant approach, you have:

• One codebase (Next.js app)
• One Vercel deployment
• Multiple domains pointing to the same deployment
• Dynamic content served based on the requesting domain

Each tenant gets their own domain or subdomain, but you only have one Next.js deployment running on Vercel 1.

Architecture Overview

Here's how you can structure this with Sanity:

Key Benefits

1. Single Codebase: One Next.js app serves all sites
2. Dynamic Content: Content is fetched from Sanity based on the requesting domain
3. Automatic SSL: Vercel handles SSL certificates for all domains 1
4. Scalable: Can handle thousands of sites from one deployment
5. Cost Effective: No need for multiple deployments

Domain Management

Subdomains

For subdomains like tenant1.yourdomain.com, add a wildcard domain *.yourdomain.com to your Vercel project 1.

Custom Domains

For custom domains, you can programmatically add them using the Vercel API as shown in the code above 1.

Sanity CMS Integration

Your Sanity schema would include:

• Sites: Each with domain configuration, theme settings, and content
• Pages: Individual pages for each site
• Components: Reusable content blocks
• Themes: Color schemes, fonts, layouts

Non-technical users can:

1. Create new sites through Sanity Studio
2. Customize themes and content
3. Add custom domains
4. Manage all sites from one interface

This approach gives you the flexibility of a multi-tenant architecture while maintaining the simplicity of a single codebase and deployment.

To configure the generation, complete these steps: