archifyiOpen the studio

Curated example · Editable connections

SaaS architecture
you can explore.

Trace a tenant-aware web request through an API, access checks, and data stores.

Curated example

Follow the connections.

Select a component to explore
Browser

Sends a request. Treat everything arriving from the browser as untrusted input.

Make it your own

Browser -> API Gateway -> Application API -> Tenant Context Check -> PostgreSQL
API Gateway -> Auth Service
Application API -> Redis Cache
Application API -> Background Worker
Download connections

Checking workspace availability. You can explore and copy this example now.

Read the tenant-aware request path

Follow Browser → API Gateway → Application API → Tenant Context Check → PostgreSQL. Identity answers who signed in; authorization decides which workspace and records that identity may use. These arrows show intended dependencies, not a recording of production traffic.

Choose a data-isolation model

For a multi-tenant SaaS architecture, decide whether tenant records share a schema, use separate schemas, or live in separate databases. Show where tenant scope is established and checked, and where database policies add defense in depth. A tenant ID column by itself is not an isolation strategy.

Carry tenant scope across services

Use tenant-aware cache keys, pass the intended workspace into asynchronous jobs, and check access again when a worker reads data. Remove the gateway if your browser calls the application directly; add a queue if jobs pass through one. This curated software architecture diagram helps review a design but does not prove security or deployment correctness.