# Installation overview (admin)

> For administrators: the different ways to run Probe — self-hosted with Docker, Windows-native alongside Trace, and offline — and how to choose.

_Source: E-Sharp (esharp.se) · Probe guide_


*This page is for the administrator.*

Probe runs self-hosted at your site — your design stays on your network. There are a few installation paths; this page helps you choose.

## The paths

- **Self-hosted (Docker)** — runs on an ordinary Docker install (Linux server or Docker Desktop). Pulls ready-made images, no source code or build required. See [self-hosted with Docker](/en/probe/support/self-hosted-with-docker).
- **Windows-native** — for a server already running Trace; Probe uses Trace's PostgreSQL, pgvector and Ollama and installs nothing of its own. See [Probe on Windows](/en/probe/support/probe-on-windows).
- **Offline / air-gapped** — for environments without internet. Some background features are switched off. See [offline](/en/probe/support/offline).

## How to choose

If you already run Trace on Windows, Windows-native is usually simplest. If Probe stands alone on a Linux server, the Docker path fits. If the environment has no internet, the offline package is right.

> To confirm: which of these paths we offer customers externally is an open question (see the plan) — the central, E-Sharp-internal deploy path is not described here.

---

Related: [update and backup](/en/probe/support/update-and-backup) and [security and data handling](/en/probe/security).

*Probe is E-Sharp's design-review engine. It runs at your site — no design leaves your network.*
