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

# Compute and outposts

> Run on your systems, Darkmatter compute, or partner infrastructure connected to the same mesh.

## Choose where work runs

* **Your systems.** Run the software on your own compute, embedded devices and physical systems.
* **Darkmatter compute.** Work with our team to provision capacity and handle installation.
* **Partner infrastructure.** Use a supported provider’s GPUs as a pool your outpost serves from, or partner-run outposts enrolled in your mesh.

An installation is an outpost; enrollment admits it to a mesh. Its served models, capabilities and advertised capacity determine what work it can accept. A new outpost runs on its own until an administrator creates a mesh or joins one with an invitation, and outposts share work only within one mesh.

## The console at a glance

After [installing](https://docs.drkm.dev/installation.md) and `drkm start`, the console is at `https://drkm.localhost:3756` and on your local network as `https://<callsign>.local`. Its sidebar is **Chat**, **Schedules**, **Outposts** (the fleet and its jobs), **Overwatch** (the map) and, when a video connection is ready, **Watchdog**; **Settings** opens from your account menu. `⌘K` opens a palette that finds conversations, opens services and sends a message to the agent. A new chat’s **Apps** open a map scan, an overlay import, a Splash plan or Watchdog beside the composer without starting a conversation; each appears only where the outpost runs it.

Each conversation gets its own sandbox, the agent’s computer: a leased machine whose files persist across turns, with `workspace/` as every run’s working directory and no network access. Uploads land under `uploads/`; a thread’s **Files** panel shows them beside the agent’s, and **Activity** shows background runs, jobs and watches with a Stop for each.

```bash Terminal theme={null}
drkm start
drkm models setup
drkm console models
drkm console outposts
```

## Operate the fleet

Use the **Outposts** page to inspect outposts and their work: a fleet map, a panel with **Jobs** and **Outposts** tabs, and an outpost’s detail with its running jobs, hardware and models. Administrators manage which outposts belong to the mesh in **Settings → Mesh**, which people may sign in and with what role in **Settings → Users**, outside services in **Settings → Connections**, served models in **Settings → Models** and releases in **Settings → Updates**.

For scripts, `drkm console outposts` prints the fleet, and after `drkm.connect()` the SDK’s `drkm.outposts()` returns it with each outpost’s `outpost_id`; use those IDs with the placement controls in [routing and placement](https://docs.drkm.dev/routing.md). Continue to [add devices to the mesh](https://docs.drkm.dev/mesh.md).


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