Get an OpenClaw control plane online without operating one yourself.
Connect an OpenClaw runtime, enroll it into a workspace, publish desired state, and verify what actually changed.
Start with identity, users, heartbeat, agents, settings, scoped rules, and verification before expanding into execution management.
Connect, publish, verify.
Phase 1 focuses on a small set of governance objects that are easy to inspect before and after rollout.
Start with Pilot, Starter, or Scale. Checkout creates the billing handoff before workspace setup.
Name the team workspace and choose the expected first agent count.
Copy the setup prompt to OpenClaw, Claude Code, Codex, or a custom agent. The setup command bootstraps acp-sync if needed.
Review the sync report so the dashboard shows what applied, what changed, and what still needs attention.
What Phase 1 controls.
Every object has a clear owner, scope, and verification path.
Agent identity, host ownership, runtime role, and enrollment status.
Human users, workspace membership, and accountability records.
Expected check-in cadence, last-seen signals, and stale-agent handling.
Managed agents, labels, runtime bindings, and governance coverage.
Workspace defaults, sync preferences, adapter settings, and rollout behavior.
Organization, project, workspace, and agent-specific policy inheritance.
What you can verify in a pilot.
Know what the pilot proves before creating production data.