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

# Security model

> The trust boundaries behind HQ's self-hosted architecture.

HQ is self-hosted admin software with tenant-scoped row-level security on every table. Self-hosted installs use a single default tenant, so all authenticated users share the workspace — treat anyone with a Supabase account as a full admin. [HQ hosted](/hosted/getting-started) manages these trust boundaries for you — each workspace gets a dedicated database and isolated runtime.

## Trust boundaries

<CardGroup cols={2}>
  <Card title="Supabase project" icon="database">
    Stores all shared state. The service role key grants full database access — treat it like a database admin password.
  </Card>

  <Card title="Docker host" icon="server">
    The gateway container runs agents with full access to the shared volume, Chrome, and the service role key.
  </Card>

  <Card title="Runner Docker socket" icon="shield-halved">
    The runner mounts `/var/run/docker.sock` — root-equivalent access to the host. Any RCE in the runner owns the host.
  </Card>

  <Card title="noVNC endpoint" icon="desktop">
    Remote desktop into the gateway container. Protected by VNC password, but do not expose directly to the public internet.
  </Card>
</CardGroup>

<Warning>
  Use Tailscale or another private access layer for remote use. Do not expose noVNC or the files API directly to the public internet without a reverse proxy and auth layer.
</Warning>

Read the full [security policy](/security/security-policy) for detailed threat analysis, responsible disclosure, and hardening guidance.