# Detailed Architecture

This page outlines the entire Kaisar process from the initial connection of the wallet to the utilization of the container service by the end-user. Each step involves specific entities and actions that ensure secure, verified, and efficient deployment and interaction with the container service.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd_dv5iU32sY6dxQtLU7uaGtFZ5ecLNeBDNFjTLWl9gfJNXjnCLqwSalHWKJNr6CDbFP58OH-aKIhIxnbYiGtfFDCVIDpz3XmCiLir2TLku3BFzpKLEEg3RkJp_b6YgnvRBSsT0Ao7mLvcvsmTkHw7UGic?key=UbI8YI3-VF8UhldN54mDkg" alt=""><figcaption></figcaption></figure>

*<mark style="color:blue;">1. Initiating the Deployment</mark>*

1. **Connect to Wallet**

* **Entity Involved:** End-user
* Action: The end-user connects their wallet to the Console Portal to begin the deployment process.

2. Buy New Container

* Entity Involved: End-user
* **Action:** The end-user purchases a new container through the Console Portal.

*<mark style="color:blue;">2. Transaction Handling</mark>*

1. **Issue Transaction**

* **Entities Involved:** Console Portal, Blockchain
* **Action:** The Console Portal issues a transaction to the Blockchain to record the purchase.

2. **Transaction Details**

* **Entities Involved**: Blockchain
* **Action:** The Blockchain records the transaction details, ensuring transaction integrity.

*<mark style="color:blue;">3. Port Exposure and Container Deployment</mark>*

1. **Request to Expose New Ports**

* **Entities Involved:** Console Portal, VPN
* **Action:** The Console Portal sends a request to the VPN to expose new ports for the container.

2. **Request Results**

* **Entities Involved:** VPN
* **Action:** The VPN processes the request and returns the results to the Console Portal.

3. **Deploy New Container**

* **Entities Involved:** Console Portal, Checkers
* **Action:** The Console Portal commands the Checkers to deploy the container.

4. **Deploy Container**

* **Entities Involved:** Checkers, Worker Node
* **Action:** The Checkers send the deployment command to the Worker Node where the container will be deployed.

*<mark style="color:blue;">4. Notification and Service Connection</mark>*

1. **Event Notification**

* **Entities Involved:** End-user
* **Action:** The end-user is notified of the deployment event.

2. **Container Deployment Confirmation**

* **Entities Involved:** End-user
* **Action:** The end-user receives confirmation of the container deployment.

3. **Connect to Container Service**

* **Entities Involved:** End-user
* **Action:** The end-user connects to the newly deployed container service.

*<mark style="color:blue;">5. Service Utilization</mark>*

1. **Request to Container Service**

* **Entities Involved:** End-user
* **Action:** The end-user makes requests to the container service.

2. **Request Result**

* **Entities Involved:** Container Service
* **Action:** The container service processes the requests and returns the results to the end-user.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kaisar.io/kaisar-network/kaisar-architecture/detailed-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.