# OpenClaw vs SOAT: Feature Comparison

> OpenClaw and SOAT compared on 15 agent capabilities, 6 vs 12 native, each rating linked to its source.

# SOAT vs OpenClaw

OpenClaw is an agent framework (MIT, self-hosted). SOAT is agent infrastructure (Apache-2.0, self-hosted). Of the 15 capabilities the [benchmark](/benchmark) tracks, OpenClaw covers 6 natively and SOAT 12.

## At a glance

| | OpenClaw | SOAT |
| --- | --- | --- |
| Type | an agent framework | agent infrastructure |
| License | MIT | Apache-2.0 |
| Deployment | self-hosted | self-hosted |
| Native capabilities | 6 of 15 | 12 of 15 |
| Last verified | 2026-08-14 | 2026-08-14 |

## Where each one leads

- **OpenClaw** is native where SOAT is not: channels, code execution.
- **SOAT** is native where OpenClaw is not: orchestration, identity & governance, observability, data & secrets, evaluation, multi-tenancy, declarative deployment, versioning & rollout.

## What OpenClaw is

Open-source personal AI assistant framework: a local gateway control plane connecting AI models to WhatsApp, Telegram, Slack, Discord, Signal, and iMessage, with tools, skills, MCP, scheduling, and optional sandboxed execution — built for a single operator who owns their data. [OpenClaw documentation](https://openclaw.ai).

## Capability by capability

### Agent runtime

_Agent loop, sessions, and generation lifecycle._

- **OpenClaw: Native.** Gateway-managed sessions running AI-driven workflows with tools and skills. ([source](https://github.com/openclaw/openclaw))
- **SOAT: Native.** Agents, sessions, chats, and generations with full lifecycle tracking. ([source](https://soat.ttoss.dev/docs/modules/agents))

### Orchestration

_Multi-step pipelines, workflows, and triggers._

- **OpenClaw: Partial.** Scheduling for unattended automations; no declarative DAG/workflow engine. ([source](https://github.com/openclaw/openclaw))
- **SOAT: Native.** DAG orchestrations, workflow state machines, durable tasks, and triggers (manual, webhook, schedule). ([source](https://soat.ttoss.dev/docs/modules/orchestrations))

### Knowledge & memory

_Documents, embeddings, semantic search, and recall._

- **OpenClaw: Native.** Session and contextual memory managed by the gateway across channels. ([source](https://github.com/openclaw/openclaw))
- **SOAT: Native.** Documents with per-chunk embeddings, named memories, unified semantic search, and ingestion rules for PDFs, images, and audio. ([source](https://soat.ttoss.dev/docs/modules/knowledge))

### Tools & integration

_Tool calling, MCP, providers, and webhooks._

- **OpenClaw: Native.** Tools, skills, plugins, and MCP integrations distributed through ClawHub. ([source](https://github.com/openclaw/openclaw))
- **SOAT: Native.** HTTP, MCP, client, and agent-to-agent tools; model routes with failover; webhooks; any LLM provider. ([source](https://soat.ttoss.dev/docs/modules/tools))

### Identity & governance

_IAM, guardrails, approvals, quotas, and audit._

- **OpenClaw: Partial.** Pairing controls and access management for a single operator — not multi-tenant IAM, policies, quotas, or approvals. ([source](https://github.com/openclaw/openclaw))
- **SOAT: Native.** AWS-inspired IAM, actors, scoped API keys, guardrails, human approvals, quotas, and an append-only audit log. ([source](https://soat.ttoss.dev/docs/modules/iam))

### Observability

_Traces, activity, usage, and failure queues._

- **OpenClaw: Absent.** No structured trace, usage, or audit model beyond gateway session logs.
- **SOAT: Native.** Traces of every tool call and model response, activity feed, usage/cost tracking, and an exceptions queue. ([source](https://soat.ttoss.dev/docs/modules/traces))

### Data & secrets

_File storage and encrypted secrets._

- **OpenClaw: Absent.** No managed file storage or encrypted secrets store.
- **SOAT: Native.** File storage over local/S3/GCS backends and encrypted secrets storage. ([source](https://soat.ttoss.dev/docs/modules/files))

### Evaluation

_Datasets, scorers, and eval-gated improvement._

- **OpenClaw: Absent.** No built-in datasets, scorers, or eval runs.
- **SOAT: Native.** Datasets, scorers, and scored runs; eval-gated promotion of agent versions. ([source](https://soat.ttoss.dev/docs/modules/evaluations))

### Channels

_Built-in gateways to messaging platforms and UIs._

- **OpenClaw: Native.** First-class gateways for WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, and iMessage — its headline feature. ([source](https://github.com/openclaw/openclaw))
- **SOAT: Absent.** Surfaces are REST, MCP, CLI, and SDK — no built-in gateways to messaging platforms like Slack, WhatsApp, or Telegram.

### Code execution

_Sandboxed code or terminal runtimes for agents._

- **OpenClaw: Native.** Optional isolated (sandboxed) execution environments for tool runs. ([source](https://github.com/openclaw/openclaw))
- **SOAT: Absent.** Tool types are HTTP, MCP, client, and agent-to-agent — no built-in sandboxed code or terminal runtime.

### Human-in-the-loop

_Pausing a run for human approval, then resuming it._

- **OpenClaw: Native.** The gateway broadcasts an approval-requested event that pauses the command while operator clients resolve it, with ask modes and a deny or allowlist fallback on timeout. ([source](https://docs.openclaw.ai/tools/exec-approvals))
- **SOAT: Native.** Approvals are a first-class human-decision queue with frozen evidence, and guardrails classify each tool call so risky actions pause for a decision. ([source](https://soat.ttoss.dev/docs/modules/approvals))

### Multi-tenancy

_Projects or workspaces scoping resources and permissions._

- **OpenClaw: Absent.** The security model is one trusted operator per gateway; isolation means running a separate gateway process and state tree per trust domain, not tenant scoping inside one deployment.
- **SOAT: Native.** Projects are multi-tenant namespaces scoping every resource, with IAM policies and quotas enforced per project. ([source](https://soat.ttoss.dev/docs/modules/projects))

### Declarative deployment

_Templates that provision agent resources as one stack._

- **OpenClaw: Absent.** Agents are declared in gateway config files and deployed with Docker Compose, but there is no dependency-graph provisioning of agent resources with plan/apply.
- **SOAT: Native.** Formations provision providers, memories, tools, agents, orchestrations, and webhooks from one template, resolving refs into a dependency graph with tracked operations. ([source](https://soat.ttoss.dev/docs/modules/formations))

### Versioning & rollout

_Agent versions, canary rollout, gated promotion._

- **OpenClaw: Absent.** No immutable agent definition versions, aliases, canary rollout, or rollback; skills carry a version field but agents themselves are unversioned.
- **SOAT: Native.** Every config change is archived as an append-only agent version, with canary rollout to a slice of traffic and eval-gated promotion. ([source](https://soat.ttoss.dev/docs/tutorials/agent-versioning-and-canary-rollout))

### Skill learning

_Agents authoring reusable skills from their own experience._

- **OpenClaw: Partial.** The Skill Workshop has the agent draft a proposal when it spots reusable work rather than writing skills directly, and a human reviews and approves before changes land. ([source](https://docs.openclaw.ai/tools/skills))
- **SOAT: Absent.** Memories and knowledge store retrievable context, but agents do not author or refine reusable skills from their own experience.

## How this is rated

Each rating comes from the public documentation linked beside it: **Native** is built in, **Via plugin** needs an add-on, **Partial** covers part of the capability, **Absent** is not offered. Every solution side by side is on the [benchmark](/benchmark). A rating that is out of date is a bug: [open an issue](https://github.com/ttoss/soat/issues).