---
title: "Remote Outpost"
description: "Remote Outpost is the air gapped edition. It manages endpoints on a network that never reaches the internet."
url: "https://support.outpostplatform.com/remote-outpost/"
product: "remote-outpost"
type: "concept"
status: "stub"
ai_summary: "Overview of Remote Outpost, the air gapped edition of the platform. Runs entirely inside an isolated network with no connection to Outpost, is licensed annually rather than metered, and takes updates, licences and content through a deliberate offline transfer."
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/remote-outpost/index.md"
license: "CC BY 4.0"
---

# Remote Outpost

Remote Outpost is what you install when the network you manage cannot reach the
internet at all: a secure facility, a ship, an isolated production line. It runs
the same platform with the connection to Outpost deliberately absent, which
changes
licensing, updates and support. This section is for the administrator of an air
gapped site.

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

Sections:

- What Remote Outpost is, and the situations it exists for.
- What differs from a connected deployment, as a table.
- Licensing: annual rather than metered, and how the licence gets in.
- Updates: how a new version crosses the gap, and how it is verified.
- What is unavailable, stated plainly, so nobody plans around it.
- Getting support without a connection: what to collect and how to send it.
- Compliance evidence from an isolated site.
- Moving from a connected deployment to an isolated one, and back.
-->

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