Multi-Tenant Platforms

A multi-tenant platform serves every customer from one codebase and one Vercel deployment. Next.js Proxy resolves the tenant from the incoming domain or subdomain, and each tenant sees its own content and branding. Start with the concepts, then follow the quickstart.

Concepts

How tenants, domains, routing, and data isolation work.

Quickstart

Build a multi-tenant app with subdomain routing from scratch.

Configuring domains

Add, verify, redirect, and remove wildcard and custom domains with the SDK.

Custom subpaths

Serve tenants from paths like /tenant1 instead of subdomains.

Proxy and routing

Resolve tenants in Proxy and pass context to your app.

Serving static files

Serve tenant-specific static assets from a multi-tenant app.

Preview URLs

Generate per-tenant preview URLs for testing changes before release.

Reference

Domain API, error codes, troubleshooting, and FAQ.

Limits

Domain limits, preview URLs, and SSL options across plans.

Last updated July 28, 2026

Cross-link map: Multi-Tenant Platforms (/docs/platforms/multi-tenant-platforms)

From the Vercel docs graph (built 2026-10-14T10:24:21.026Z), spanning vercel.com docs + KB, nextjs.org, ai-sdk.dev, and other Vercel documentation sites. Full graph as JSON: https://vercel.com/docs/graph.json

Semantically closest pages

Multi-Tenant Platform Concepts — Understand tenants, domains, routing, and architecture for building multi-tenant applications on Vercel for Platforms.
Vercel for Platforms — Build platforms where agents and users deploy apps with isolated projects or shared multi-tenant deployments.
Multi-Tenant Template — Build SaaS applications that serve multiple domains from a single Next.js codebase.
Multi-Project Platforms Concepts — Understand projects, deployments, domains, and architecture for multi-project platforms on Vercel.
Multi-Project Platforms — Give each customer its own Vercel project and deployment, created and managed programmatically with the Vercel SDK.

Prerequisites

Vercel for Platforms — Build platforms where agents and users deploy apps with isolated projects or shared multi-tenant deployments.

This page links to (9)

Multi-Tenant Platform Concepts — Understand tenants, domains, routing, and architecture for building multi-tenant applications on Vercel for Platforms.
Configuring Custom Domains — Add, verify, redirect, and remove wildcard and custom domains for a multi-tenant application using the Vercel SDK.
Configuring Custom Subpaths — Host platform content on custom subpaths of customer domains while maintaining a single Next.js application.
Multi-tenant Limits — Understand the limits and features available for Vercel for Platforms.
Multi-tenant Preview URLs — Test tenant-specific experiences in preview deployments using dynamic URL prefixes.
Proxy and Routing — Resolve tenants and route requests by subdomain, custom domain, or path using Next.js Proxy on Vercel.
Multi-Tenant Platform Quickstart — Set up wildcard domains, custom domains, domain verification, and redirects for a multi-tenant application on Vercel.
Multi-tenant Reference — Reference for the Vercel domain API, error codes, troubleshooting, and FAQ for multi-tenant platforms.
Serving Static Files — Serve tenant-specific static files like robots.txt, sitemap.xml, and llms.txt dynamically using route handlers.

Vercel for Platforms

Concepts

Was this helpful?