---
title: "Depot"
description: "Depot is the server you run. It holds your endpoints, your policies and your data, and it is the console you work in."
url: "https://support.outpostplatform.com/depot/"
product: "depot"
type: "concept"
status: "stub"
ai_summary: "Overview of Depot, the per organisation Outpost server. Runs the console, terminates agent connections, stores inventory, policies and tickets, and operates in one of four licensed modes. Multi-tenant for providers, with a control database and one database per client."
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/depot/index.md"
license: "CC BY 4.0"
---

# Depot

Depot is the part of Outpost you run and own. Endpoints connect to it, the
console is served by it, and your inventory, policies, scripts, tickets and
documents live in its databases rather than in anybody else's. This section is
for whoever installs, configures and operates that server.

<!-- TODO: write this page against the concept template.

Sections:

- What Depot does, in one paragraph, for somebody who has not installed it.
- The console, and who signs in to it.
- The agent connection, and why it is separate from the console.
- The database layout: one control database, one per client.
- Multi-tenancy: how a provider serves many clients from one Depot.
- The four operating modes, in one line each, linked to the modes page.
- What Depot sends to the Outpost service, and what it never sends.
- Sizing and where Depot runs.
-->

Follow the [concept template](https://gitlab.com/outpostplatform/docs/-/blob/main/templates/concept.md).