Ask the provider
Can we review independent reports, data location, retention, training terms, breach response windows, subcontractors, key handling, egress controls and audit exports?
Neither a vendor logo nor a local install is a security guarantee. The right question is who controls the trust boundary, what evidence is available, and who responds when something fails.
Vendor-risk decisions
Managed service providers are not automatically insecure, and local deployment is not automatically safe. A provider may publish strong policies, audits and contractual commitments. A self-hosted platform offers different responsibilities: patching, monitoring, backups, identity, operator review and incident response remain yours.
Can we review independent reports, data location, retention, training terms, breach response windows, subcontractors, key handling, egress controls and audit exports?
Can we actually patch OpenClaw, harden Podman, rotate credentials, collect tamper-resistant logs, and restore from backups?

“The brochure says enterprise security. Are we covered?”

“The brochure is the beginning of diligence. Ask for the SOC report scope, data map, IAM model, log exports, network diagram and tested recovery objectives.”
For example, Gumloop publishes a trust center with SOC 2 Type II and other assertions. Those claims deserve a fair review of the underlying report and scope, not dismissal.
| Control | Managed service question | Self-managed Clawsolator question |
|---|---|---|
| Data custody | Where is data stored and processed? Who can access it? | What data still leaves for model APIs, integrations or backups? |
| Security evidence | Can we inspect reports, incident records, logs and test scope? | Do we export daemon logs and preserve audit integrity? |
| Isolation | What separates tenants and credentials? | How are Podman, mounts and gateway identities actually configured? |
| Operations | Who approves changes and responds after hours? | Who owns host approvals, patching and incident response? |
Explore the evidence
Inspect the controls, verify the boundaries, and ask what happens after a failure—not merely before it.
Explore the security lattice →Read the architecture →OpenClaw, OpenShell, Hermes, ZeroClaw, Gumloop, Aider, Continue and cloud providers solve overlapping but different problems. Find what each actually provides, what you must still configure, and what XMAN adds.