docs: consolidate remote deployment on headless servers

ci/platform-matrix.json

@@ -1,7 +1,7 @@
 {
   "$comment": "SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.\nSPDX-License-Identifier: Apache-2.0\n\nSingle source of truth for NemoClaw launch claims and platform support. Covers platforms, inference providers, supported agents, messaging integrations, and deployment paths. Scripts read this to generate README and docs tables. QA/CI update platform/provider rows; the engineering owner reviews other rows. Docs are derived.",
   "version": "1.1",
-  "updated": "2026-07-17",
+  "updated": "2026-07-21",
 
   "project_status": {
     "stage": "alpha",
@@ -271,7 +271,7 @@
     {
       "name": "Hosted SaaS / managed NemoClaw",
       "status": "unsupported",
-      "notes": "There is no managed offering. Supported deployment paths are Local CLI onboard, Remote GPU with Brev CLI, and Brev web UI."
+      "notes": "There is no managed offering. Supported deployment paths are local CLI onboarding and headless Linux server onboarding."
     },
     {
       "name": "Native provider integrations not in the Providers table",
@@ -325,14 +325,9 @@
       "notes": "Run `$$nemoclaw onboard` on a tested platform with Docker available locally. Primary path."
     },
     {
-      "name": "Remote GPU with Brev CLI",
+      "name": "Headless Linux server",
       "status": "caveated",
-      "notes": "Legacy compatibility wrapper provisions a Brev VM, installs Docker + NVIDIA Container Toolkit, and runs `$$nemoclaw onboard` on that host. Defaults to GCP; override with `NEMOCLAW_BREV_PROVIDER`. The preferred path is the standard installer followed by `$$nemoclaw onboard` after the VM is reachable."
-    },
-    {
-      "name": "Brev web UI",
-      "status": "tested",
-      "notes": "Browser-driven launcher provisions a Brev-managed Linux VM with Docker, the OpenShell runtime, a NemoClaw sandbox running OpenClaw, inference routing, and the OpenClaw dashboard."
+      "notes": "Provision a tested Linux host, connect over SSH, run the standard installer and `$$nemoclaw onboard`, and keep dashboards bound to loopback behind SSH port forwarding. Automatic recovery after a host reboot is not guaranteed; follow the documented manual recovery flow."
     }
   ]
 }

docs/about/overview.mdx

@@ -82,7 +82,7 @@ Use NemoClaw for these use cases.
 | Always-on assistant       | Run a sandboxed agent with controlled network access and operator-approved egress.        |
 | Terminal coding harness   | Run `dcode` inside an OpenShell sandbox with host-owned inference credentials and a managed terminal workflow. |
 | Sandboxed testing         | Test agent behavior in a locked-down environment before granting broader permissions.         |
-| Remote GPU deployment     | Deploy a sandboxed agent to a remote GPU instance for persistent operation.                   |
+| Headless server deployment | Run a sandboxed agent on a remote Linux server through SSH. Refer to [Deploy to a Headless Server](../deployment/deploy-to-headless-server). |
 
 ## Next Steps
 

docs/changelog/2026-07-08.mdx

@@ -34,7 +34,7 @@ NemoClaw v0.0.78 adds opt-in thread-scoped auto-approval and policy-routed repos
   For more information, refer to [Install OpenClaw Plugins](/user-guide/openclaw/manage-sandboxes/install-openclaw-plugins), [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes), and [Extension Taxonomy and SDK Readiness](/user-guide/openclaw/reference/extension-taxonomy-sdk-readiness).
 - Remote dashboard and shutdown flows now provide copyable SSH port-forward hints, recognize a live untracked loopback forward before rolling back onboarding, align the Hermes WebUI with the resolved host dashboard port, and make the deprecated full stop attempt agent-owned host-forward cleanup before safely releasing an unshared, ownership-verified OpenShell gateway port.
   Supervisor-owned Hermes runtime processes remain under sandbox control, and OpenClaw Slack and compact-QR WhatsApp runtime hooks compose safely when both are enabled.
-  For more information, refer to [Deploy to a Remote GPU Host](/user-guide/openclaw/deployment/deploy-to-remote-gpu), [NemoClaw Quickstart with Hermes](/user-guide/hermes/get-started/quickstart), [Choose Messaging Channels](/user-guide/openclaw/manage-sandboxes/messaging-channels/choose-messaging-channels), and [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
+  For more information, refer to [Deploy to a Headless Server](/user-guide/openclaw/deployment/deploy-to-headless-server), [NemoClaw Quickstart with Hermes](/user-guide/hermes/get-started/quickstart), [Choose Messaging Channels](/user-guide/openclaw/manage-sandboxes/messaging-channels/choose-messaging-channels), and [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
 - Starter prompts now bind the local credential form to an authenticated one-shot helper with immutable commit and SHA-256 pins, explicit isolated or account-home execution profiles, denial of ambient process-control variables, and a preview, edit, and confirm flow.
   This keeps credential collection behind verified helper and approved-command boundaries.
   For more information, refer to [NemoClaw Quickstart with OpenClaw](/user-guide/openclaw/get-started/quickstart) and [Use NemoClaw Docs with Your Coding Agents](/user-guide/openclaw/resources/agent-skills).