multi-tenant-architecture

Blueprint multi-tenant SaaS architectures on Cloudflare or Vercel.

Updated Sep 10, 2025
One-click install
npx skills add https://github.com/tillysoso/mv1 --skill multi-tenant-architecture-tillysoso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-tenant-architecture
Source: https://github.com/tillysoso/mv1/tree/main/.claude/skills/multi-tenant-architecture
Command: npx skills add https://github.com/tillysoso/mv1 --skill multi-tenant-architecture-tillysoso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides architecture guidance for building scalable multi-tenant SaaS platforms on Cloudflare or Vercel, covering domain strategy, tenant isolation, routing, and tenant-context propagation.

Core Features & Use Cases

  • Guidance on platform selection (Cloudflare vs Vercel) and the associated design trade-offs.
  • Techniques for tenant identification, isolation models, and deterministic routing.
  • Procedures for per-tenant context propagation, custom-domain onboarding, and per-tenant static file handling.

Quick Start

Define your platform choice (Cloudflare or Vercel) and outline the initial tenant identification, isolation, and routing plan to bootstrap your multi-tenant architecture.

Frequently Asked Questions about multi-tenant-architecture

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

FAQPage Schema
How do I design multi-tenant SaaS architecture for tenant isolation and routing?

Multi-tenant SaaS architecture requires a blueprint for tenant identification, isolation models, and deterministic routing. This involves selecting a platform, defining tenant context propagation, and planning custom-domain workflows to isolate tenants.

What is the best way to handle tenant identification and custom-domain onboarding in a multitenancy platform?

Tenant identification and custom-domain onboarding in multitenancy require procedures for per-tenant context propagation and static file handling. You must map custom domains to specific tenants and ensure context flows correctly across services.

Does Cloudflare or Vercel work better for scalable multi-tenant domain management?

Cloudflare and Vercel both support scalable multi-tenant domain management but involve distinct design trade-offs. Your platform choice dictates how per-tenant bindings, routing, and custom-domain workflows are implemented.

How do I propagate tenant context across services in a multi-tenant SaaS platform?

Propagating tenant context across services in a multi-tenant SaaS platform requires deterministic routing and per-tenant bindings. This ensures requests maintain correct tenant identification and isolation throughout the processing pipeline.

When should I not use a shared database model for tenant isolation in SaaS architecture?

Tenant isolation model limitations depend on your platform choice and scale. If per-tenant bindings and custom-domain workflows require strict data separation, you may need stricter isolation boundaries than a shared database model provides.