> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/catalog/deployments.md).
# Deployments
Every running instance of a service, by environment, changeset, container version and exposure, and how exposure differs between stages.
A **Deployment** is a running instance of a service in a specific environment — dev, staging, production. The **Deployments** inventory (**Catalog → Deployments**) connects your code, container images, infrastructure and findings into one view: what is running where, which container versions are live, which findings sit on running workloads, and how exposure differs between environments.
Deployments — each running instance with its exact changeset, container tag, environment, and exposure.
{% hint style="info" %}
**Prerequisites:** Deployments are observed from your running environments, so they require a connected cloud provider (CSP) in addition to your source-code (SCM) provider.
{% endhint %}
## The listing
| Column | What it shows |
| ----------------- | ---------------------------------------------------------------------- |
| **Service** | The service the deployment belongs to. |
| **Resource** | The runtime resource it's deployed to. |
| **Changeset** | The exact code changeset running. |
| **Container Tag** | The deployed container image version. |
| **Environment** | The environment boundary (Test, Staging, Production). |
| **Accessibility** | Whether it's internet-accessible (reachable from the public internet). |
| **Findings** | Security findings associated with the deployment. |
Filter by Service, Deployment Type, Environment, and Accessibility, and sort by changeset, environment, or findings. This is how you isolate issues by environment, verify safe promotion between stages, and detect **security drift** across deployments. See [Filtering and Exports](/mrecEO40m5D6bt7Pq5pE/operate/dashboards/filtering-and-exports.md).
## Reading a deployment
For each deployment you can [**view details**](/mrecEO40m5D6bt7Pq5pE/catalog/deployments/deployment-detail.md) (and export them as JSON) and **Export SBOM** — a CycloneDX SBOM of exactly what's running in that instance.
## Related
* [Deployment Detail](/mrecEO40m5D6bt7Pq5pE/catalog/deployments/deployment-detail.md) — the per-deployment view and SBOM.
* [Services → Deployments](/mrecEO40m5D6bt7Pq5pE/catalog/services/service-detail.md) — a service's deployments in context.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/catalog/deployments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
