Overview

Vercel for Platforms helps you build platforms that serve multiple customers. Choose from two distinct approaches depending on your use case.

Choose your approach

Multi-Tenant

Single codebase serving multiple tenants with their own domains.

Routing, data, and configuration are tenant-aware within one deployment. Use this when the content is unique, but the codebase is the same.

Examples: Mintlify, Fern (documentation platforms), Hashnode, Dub (content platforms), Super (website builders)

Best for: Documentation platforms, content platforms, website builders, SaaS dashboards where all customers share the same application structure.

Learn about Multi-Tenant →

---

Multi-Project

Multiple unique codebases, each with its own Vercel project.

Each tenant has its own repository or deployment generated from a template. Use this when agents or users are deploying unique codebases.

Examples: Spawn, Orchids (AI coding platforms), v0 (generative UI), Replit (code environments)

Best for: AI coding platforms, per-customer isolated environments, user-generated applications, platforms where each tenant needs custom code.

Learn about Multi-Project →

---

What you can build

Website builders: Let customers create sites, connect domains, and publish instantly.

E-commerce platforms: Spin up tenant stores from a template, connect headless APIs, and route custom domains.

AI coding platforms: Create collaborative coding environments with real-time features, custom domain support, and integrated deployment options.

SaaS dashboards: Serve tenant-aware dashboards from a single codebase with strict data boundaries.

Documentation and knowledge bases: Multi-tenant docs with search and custom domains per workspace.

Developer platforms: Provision apps from templates, enforce standards, and give teams routing and domain controls.

How it works

Multi-Tenant architecture

With Multi-Tenant, you deploy a single Next.js application to Vercel. Your middleware identifies which tenant a request belongs to (by subdomain or custom domain), then loads that tenant's data and configuration. All tenants share the same codebase but see different content.

You can offer:

• Wildcard subdomains like tenant1.yourapp.com, tenant2.yourapp.com
• Custom domains like tenant1.com, tenant2.com
• Automatic SSL certificates for all domains

Multi-Project architecture

With Multi-Project, you programmatically create separate Vercel projects for each tenant using the Vercel SDK. Each project has its own codebase, deployments, and domains. This gives complete isolation between tenants.

You can:

• Create projects from templates
• Deploy unique code per tenant
• Manage deployments programmatically
• Configure domains per project

Getting started

The fastest way to get started depends on your use case:

Multi-Tenant: Clone the Platforms Starter Kit and configure wildcard domains.

Multi-Project: Use the Vercel SDK to programmatically create and deploy projects.

Comparison table

Which approach should I choose?

Choose Multi-Tenant if:

• All tenants use the same application structure
• Content and branding differ, but functionality is the same
• You want to deploy once and update all tenants simultaneously
• You're building: documentation platforms, content platforms, website builders

Choose Multi-Project if:

• Each tenant needs custom code or unique functionality
• Tenants deploy their own code (AI agents, user-generated apps)
• Complete isolation is required between tenants
• You're building: AI coding platforms, per-customer environments, template-based platforms

Next steps