营销与销售
multi-tenant-architecture
Designs tenant isolation, hostname routing, custom-domain lifecycle, and plan limits on Cloudflare or Vercel. Use when asked to "isolate tenant data", "support custom domains", "build a white-label platform", or assess PSL registration. For general module structure use codebase-architecture; for SEO content use optimise-seo.
mblode · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add mblode/agent-skills --skill multi-tenant-architecture技能说明
name: multi-tenant-architecture description: Designs tenant isolation, hostname routing, custom-domain lifecycle, and plan limits on Cloudflare or Vercel. Use when asked to "isolate tenant data", "support custom domains", "build a white-label platform", or assess PSL registration. For general module structure use codebase-architecture; for SEO content use optimise-seo.
Multi-Tenant Platform Architecture (Cloudflare or Vercel)
- IS: platform choice, domain strategy and PSL, tenant identification, compute and data isolation, hostname routing, tenant context propagation, custom domains and SSL, per-tenant static files, and mapping platform limits to plans.
- IS NOT: general folder structure or module contracts (use
codebase-architecture), scaffolding a new repo (usescaffold-nextjs), or the content of per-tenant SEO files once routing serves them dynamically: sitemap entries, canonical URLs, structured data, indexing policy (useoptimise-seo).
Contents
- Platform dispatch (decide first)
- Reference files
- Workflow (order matters)
- Gotchas
- Output schema
- Pre-commit checklist
- Related skills
Platform dispatch (decide first)
| Signals | Platform | Model |
|---|---|---|
| Tenants upload or generate their own code; code-level isolation; edge compute on KV, D1, Durable Objects, R2 | Cloudflare | Dispatch Worker in front of a dispatch namespace of per-tenant Workers; Cloudflare for SaaS for custom hostnames |
| Every tenant runs the same Next.js codebase and differs by content, branding, and plan; ISR, Server Components, Vercel deploys | Vercel | One deployment; proxy.ts resolves the tenant from the hostname; wildcard plus custom domains on the project |
- Pick one platform per product. Fronting a Vercel app with a Cloudflare proxy doubles the TLS and redirect layers and is the usual cause of redirect loops and failed certificate issuance.
- Tenants shipping their own code on Vercel is the multi-project model (one Vercel project per tenant, created with the SDK). It follows the Cloudflare row's isolation reasoning; this skill's Vercel references cover the single-deployment model only.
Reference files
| File | Read when |
|---|---|
| cloudflare-platform.md | Cloudflare chosen: dispatch namespaces, routing, Cloudflare for SaaS custom hostnames, isolation modes, KV and D1 (steps 3 to 7) |
| vercel-platform.md | Vercel chosen: proxy.ts resolution, App Router layout, Global Config lookups, per-tenant static files, custom subpaths, local dev (steps 4 to 7) |
| vercel-domains.md | Vercel chosen: SDK domain lifecycle, DNS targets, verification, wildcard nameservers, SSL, troubleshooting (step 7) |
| data-isolation.md | Step 3 on either platform: shared schema with RLS, schema-per-tenant, database-per-tenant, and the Postgres/Supabase/Drizzle policy pattern |
| psl.md | Step 1 when tenants publish content or run code on sibling subdomains: eligibility, submission, interim cookie controls |
| limits-and-quotas.md | Step 8: dated snapshot of Cloudflare, Vercel, and Neon limits to map onto plans |
agents/openai.yaml | Never during a task: launcher metadata for external runners |
Workflow (order matters)
Copy this checklist to track progress:
Multi-tenant progress:
- [ ] Step 1: Domain strategy and PSL decision
- [ ] Step 2: Tenant identification strategy
- [ ] Step 3: Isolation model (compute and data)
- [ ] Step 4: Deterministic routing
- [ ] Step 5: Tenant context propagation
- [ ] Step 6: Tenant config and least-privilege bindings
- [ ] Step 7: Custom domains and per-tenant static files
- [ ] Step 8: Limits mapped to plans, evidence captured
- Choose the domain strategy
- Put tenant workloads on a dedicated registrable domain (
acme.appfor tenants,acme.comfor brand). One phishing tenant onx.acme.computs the whole domain on blocklists, and a tenant cookie withDomain=acme.comreaches your dashboard. - Keep the dashboard and auth on a different apex from tenant subdomains (
app.acme.comfor the console,*.acme.appfor tenants). - If tenants publish content or run code on sibling subdomains, submit the label directly above the tenant name (
acme.app, orsites.acme.appfor<tenant>.sites.acme.app) to the PSL and start now: there is no SLA. Tenant-owned custom domains need no PSL entry. Otherwise recordNo PSLwith the reason.
- Choose tenant identification (one primary; custom domain as the upgrade path)
- Subdomain
tenant.acme.app: wildcard DNS plus wildcard certificate. The default. - Custom domain
tenant.com: the tenant CNAMEs to you. Paying tenants; reputation shifts to them; needs the onboarding lifecycle in step 7. - Path
acme.app/tenant: no per-tenant DNS or certificates, but no cookie isolation and no branding. Choose it only when tenants will never get a hostname.
- Define the isolation model
- Compute, Cloudflare: one dispatch namespace in untrusted mode; per-invocation
cpuMsandsubRequestslimits per plan; an outbound Worker if tenant code may call the internet. - Compute, Vercel: one deployment, tenant code never executes. If tenants must ship code, move to Vercel multi-project or Cloudflare rather than sandboxing inside the app.
- Data: shared schema with
tenant_idon every tenant-aware table plus RLS is the default; database-per-tenant for regulated or noisy tenants, selectable per plan. See data-isolation.md.
- Route deterministically (tenants never influence routing or see each other)
- Cloudflare: a single
*/*route on the SaaS zone to the dispatch Worker; hostname -> tenant record (KV, D1 on miss) ->env.DISPATCHER.get(script);Worker not found-> 404. - Vercel:
proxy.ts(Next.js 16; `middlewa