Multi Tenant Architecture

Walks you through building a white-label SaaS platform on Cloudflare or Vercel, handling the messy parts like subdomain routing, custom domain verification, tenant isolation, and cookie separation. Pushes you to separate your brand domain from tenant workloads early (a phishing site on random.acme.com tanks your whole domain), reminds you that PSL submission takes weeks, and forces a choice between per-tenant Workers or a shared Next.js app with tenant scoping. The workflow is opinionated and sequential: pick a platform, choose subdomain vs custom domain, wire up middleware or dispatch namespaces, then map limits to pricing tiers. Useful when you're past the MVP and need production multi-tenancy that won't leak data or reputation.

skills.sh installs: 1.8K
GitHub stars: 191
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add mblode/agent-skills --skill multi-tenant-architecture --agent claude-code

Installs into .claude/skills of the current project.

Files

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 (use scaffold-nextjs), or the content of per-tenant SEO files once routing serves them dynamically: sitemap entries, canonical URLs, structured data, indexing policy (use seo).