vercel-platforms

Implement multi-tenant and multi-project platforms on Vercel with tenant routing and custom domains.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/skills --skill vercel-platforms-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-platforms
Source: https://github.com/leonardoacosta/skills/tree/main/web-frontend-kit/skills/vercel-platforms
Command: npx skills add https://github.com/leonardoacosta/skills --skill vercel-platforms-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @vercel/sdk, @vercel/edge-config, @upstash/redis, tldts, and includes references (resource) components.

What problem does it solve? Building a platform that serves many customers from Vercel requires solving tenant routing, wildcard DNS, per-tenant SSL, custom domain verification, and programmatic project provisioning — each with plan gates and edge cases that are easy to get wrong. ## Core Features & Use Cases - Tenant Routing: Resolve tenants from subdomains, custom domains, paths, or preview URL prefixes using Next.js middleware/proxy, with rewrite-vs-redirect guidance and local development handling. - Domain Management: Configure wildcard domains, customer custom domains, verification flows, and automatic SSL, including paid-plan gates like custom_domain_needs_upgrade. - Programmatic Provisioning: Create Vercel projects, deployments, and domains per tenant via the Vercel SDK, plus prebuilt Platform Elements Actions and Blocks. - Use Case: You are building a white-label docs platform where each customer gets customer.yourapp.com or brings their own domain. Use this Skill to set up wildcard DNS, middleware tenant resolution with Edge Config lookups, and a custom-domain onboarding flow. ## Quick Start Use the vercel-platforms skill to set up subdomain-based tenant routing for my Next.js app on Vercel.

Frequently Asked Questions about vercel-platforms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a multi-tenant app on Vercel with subdomains?

Add a wildcard domain like *.yourapp.com to your Vercel project, point the apex at Vercel's nameservers, then use Next.js middleware to extract the subdomain, look up the tenant, and rewrite requests to an internal tenant route such as /s/{subdomain}.

Multi-tenant vs multi-project on Vercel: which should I choose?

Choose multi-tenant when all customers run the same code with different content, deployed once. Choose multi-project when tenants ship their own code or need hard infrastructure isolation, accepting the overhead of managing one Vercel project per tenant.

Why is my Vercel wildcard domain not issuing SSL certificates?

Wildcard domains require Vercel's nameservers (ns1.vercel-dns.com and ns2.vercel-dns.com) for certificate issuance. A CNAME setup will not work for wildcards, which is the most common multi-tenant setup failure.

Can I add customer custom domains on the Vercel Hobby plan?

No. Adding a customer domain on the Hobby plan returns a custom_domain_needs_upgrade error stating domain creation requires a premium account. Design bring-your-own-domain flows around a paid plan.

How do I let tenants test on Vercel preview deployments?

Use preview URL prefixes of the form tenant---preview-url, which route to the deployment while your code receives the full hostname. This requires a custom Preview Deployment Suffix, a billing add-on included on Enterprise and enable-able on Pro.

Does Next.js 16 still use middleware.ts for tenant routing?

Next.js 16 renames the convention to proxy.ts with an exported proxy function, though the logic is identical. Vercel's docs are mid-migration and inconsistent, so check your Next major version before copying any snippet.