# Kaisar Cloud ( End-User ) Workflow

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfnOVUQikoVrlfwi2YPt-x37EO_EGqKLJnRZ5_Z-9vEc-CRvgtkAa4PwQSIqHtfuUnHCW38xsL2FE883jajf8OILj-uC9OHxFBohU2MBnPCHBFT9W4EMmH4br94EHSzeIQTTHt9mD8Dvw_iu7Plg88Xcwi2?key=UbI8YI3-VF8UhldN54mDkg" alt=""><figcaption></figcaption></figure>

1. End Users initiates the process by connecting their wallet to the Console Portal of Kaisar to pay for GPU resources.
2. After connecting the wallet, the end-user buys a new container through the Console Portal.
3. The Console Portal issues a transaction that involves multiple Kaisar components like VPN and Blockchain.
4. The VPN processes the transaction details and communicates with the Blockchain.
5. The Blockchain component handles the request to expose new ports to the Proxy/Gateway for accessing the container services.&#x20;
6. The Kaisar Checkers is responsible for deploying the new container. It sends the deployment request to the Provider's Worker Node.
7. The Worker Node in the Provider's infrastructure deploys the container.An event is triggered once the container is deployed, which is communicated back through the Checkers component.
8. The Console Portal updates the end-user with the status: "Container is deploying..." and eventually, "Your Container has been deployed successfully.".
9. Finally the GPU resources are available as Container services by the Providers

* Types of Container Services:&#x20;

&#x20;       \-  Worker Node (Container): Hardware: CPU, RAM, GPU, storage.( By Q2 2024 )

&#x20;       \-  Worker Cluster: Comprises multiple Worker Nodes to allows pooling of resources from multiple  nodes.(Available by Q4 2024)

&#x20;        \-  End users rent resources from mobile nodes provided by Providers.(Available by Q3 2025)


---

# 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/core-workflows/kaisar-cloud-end-user-workflow.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.