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

# Overview

Foundry OSD is a Windows deployment tool: you prepare deployment media on a PC, start a device from it, and Foundry installs Windows on that device through a guided workflow.

<figure><img src="https://64695594-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdn0pr5zia6oG2DU1R1Pn%2Fuploads%2Fgit-blob-11aad54aa8516c9bb29379c25e8bed32d50d30da%2Fshared-overview-01-hero.png?alt=media" alt="Foundry OSD"><figcaption></figcaption></figure>

## Choose your task

| I want to ...                                                                 | Go to                                                                |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| Start from the beginning: requirements, installation, how a deployment works  | [Get started](https://docs.foundryosd.com/start-here.md)             |
| Create my first media and deploy one test device                              | [Quick start](https://docs.foundryosd.com/start-here/quick-start.md) |
| Configure networking, Windows Autopilot, Domain Join or Windows customization | [Foundry OSD](https://docs.foundryosd.com/foundry-osd.md)            |
| Connect a device that has started from the media                              | [Foundry Connect](https://docs.foundryosd.com/foundry-connect.md)    |
| Choose the disk, Windows and drivers, then deploy                             | [Foundry Deploy](https://docs.foundryosd.com/foundry-deploy.md)      |
| Fix a problem                                                                 | [Troubleshooting](https://docs.foundryosd.com/troubleshooting.md)    |
| Look up versions, network endpoints or privacy details                        | [Reference](https://docs.foundryosd.com/reference.md)                |

## How Foundry works

You work with three applications. Only the first one is installed; the other two start on the target device from the deployment media.

| Application     | Runs on                      | Used by       | What it does                                                                      |
| --------------- | ---------------------------- | ------------- | --------------------------------------------------------------------------------- |
| Foundry OSD     | Administrator PC             | Administrator | Holds your deployment settings and creates an ISO, a USB drive or PXE boot files. |
| Foundry Connect | Target device, in Windows PE | Technician    | Checks that the device has network access, with Ethernet or Wi-Fi.                |
| Foundry Deploy  | Target device, in Windows PE | Technician    | Guides the choice of disk, Windows and drivers, then installs Windows.            |

Two components run without input from you: the Windows PE startup, which prepares Windows PE and starts Foundry Connect and Foundry Deploy, and the post-installation step, which finishes the configuration after the device restarts into Windows. [Deployment workflow](https://docs.foundryosd.com/start-here/deployment-workflow.md) shows where each one fits.

{% hint style="warning" %}
Creating a USB drive erases that drive, and deploying Windows erases the disk you select on the target device. Check both selections before you confirm.
{% endhint %}


---

# 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.foundryosd.com/readme.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.
