> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/deployment.md).

# Deployment

In this section you can find information to assist with the deployment and management of your StrongDM organization.

* [Quick Start Guide](/admin/deployment/quickstart.md) - The Admin quick start is a good place to start if you want a quick look at setting up StrongDM end to end in a test scenario - a user with a role, a gateway, and a resource, with a test of proxied access.
* [Terraform](/admin/deployment/terraform.md) - The Terraform quick starts provide a similar starting point for investigating deployments using the [StrongDM Terraform Provider](https://registry.terraform.io/providers/strongdm/sdm/latest/docs).
* [Deployment Scenarios](/admin/deployment/scenarios.md) - Here, you will find a variety of specific examples of deployment scenarios, such as self-registering relays, gateways deployed with specific technologies, temporary access granted with chat bots or PagerDuty schedules, and other use case examples with guides.
* [Integrations](/admin/deployment/integrations.md) - The integrations page contains an overview of the integrations that StrongDM provides, and links out to guides for setting up those integrations.
* [Environment Variables](/admin/deployment/environment-variables.md) - The environment variables page is a handy guide containing information about the environment variables that may need to be set up where you run StrongDM software, such as on clients, gateways, relays, or proxy clusters.
* [Parent/Child Organizations](/admin/deployment/parent-child.md) - For some complex deployments, the "Parent/Child" organization structure may make sense. Learn more about it here.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.strongdm.com/admin/deployment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.