Choose how to connect devices
Every method starts with your private WinGet source. The agent and Intune add to it.
| Method | Plan | Agent | What you get |
|---|---|---|---|
| winget and a source key | All | No | Devices install approved versions with winget. |
| Agent, Inventory mode | Business | Yes | Installed software per device, matched to your catalog. The epw command line in read-only mode. |
| Agent, Managed mode | Premium | Yes | The agent keeps catalog packages on the approved version, with rings and two-person approval. In preview. |
| Intune | Business for the agent, Premium for the kit | Yes | Deploy the agent and baselines as Win32 apps. Remediations and custom compliance. |
Which one should I use?
Section titled “Which one should I use?”- Start with winget and a source key. It works on every plan and needs nothing installed.
- Add the agent when you need to know which devices run which version.
- Use Intune to deliver the source command and the agent if you already manage devices with it.
Requirements
Section titled “Requirements”| Item | Requirement |
|---|---|
| Windows | Windows 10 or 11 with winget (App Installer). Windows Server 2025 works with winget. |
| Network | Devices reach the EndpointWorks API host over HTTPS (443). Community installers download from the vendor URLs in their manifests. |
| Agent | x64 or arm64. Windows 10 22H2 or later for the Intune baseline apps. |