Reza Salmanian

Command Palette

Search for a command to run...

Architecture Gallery

System design, at a conceptual level

These diagrams communicate the shape of the systems I build — how requests, data, and permissions flow — without revealing proprietary implementation.

Enterprise SaaS Architecture

The shared shape behind CBSai and its modules: a governed core wrapping independently deployable business domains.

  1. 1

    Client (web)

  2. 2

    API gateway

  3. 3

    Module services (Finance, CRM, HR, ...)

  4. 4

    Shared data layer

Multi-Tenant Architecture

Tenant isolation enforced at the data-access layer so no application-level bug can leak one customer's data into another's.

  1. 1

    Tenant resolver

  2. 2

    Scoped data access layer

  3. 3

    Per-tenant storage boundary

Authentication Flow

Session issuance, token refresh, and identity propagation across services in a multi-tenant system.

  1. 1

    Login / identity provider

  2. 2

    Session issuance

  3. 3

    Token verification per request

Role-Based Permissions

A single permissions model shared by every module and by the AI layer, so access is defined once per tenant.

  1. 1

    Roles & policies

  2. 2

    Permission check middleware

  3. 3

    Module & AI access enforcement

AI Orchestration

Cross-module AI reasoning implemented as orchestration over governed APIs, inheriting existing permission boundaries.

  1. 1

    User query

  2. 2

    Reasoning/orchestration layer

  3. 3

    Governed module APIs

  4. 4

    Grounded response

Voice AI Pipeline

Real-time voice transport decoupled from the reasoning engine so the same intelligence serves chat, voice, and automated briefings.

  1. 1

    Real-time voice transport

  2. 2

    Speech-to-intent

  3. 3

    Reasoning engine

  4. 4

    Voice response

REST API Architecture

Consistent resource modeling, versioning, and permission enforcement across services.

  1. 1

    Resource routes

  2. 2

    Validation & auth middleware

  3. 3

    Service layer

  4. 4

    Data layer

Database Relationships

High-level entity relationships showing tenancy boundaries and shared reference data across modules.

  1. 1

    Tenant

  2. 2

    Core entities (user, account)

  3. 3

    Module-owned entities

Cloud Deployment

Independent scaling per module on cloud-native infrastructure, with CI/CD from commit to production.

  1. 1

    CI/CD pipeline

  2. 2

    Cloud Functions / services

  3. 3

    Cloud storage

  4. 4

    Monitoring & scaling