> For the complete documentation index, see [llms.txt](https://bluebricks.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluebricks.co/docs/orchestration/cloud-graph.md).

# Cloud Graph

The cloud graph gives you a clear, operational view of your infrastructure and the relationships between different resources. It brings discovery, codification, and deployment into a single visual graph, so you can reason about infrastructure before deciding how to change it.

{% hint style="success" %}
**Ask the agent.** Query your cloud graph through natural conversation. See [Agent Overview](/docs/agent/agents-overview.md).
{% endhint %}

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

The cloud graph shows infrastructure across all [collections](/docs/orchestration/collections.md) you configured in Bluebricks.\
While the graph itself shows all managed environments and their states, Discovery allows you to drill in and see all resources provisioned to your cloud, even those that are not managed by code.

## How the cloud graph works

The cloud graph starts with **discovery**.

Bluebricks first reads your cloud as it exists today and shows those resources in the graph. From there, each resource is labelled as either **unmanaged** (visible but not controlled) or **managed** (controlled via Bluebricks through an [environment](/docs/orchestration/environments.md)).

### Graph canvas

The canvas shows the structure of a collection at a glance:

* **Collection nodes**
* **Environment nodes** represent managed environments

### Resource explorer

The resource explorer drawer is where details live. It is the single source of truth for resource data.

What you see depends on what’s selected in the graph:

* If a **collection** is selected, it shows all resources in the collection, managed & unmanaged.
* If a **environment** is selected, it shows the packages and resources managed by that environment.
* If an **artifact** or **resource** selected, it shows details scoped to that node.

Managed resources are clearly labeled, with links back to the environment that owns them. Unmanaged resources remain selectable for codification.

### Codification

Discovery is not just for viewing. Unmanaged resources can be turned into code through the **cloud import agent**.

Once codified, those resources become managed. Their ownership shifts from “cloud-only” to an explicit environment in the graph.

[Learn more about importing and codifying your resources](/docs/agent/codifying-infrastructure.md)

### Notes and limitations

Discovery visibility depends on the permissions configured for the collection. Collections without discovery enabled will show managed resources only.