# Architecture

The QMCLOUD software is made up of multiple docker containers and besides the SaaS platform, it can be installed in a customer’s environment including public cloud or private cloud. 

{% hint style="info" %}
The following architecture is relevant for self-hosting and AWS marketplace appliance options only. The SaaS version of QMCLOUD uses a similar architecture but varies significantly to account for multi- tenancy and RBAC.
{% endhint %}

The following diagram depicts the architecture of QMCLOUD.

Diagram – QMCLOUD architecture

<figure><img src="/files/ELRMkVbDvpnM6jh3iJlp" alt=""><figcaption></figcaption></figure>

The following components are depicted in the diagram:

1. User workstation
2. URL / FQDN used to access QMCLOUD
3. Set of docker containers that constitutes QMCLOUD Sofware
4. Proxy or Load balancer
5. Backend – NodeJS, and Java
6. Front end - ReactJS
7. Postgres database
8. Pulumi Automation API
9. Pulumi state software using app.pulumi.com
10. Azure cloud platform
11. AWS cloud platform


---

# 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.qmcloud.io/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.