Skip to main content

Curated, evidence-linked composition

Self-hosted channel agent

Reference architecture for a user-controlled OpenClaw gateway and one messaging channel.

OpenClaw

Intended use case

Personal or single-organization messaging assistant deployments.

Data flow

This is the intended logical flow. Actual data access depends on each component configuration and permission boundary.

  1. 1Authorized channel → self-hosted gateway
  2. 2Gateway → configured model/tools
  3. 3Agent response → authorized channel

Linked capability trust cards

Open every component before copying configuration. A stack is only as safe as its broadest permission and weakest trust boundary.

Alternatives