Multi-tenant data isolation architecture diagram
Prompt
Create a clean technical diagram illustrating three approaches to multi-tenant data isolation for a [saas_type] SaaS platform serving [tenant_count] tenants.
The diagram should show three horizontal bands stacked vertically, each depicting a different isolation model:
1. Shared database, shared schema (tenant_id column) — cheapest, least isolated
2. Shared database, schema-per-tenant — middle ground
3. Database-per-tenant — strongest isolation, most expensive
Use a [color_scheme] palette. Each band should include: tenant icons on the left, an application layer in the middle, and the database layout on the right with clear visual indicators of isolation boundaries.Customise this prompt
Fill in 3 variables to personalise this prompt
Example output
A polished technical architecture diagram titled "Multi-Tenant Data Isolation Models" showing three stacked horizontal bands against a clean off-white background, separated by thin horizontal dividers. Each band represents one isolation strategy for a B2B SaaS platform serving 500 tenants. **Top band — Shared Database, Shared Schema:** On the left, a column of five small rounded-rectangle tenant icons in different muted colors (indigo, teal, amber, rose, slate), each labeled "Tenant A" through "Tenant E". Arrows from all tenants converge into a single application server icon in the center (a labeled rounded rectangle reading "App Server / tenant_id middleware"). From the app server, a single arrow points to the right toward one cylindrical database icon labeled "PostgreSQL — public schema". Inside the database cylinder, a small inset table graphic shows columns "tenant_id, user_id, email" with rows in different tenant colors mixed together, visually conveying that all tenant rows coexist. A caption below reads: "cheapest per tenant, weakest isolation, noisy-neighbor risk". **Middle band — Shared Database, Schema per Tenant:** The same five tenant icons on the left. Arrows converge on an app server in the center labeled "App Server / SET search_path". On the right, a single larger database cylinder labeled "PostgreSQL", but inside it five small stacked schema blocks each labeled "schema_a", "schema_b", "schema_c", etc., each in its tenant color. Caption: "balanced isolation, moderate operational cost, limited by max schema count". **Bottom band — Database per Tenant:** The same five tenant icons on the left. Arrows go through an app server labeled "App Server / connection router" in the center. On the right, five separate database cylinders side by side, each in its tenant color and labeled "db_tenant_a" through "db_tenant_e", each with its own subtle lock icon indicating isolation. Caption: "strongest isolation, highest cost, per-tenant backup and compliance". Visual treatment: each band has a faint background wash (pale indigo, pale teal, pale amber) to separate the three strategies. Arrows use rounded right-angle paths in charcoal. A legend in the lower-right corner explains arrow styles (solid = SQL traffic, dotted = auth lookup) and the three isolation strategies. Typography is a clean modern sans-serif like Inter, with band titles in 18pt medium weight and captions in 11pt regular gray. The overall aesthetic is professional engineering documentation, suitable for an architecture review deck — crisp vector lines, no gradients, no skeuomorphism.