System Architecture

Auto-generated by IssAssist Documentation Bootstrap · 2026-06-25 Review this page and remove [TODO: verify] markers as you verify each detail.

---

IssAssist System Architecture

IssAssist is a comprehensive backup management and monitoring platform built by IssTech. This document provides an overview of the system's components, their interactions, and deployment modes.

Components

The following components make up the IssAssist system:

• issassist-api: Python 3.12 / FastAPI backend (port 8000), PostgreSQL database
• issassist-webgui: TypeScript / Svelte 5 / SvelteKit frontend (port 80)
• issassist-tsm-agent: Python 3.12 bridge to IBM Storage Protect via dsmadmc CLI
• issassist-utils: shared Python library (Pydantic models, async HTTP helpers, logging)
• AI Agents:
  • pm-agent
  • architect
  • developer
  • security
  • tester
  • docs

ASCII Diagram of Component Interactions

          +---------------+
          |  IBM Storage  |
          |  Protect (dsm) |
          +---------------+
                  |
                  |
                  v
          +---------------+
          |  issassist-  |
          |  tsm-agent    |
          +---------------+
                  |
                  |
                  v
          +---------------+       +---------------+
          |  issassist-api |       |  issassist-web  |
          |  (PostgreSQL) |       |  gui (Svelte)   |
          +---------------+       +---------------+
                  |
                  |
                  v
          +---------------+       +---------------+       +---------------+
          |  pm-agent     |       |  architect    |       |  developer    |
          |  (GitHub      |       |  (Architect   |       |  (Developer)  |
          |  Projects v2)|       |  column)       |       |  (Security)  |
          +---------------+       +---------------+       +---------------+
                  |
                  |
                  v
          +---------------+       +---------------+       +---------------+
          |  security    |       |  tester       |       |  docs        |
          |  (Security   |       |  (Tester)     |       |  (Documentation)|
          |  column)      |       |               |       |               |
          +---------------+       +---------------+       +---------------+
                  |
                  |
                  v
          +---------------+       +---------------+
          |  docs        |       |  release      |
          |  (Documentation)|       |  (Release)    |
          +---------------+       +---------------+
                  |
                  |
                  v
          +---------------+
          |  Kubernetes  |
          +---------------+

Data Flow

A backup alert travels through the following data flow:

1. IBM Storage Protect (dsm) → issassist-tsm-agent via dsmadmc CLI
2. issassist-tsm-agent → issassist-api via HTTP request
3. issassist-api → issassist-webgui via API request
4. issassist-webgui → User

Database Schema Overview

The PostgreSQL database contains the following tables:

• users
• nodes
• alerts
• restore_groups
• ...

Authentication Flow

The authentication flow involves the following steps:

1. User requests access to IssAssist
2. IssAssist checks user credentials (JWT tokens)
3. If valid, tokens are validated and stored in the session cookie
4. User can now interact with the system

AI Agent Pipeline

The AI agent pipeline involves the following stages:

1. Mission → pm-agent
2. pm-agent → architect
3. architect → developer
4. developer → security
5. security → tester
6. tester → docs
7. docs → release

Deployment Modes

IssAssist can be deployed in the following modes:

1. Docker Compose (dev/test): Quick development and testing environments
2. Kubernetes/Helm (production): Scalable and secure production environment

Network Topology

The following services need to reach each other on the network:

• issassist-api → pm-agent, architect, developer
• issassist-webgui → pm-agent, architect, developer
• issassist-tsm-agent → pm-agent, architect, developer
• docs → release

Note: The above documentation is based on the provided source code and may not cover all aspects of the system.