This page provides an overview of Q-Cloud and the various components.


Q-Cloud allows a user to compose, edit, and deploy cloud infrastructure resources with minimal programming experience. Once a user deploys the desired state, Q-Cloud generates the required code automatically on behalf of the user and uses a third-party software (Pulumi) to initiate the deployment of resources.
Q-Cloud stores various configuration details in its internal database about a stack and the cloud resources that are deployed including properties, connections, state of deployment.
Q-Cloud currently relies on the Pulumi service to store the current state of the cloud infrastructure resources. The state is a set of metadata about the infrastructure so that it can managed appropriately. Each stack (a unit of infrastructure) has its own state, and state is how Q-Cloud and Pulumi know when and how to create, read, delete, or update cloud resources.
Note - Please refer to this link on what is Pulumi service, and state and how it stores the metadata. https://www.pulumi.com/docs/intro/concepts/state/

Logical Components

Q-Cloud consists of the following logical components:
  • Organization
  • Workspace
  • Stack, Stack group and Stack profile
  • Canvas
  • Users, Permissions, and Roles
The following diagram depicts the high-level structure and components of Q-Cloud and their relationships.
Diagram 1 – Q-Cloud components and their relationships
Copy link
On this page
Logical Components