> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zerogpu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported Platforms and Downloads

> Every platform ZeroGPU Edge supports, whether it's a downloadable agent or an SDK integration, and where to get it.

ZeroGPU Edge runs on seven platforms. On Windows, macOS and Linux machines you manage, you install a **downloadable agent**. Everywhere else, you build an **SDK integration** into an app you ship.

## Downloadable agent

ZeroGPU Edge is a background service with a small status app. Install it on each machine with your fleet's SDK key. It needs no code, no app and no signed-in user.

**All agent downloads are at [apps.zerogpu.ai/edge](https://apps.zerogpu.ai/edge).** The page offers the right installer for the computer you're on, lists every file with its SHA-256 checksum, and always shows the current release.

| Platform | Supported systems | Installers | Guide |
| - | - | - | - |
| **Windows** | Windows 10 and 11, x64 | `ZeroGPU-Setup.exe` (guided), `ZeroGPU-Edge.msi` (managed) | [Windows](https://docs.zerogpu.ai/edge/agent/windows.md) |
| **macOS** | macOS 14+ on Apple silicon, 13.4+ on Intel | `ZeroGPU.dmg` (guided), `zerogpu-edge.pkg` (MDM) | [macOS](https://docs.zerogpu.ai/edge/agent/macos.md) |
| **Linux** | glibc 2.30+ (Ubuntu 20.04+, Debian 11+, Fedora, RHEL / Rocky 9+); x86\_64 and ARM64 | `.deb`, `.rpm` | [Linux](https://docs.zerogpu.ai/edge/agent/linux.md) |

Versioned files are at `https://apps.zerogpu.ai/edge/releases/<version>/`, with a `SHA256SUMS` file next to them. Installed machines update themselves.

## SDK integrations

ZeroGPU on GitHub: [github.com/zerogpu](https://github.com/zerogpu).

| Platform | Package | Install | Guide |
| - | - | - | - |
| **Android** | [`ai.zerogpu:android-sdk`](https://central.sonatype.com/artifact/ai.zerogpu/android-sdk) | Maven Central | [Android](https://docs.zerogpu.ai/edge/sdk/android.md) |
| **Chrome extensions** | [`@zerogpu/browser-extension-sdk`](https://www.npmjs.com/package/@zerogpu/browser-extension-sdk) | npm, vendored with `npx zerogpu init` | [Chrome Extension](https://docs.zerogpu.ai/edge/sdk/chrome-extension.md) |
| **Websites** | `https://js-sdk.zerogpu.ai/dist/loader.js` | Script tag, or the npm package | [Browser](https://docs.zerogpu.ai/edge/sdk/browser.md) |
| **Telegram Mini Apps** | `https://js-sdk.zerogpu.ai/dist/loader.js` | Script tag | [Telegram](https://docs.zerogpu.ai/edge/sdk/telegram.md) |
| **macOS desktop apps** | [`@zerogpu/worker`](https://www.npmjs.com/package/@zerogpu/worker) | npm, in an Electron utility process | [macOS desktop apps](https://docs.zerogpu.ai/edge/sdk/electron.md) |
| **Server / npm** | [`@zerogpu/worker`](https://www.npmjs.com/package/@zerogpu/worker), [`zerogpu/worker`](https://hub.docker.com/r/zerogpu/worker) | npm or Docker | [Server / npm](https://docs.zerogpu.ai/edge/sdk/server.md) |

> [!NOTE]
>
> Have a Mac or Linux server you just want to connect, not an app to ship? Use the [downloadable agent](#downloadable-agent). The SDKs are for building ZeroGPU into your own software.

## App ID and app name (optional)

Every app you register in the [Edge Operator Portal](https://edge.zerogpu.ai) gets an **app ID** (a UUID). Copy it from the app's row on **My Apps**; IDs are shown once an app is approved. The same ID identifies the app in the [Reporting API](https://docs.zerogpu.ai/edge/reporting-api.md).

The SDKs can send the app ID and your app's name when a device registers, so the inference the device serves is attributed to that app. Both are optional. If a device doesn't send them, ZeroGPU uses the app your SDK key belongs to and that app's name from the portal.

| Platform | App ID (optional) | App name (optional) | Native ID (optional) |
| - | - | - | - |
| [Android](https://docs.zerogpu.ai/edge/sdk/android.md#app-id-and-app-name-optional) (0.5.0+) | `appId` | `appName` | Package name, sent automatically |
| [Chrome Extension](https://docs.zerogpu.ai/edge/sdk/chrome-extension.md#app-id-and-app-name-optional) (0.5.1+) | `appId` | `appName` | Extension ID, sent automatically |
| [Browser](https://docs.zerogpu.ai/edge/sdk/browser.md#app-id-and-app-name-optional) | `appId` or `data-app-id` | `appName` or `data-app-name` | `externalAppId` or `data-external-app-id` |
| [Telegram Mini Apps](https://docs.zerogpu.ai/edge/sdk/telegram.md#app-id-and-app-name-optional) | `data-app-id` | `data-app-name` | Your bot username, as `data-external-app-id` |

## Which key to use

Every platform uses the SDK key (`zgpu-sdk-…`) of an approved app or GPU fleet from the [Edge Operator Portal](https://edge.zerogpu.ai). The agent calls it the *operator key*. It's different from the API key (`zgpu-api-…`) that ZeroGPU [Inference](https://docs.zerogpu.ai/docs/quickstart.md) customers use to call the API.

| You're connecting | Register in the portal as |
| - | - |
| Windows, macOS or Linux machines with the agent | **GPU Fleet** |
| Servers or containers running `@zerogpu/worker` | **GPU Fleet**, device type **Linux / Server** |
| An Android app, Chrome extension, website or Telegram Mini App | **App**, with the matching app types |
| A macOS desktop (Electron) app | **App**, app type **Others** |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.