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

# Deploy the EDR

Check the deployment rules and supported hardware, then deploy Stoïk MDR (EDR) from Stoïk Protect or by following the guide for your EDR and operating system.

## Prerequisites

* Uninstall any existing antivirus software before deployment. To avoid conflicts between EDR and any existing antivirus software, we recommend uninstalling any antivirus or similar solutions before installation. See [Antivirus and exclusions](/mdr/deploy/antivirus.md).
* Your equipment is supported: see [Supported environments](#supported-environments).

## Basic rules for deployment

* **No restart required**. Neither your servers nor user workstations need to be restarted. EDR deployment is simple and requires no service interruption.
* **Immediate internet connection not required.** Endpoints can be installed offline, but will need to connect to the internet later to fully activate the EDR.
  * If deploying via MDM or GPO, add `ProvNoWait=1` to the install command: `WindowsSensor.exe /install /quiet /norestart CID=<customer_ID> ProvNoWait=1`

## Two ways to deploy

1. **From the Stoïk Protect app (recommended).** Available environments depend on the provider:

   * CrowdStrike: Windows, macOS, Linux, ChromeOS, Virtual environments, and Mobile
   * SentinelOne: Windows, macOS, Linux

   The screenshot below shows the view if your provider is CrowdStrike:

   <figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2F78rjVLESH4LyyVG5pli0%2Fimage.png?alt=media&amp;token=f60eee67-d7f0-481b-8ced-d5cc271bad74" alt=""><figcaption></figcaption></figure>
2. **From the Help Center documentation.** Follow the guide for your EDR and operating system:
   * CrowdStrike: [Windows](/mdr/deploy/crowdstrike/os/windows.md), [macOS](/mdr/deploy/crowdstrike/os/macos.md), [Linux](/mdr/deploy/crowdstrike/os/linux.md), [ChromeOS](/mdr/deploy/crowdstrike/os/chromeos.md), [Virtual environments](/mdr/deploy/crowdstrike/os/virtual-environments.md), or [Mobile devices](/mdr/deploy/crowdstrike/add-on/mobile.md)
   * SentinelOne: [Windows](/mdr/deploy/sentinelone/os/windows.md), [macOS](/mdr/deploy/sentinelone/os/macos.md), or [Linux](/mdr/deploy/sentinelone/os/linux.md)
   * Microsoft Defender: see [Microsoft Defender](/mdr/deploy/microsoft-defender.md).

## Supported environments

Stoïk MDR is designed for **IT workstations and servers only**. It cannot be installed on industrial or embedded hardware. If you are unsure whether your equipment is compatible, contact us at <protect@stoik.io>.

The following hardware **is supported:**

* Standard x86\_64 (Intel / AMD) or server-grade ARM64 workstations and servers
* Windows, macOS, Linux with standard vendor kernels (Debian, Ubuntu, RHEL, etc.)

For detailed system requirements, refer to your vendor's documentation.

The following hardware **is not supported:**

* **OT / IoT devices**: industrial gateways, PLCs, SCADA controllers
* **Embedded systems**: hardware from Compulab, Advantech, Moxa, Wago, Siemens Industrial, etc.
* **Custom or stripped-down kernels**: missing standard modules such as `CONFIG_DMI_SYSFS`
* **Low-resource embedded SoCs**: Cortex-A53, i.MX8, and similar processors with limited RAM / storage


---

# 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.stoik.io/mdr/deploy.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.
