> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/unigetui/guides/understand/how-it-works.md).

# How UniGetUI works

UniGetUI doesn't host any software. It's a single interface for the package managers on your computer, which download apps from their publishers.

UniGetUI doesn't contain or host any apps. It's a **window onto the package managers** already used by millions of people, such as WinGet on Windows, Homebrew on macOS or APT on Linux. Understanding this one idea explains almost everything else: where apps come from, why some aren't listed, and what to check when something fails.

## Three layers

<table><thead><tr><th width="200">LAYER</th><th>WHAT IT DOES</th><th>EXAMPLES</th></tr></thead><tbody><tr><td><strong>UniGetUI</strong></td><td>Shows everything in one place and sends your requests (install, update, remove) to the right package manager.</td><td>The app you're using.</td></tr><tr><td><strong>Package managers</strong></td><td>Command-line tools that know which apps exist, which version is installed, and how to install or update them.</td><td>WinGet, Scoop, Chocolatey, Homebrew, APT, Flatpak, npm, pip…</td></tr><tr><td><strong>Publishers</strong></td><td>The companies and developers who make the apps. In most cases, the installer is downloaded from their own servers.</td><td>Google, Mozilla, VideoLAN…</td></tr></tbody></table>

## What this means for you

**You get the real installer.** When you install Firefox through UniGetUI with WinGet, the installer comes from Mozilla, just as if you had downloaded it from their website. UniGetUI doesn't repackage it.

**UniGetUI sees apps you didn't install through it.** Package managers can recognize software already on your computer, so UniGetUI can offer updates for apps you installed months ago from a website.

**If no package manager knows an app, UniGetUI can't update it.** Some drivers, hardware utilities and Microsoft Store apps fall in this category. See [What UniGetUI doesn't do](/unigetui/guides/understand/limits.md).

**When something fails, the package manager usually has the answer.** UniGetUI shows the package manager's output for every operation. That's the first thing to look at, and the first thing support will ask for. See [An update or installation fails](/unigetui/help/troubleshooting/update-or-install-fails.md).

**Trust depends on the source.** Package managers like WinGet review what's added to their catalogs, but they don't write the software. Before installing something unfamiliar, check its publisher and source in the package details. See [Where packages come from and what to trust](/unigetui/guides/understand/trust-and-security.md).

## Which package managers can I use?

UniGetUI turns on the package managers that exist for your system.

{% tabs %}
{% tab title="Windows" %}
WinGet, Scoop, Chocolatey, Windows PowerShell, PowerShell 7, npm, Bun, pip, Cargo, .NET Tool and vcpkg.

If WinGet is missing or broken, UniGetUI falls back to Pinget, a built-in implementation of WinGet, so you can keep working.
{% endtab %}

{% tab title="macOS" %}
Homebrew, PowerShell 7, npm, Bun, pip, Cargo, .NET Tool and vcpkg.
{% endtab %}

{% tab title="Linux" %}
APT, DNF, Pacman, Snap or Flatpak depending on your distribution, plus Homebrew, PowerShell 7, npm, Bun, pip, Cargo, .NET Tool and vcpkg.
{% endtab %}
{% endtabs %}

You don't need all of them. Most people only use WinGet on Windows, Homebrew on macOS, or their distribution's manager on Linux. Developers often add npm, pip or Cargo.

Details and requirements for each one are in [Supported package managers](/unigetui/reference/package-managers.md).


---

# 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.devolutions.net/unigetui/guides/understand/how-it-works.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.