diff --git a/docs/architecture.md b/docs/architecture.md
new file mode 100644
index 0000000..d004c7b
--- /dev/null
+++ b/docs/architecture.md
@@ -0,0 +1,146 @@
+# Project Architecture
+
+This document provides an in-depth explanation of the system's architecture, its design choices, and its components. It serves as a guide for contributors and developers to understand how the project is structured and operates.
+
+---
+
+## Overview
+
+The project follows a <mark>[specific design pattern, e.g., Model-View-Controller (MVC) or Microservices Architecture]</mark> to ensure scalability, maintainability, and clarity. Each module or component has a distinct responsibility, and they work together to deliver the functionality of the application.
+
+---
+
+## Directory Structure
+
+The core of the project is organized as follows:
+
+```plaintext
+src/
+├── models/
+├── views/
+├── controllers/
+├── services/
+├── utils/
+```
+
+---
+
+### Breakdown
+- **`models/`**  
+  Manages interactions with the database or data sources, including ORM models or raw SQL queries.
+
+- **`views/`**  
+  Renders data for users, including HTML templates, API responses (JSON), or CLI outputs.
+
+- **`controllers/`**  
+  Implements the main logic, including routing, input validation, and coordinating between models and views.
+
+- **`services/`**  
+  Handles external dependencies like API calls, third-party integrations, and background tasks.
+
+- **`utils/`**  
+  A collection of helper functions to keep repetitive or shared logic clean and centralized.
+
+---
+
+## Workflow and Data Flow
+
+1. **Frontend Interaction**:  
+   Users interact with the frontend (web UI, CLI, or app) to send a request.
+
+2. **API Endpoint**:  
+   The request hits a RESTful API endpoint that validates and routes it.
+
+3. **Controller**:  
+   The controller processes the request, performs logic, and delegates to models or services.
+
+4. **Model**:  
+   Retrieves or manipulates data from the database.
+
+5. **View**:  
+   Formats the response for the user (JSON, rendered HTML, or text).
+
+---
+
+## Design Principles
+
+### 1. **Separation of Concerns**
+Each layer (models, views, controllers) has a specific and distinct responsibility to make the system easier to develop, test, and maintain.
+
+### 2. **Scalability**
+The system is modular to accommodate future growth, whether by adding new features, handling more users, or supporting additional integrations.
+
+### 3. **DRY (Don’t Repeat Yourself)**
+Reusable functions and utilities prevent code duplication.
+
+---
+
+## Key Components
+
+### **1. API Layer**
+- Exposes RESTful endpoints using [framework name, e.g., FastAPI, Flask, or Django].
+- Implements input validation and error handling.
+- Supports authentication using OAuth 2.0 or JWT.
+
+### **2. Database Layer**
+- Uses [database type, e.g., PostgreSQL, MongoDB, or MySQL] for persistence.
+- Follows normalization practices to ensure consistency.
+- Supports caching with [Redis or Memcached] for performance optimization.
+
+### **3. Business Logic Layer**
+- Handles complex operations like data transformations, aggregations, or algorithm execution.
+
+### **4. External Integrations**
+- Communicates with third-party services via APIs for tasks like:
+  - Payment processing.
+  - Notification systems.
+  - Analytics tracking.
+
+---
+
+## Security Features
+
+- **Authentication**: OAuth 2.0, JWT tokens, or API keys.  
+- **Data Encryption**: Sensitive data is encrypted at rest and in transit.  
+- **Input Validation**: Prevents injection attacks and invalid data entries.  
+
+---
+
+## Scalability Strategies
+
+- **Horizontal Scaling**: Additional API instances can be deployed.  
+- **Database Indexing**: Ensures fast queries on frequently accessed data.  
+- **Load Balancing**: Distributes traffic evenly across servers.
+
+---
+
+## Tools and Frameworks
+
+### Backend
+- Programming Language: Python  
+- Web Framework: Flask / FastAPI / Django  
+
+### Database
+- PostgreSQL  
+- Redis (for caching)  
+
+### Testing
+- Pytest (unit and integration tests).  
+
+---
+
+## System Diagram
+
+Below is a simplified high-level system diagram:
+
+```plaintext
+User
+ ↓
+Frontend (UI)
+ ↓
+Backend (API Layer)
+ ↓
+Database ↔ Caching Layer
+```
+
+A more detailed one can be found by running [this](docs/diagrams/system-design.bat) or opening [this](icons/system-design.png)