BoolDesk On-Premises Deployment Requirements and Architecture

1. Overview

BoolDesk is deployed as an on-premises solution where the Frontend and Backend components are installed and hosted on the same Windows Server. Client computers communicate directly with the BoolDesk Server over designated TCP ports. PostgreSQL and Redis Cache are required supporting components for application data storage and caching.

---

2. Minimum Server Requirements

Hardware Requirements

Component	Minimum Requirement
CPU	4 Core Processor (64-bit)
Memory (RAM)	16 GB
Storage	500 GB HDD or SSD
Network	1 Gbps Ethernet Adapter
Architecture	x64 (64-bit)

SSD storage is recommended for optimal application and database performance.

---

Operating System Requirements

Component	Requirement
Operating System	Microsoft Windows Server 2022 Standard or Datacenter
Updates	Latest Windows Updates and Security Patches

---

Software Requirements

Component	Requirement
BoolDesk Server	Latest Supported Version
PostgreSQL	Latest Stable Version
Redis Cache	Latest Stable Version
Microsoft .NET Runtime	Latest Supported Version

---

3. Deployment Architecture

Architecture Overview

The BoolDesk deployment consists of:

Client Layer

• Windows Desktop Client

• Web Administration Portal

Application Layer

• BoolDesk Frontend

• BoolDesk Backend

Both Frontend and Backend services are hosted on the same Windows Server.

Data Layer

• PostgreSQL Database

• Redis Cache

• File Storage (Artifacts and Logs)

• Backup Storage (On-Premises)

---

Communication Flow

Windows Desktop Client
        │
        ├── TCP 44310
        ├── TCP 44311
        └── TCP 44313
                │
                ▼
      BoolDesk Server
 (Frontend & Backend)
                │
        ┌───────┴────────┐
        │                │
        ▼                ▼
 PostgreSQL          Redis Cache
 TCP 5432            TCP 6379

Web Administration Portal:

Web Browser
      │
 HTTPS/TCP 443
      │
      ▼
BoolDesk Server

---

4. Network Requirements

The following firewall rules and network ports must be configured.

Client to BoolDesk Server

Source	Destination	Protocol	Port	Purpose
Windows Desktop Client	BoolDesk Server	TCP	44310	Primary BoolDesk Service
Windows Desktop Client	BoolDesk Server	TCP	44311	Agent Communication
Windows Desktop Client	BoolDesk Server	TCP	44313	Real-Time Communication
Web Browser	BoolDesk Server	TCP	443	Web Administration Portal (HTTPS)

---

Server Internal Services

Source	Destination	Protocol	Port	Purpose
BoolDesk Server	PostgreSQL	TCP	5432	Database Communication
BoolDesk Server	Redis Cache	TCP	6379	Cache Communication

---

Firewall Configuration

Ensure the following inbound ports are allowed on the BoolDesk Server:

• TCP 443 (HTTPS)

• TCP 44310

• TCP 44311

• TCP 44313

Ensure the following service ports are available:

• TCP 5432 (PostgreSQL)

• TCP 6379 (Redis Cache)

---

5. Database Requirements

Component	Requirement
Database Engine	PostgreSQL
Version	Latest Stable Release
Port	5432/TCP

Recommendations

• Allocate at least 100 GB for database storage.

• Configure regular database backups.

• Monitor database performance and disk utilization.

---

6. Redis Cache Requirements

Component	Requirement
Cache Engine	Redis Cache
Version	Latest Stable Release
Port	6379/TCP

Redis is used to improve application responsiveness and reduce database load.

---

7. Support Matrix

Component	Supported
Windows Server 2022	Yes
PostgreSQL Latest Stable Version	Yes
Redis Latest Stable Version	Yes
On-Premises Deployment	Yes

---

Summary

BoolDesk is deployed on a Windows Server 2022 environment with a minimum of 16 GB RAM, 4 CPU cores, and 500 GB storage. The Frontend and Backend applications run on the same server and communicate directly with Windows Desktop Clients over TCP ports 44310, 44311, and 44313. PostgreSQL and Redis Cache provide the required database and caching services for the platform.

This format is suitable for a customer deployment guide, installation manual, or software requirements specification (SRS).