# GPU Remit, Read-Only Access, and User Control

**Date**: 2026-02-27 | **Status**: Draft | **SSOT**: GitHub

## 1. GPU remit (local LLMs not dedicated to LLMHosts)

- Same local LLMs/GPUs are **not** dedicated to LLMHosts. User can use them for other productions.
- **Option A:** Route traffic through LLMHosts.com (orchestrate, track, add value).
- **Option B:** **Local-only path** — proxy on host only; no tunnel, no device registration; traffic never leaves the machine.
- LLMHosts **only manages what the user explicitly grants**. We never assume we own the GPU or process.

## 2. Existing stacks (vLLM, etc.) — read-only access

- User may have existing inference (vLLM, Ollama, LM Studio, etc.). LLMHosts may **discover and use** them but must **never change** them (no install/upgrade/reconfig of user's stack).
- Discovery = **read-only** (probe endpoints only; no write). Onboarding: "discover and use," not "we set up your vLLM."

## 3. User in control; value from real data

- Platform can **offer** to manage; user decides. No automatic takeover without opt-in.
- Show value (savings, utilization) from **real data and that customer's usage** — never speculation.
- Suggestions (e.g. "let LLMHosts manage this GPU") are opt-in; no automatic remit changes.

## 4. Per-GPU / per-instance opt-in

- User can define: "This GPU/instance is off-limits; that one you can use."
- We need a **remit model**: in-remit vs off-limits (per device, backend, or instance). Discovery and routing only use in-remit backends.

## 5. Alignment with our codebase

- **Discovery** (`llmhosts/discovery/`): Already read-only. Extend to respect remit allowlist.
- **Dispatcher**: Only register/use backends in remit.
- **Config**: Remit/allowlist (e.g. by backend URL, device id); local-only flag.
- **Onboarding**: Copy and flows = "discover and use," "you're in control," "value from your data."

## 6. OpenClaw — our stance

**We build our own solution.** OpenClaw (openclaw/openclaw, openclaw-community/openclaw-hub) is **optional leverage**: we may reuse specific code or patterns **only where they fill gaps** and match our objectives. We do **not** replicate OpenClaw. Where we've already solved something in a masterclass way (e.g. three-tier router, discovery, dispatcher, vCache), we keep and improve that. Adopt from OpenClaw only when it clearly serves GPU remit, user control, read-only access, and production-ready E2E.
