Personal Site
A private deployment for household support, fitness planning and personal correspondence.
- Family & Personal domain
- Fitness office: Personal Trainer + Dietitian
- Planning office: Scheduler + Email

Map sites, OpenClaw gateway instances, protected domains, functional offices and specialist agents without confusing an attractive visual diagram with actual isolation.
A visual world represents a Site—a physical or virtual installation. A site can contain one or more gateways. Each gateway can host many agent instances, while protected domains define what must remain segregated through actual identity, storage and tool policies. Offices are functional groups, not security controls.
Important: A separate gateway does not automatically isolate the host, and two domain cards sharing a gateway are not automatically confidential from each other. Enforce filesystem, credentials, network, agent tool permissions, session, container and operator policy boundaries independently.
A private deployment for household support, fitness planning and personal correspondence.
Company operations where legal records, media publishing and executive functions require deliberate separation.
Technical operations and bounded test environments, with agent requests separate from execution authority.
Usually the simpler choice: agent IDs, workspaces, sessions and routing bindings organize multiple specialist agents in one gateway process. Configure per-agent tool and sandbox restrictions and audit the actual limits.
Consider a separate instance for disaster recovery, incompatible environments, or stronger separation. Give every gateway distinct configuration and state directories, workspaces, ports and service profiles; verify host- and credential-level boundaries too.
Legal matters, customer data, personal information and production systems may need separate domains even if they appear within one visual site. Do not imply enforcement without approved controls and verification.
A Reporter can propose a publishing request, or a Trainer can submit a scheduling suggestion. Transfers between gateways or domains require explicit, scoped interfaces and audit trails—not implicit shared access.
Not necessarily. Worlds visualize Sites. A Site may represent a host, VM or installation; multiple gateways can operate on one host with separately configured runtime state.
No. OpenClaw supports multiple agents in a single gateway. Separate gateways are situational tools, not a default requirement for every role.
No. Gateway separation can reduce accidental shared-state risks, but privileged sockets, host filesystem access, secrets, network exposure and human approval rules still require their own enforcement.
Sources: OpenClaw multi-agent documentation · Multiple gateways and isolation checklist · Gateway configuration. These are architecture examples, not a claim that every pictured agent or gateway is deployed.
Browse the Agent Atlas