> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/developer-machines/installation-script/mdm-deployment.md).

# MDM Deployment

Dev Machine Guard is designed to be deployed at scale through your existing endpoint management tooling. This section covers fleet deployment patterns for each supported operating system.

For an overview of the underlying delivery model (loader script versus signed installer), see the [Installation Script](/developer-machines/installation-script.md) page.

#### Choose your platform

* [**Windows**](/developer-machines/installation-script/mdm-deployment/windows.md) — Microsoft Configuration Manager (SCCM/MEMCM), Microsoft Intune
* [**macOS**](/developer-machines/installation-script/mdm-deployment/macos.md) — Iru (formerly Kandji)

#### Picking a deployment pattern

Two distinct delivery models are available, depending on what your fleet already supports:

| Model                                    | When to use it                                                                                                                                                                                                      |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Signed installer (MSI, PKG, DEB/RPM)** | Your MDM treats applications as first-class objects with built-in detection, version tracking, and supersedence (e.g., SCCM Applications, Intune Win32 apps, Jamf Pro policies). Recommended for production fleets. |
| **Loader script (PowerShell, shell)**    | Your tooling pushes scripts but does not natively manage application lifecycle (e.g., custom EDR runbooks, lightweight MDMs, ad-hoc rollouts). Simpler to deploy; updates flow automatically through the loader.    |

Each platform page below shows which deployment tools are supported and links to a step-by-step guide for each one.


---

# 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.stepsecurity.io/developer-machines/installation-script/mdm-deployment.md?ask=<question>&goal=<endgoal>
```

`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.