Architecture overview
This page is reference material. Start with Quick Start when the goal is to deploy a device.
Components
| Component | Runs where | Role |
|---|---|---|
| Foundry OSD | Admin workstation | Checks prerequisites, builds media, and provisions Foundry Connect |
| Foundry Connect | WinPE target device | Validates network readiness before deployment continues |
| Foundry Deploy | WinPE target device | Loads catalogs, collects deployment choices, and executes deployment |
| catalog | Separate automation repository | Generates XML feeds for operating system, driver pack, and WinPE metadata |
Runtime sequence
- Foundry OSD prepares ISO or USB media and provisions Foundry Connect for the selected architecture.
- The target device boots WinPE.
- Bootstrap launches Foundry Connect.
- Foundry Connect validates network readiness.
- Bootstrap resolves Foundry Deploy from release assets or an available USB cache.
- Bootstrap opens Foundry Deploy, which loads catalogs and runs the deployment workflow.
Why the split exists
- Media authoring belongs on the admin workstation.
- Network readiness is validated before deployment starts.
- Deployment choices happen on the target device.
- Catalog data is produced independently and consumed by the runtime.
Next step
Open Product Boundaries for a responsibility breakdown.