Operator docs

Security Model

Ship a self-hosted OpenClaw stack you can trust — reproducible installs, controlled upgrades, and clear recovery paths from the start.

Why this exists

Self-hosting OpenClaw should feel like shipping, not firefighting. This package gives you a stable baseline so setup, maintenance, and recovery follow a known path — and you can focus on what your agents actually do.

Principles

  • +Artifact verification before execution
  • +Private-by-default deployment posture
  • +Minimal host-side lifecycle tooling to reduce drift
  • +Explicit update and rollback procedures before incidents

Limitations

  • !Outbound requests may occur depending on configuration.
  • !The baseline does not guarantee isolation across tenants.
  • !Infrastructure security remains the operator's responsibility.

What this baseline is not

the official OpenClaw projecta hosted SaaS servicemanaged infrastructurea hardened multi-tenant isolation platform

Operational Baseline

  • +Artifact verification and release integrity questions
  • +Supported baseline setup assistance
  • +Issues reproducible on the shipped baseline

Support boundaries

  • !Support is scoped to the shipped baseline and documented operator flow.
  • !Custom infrastructure hardening, platform engineering, and drift outside the baseline remain operator responsibilities.
  • !Future upgrade planning is handled directly through support contact.

Verify the artifact before first run.

Review the checksum workflow before you extract, run, or promote the bundle into your environment.

Verify your download