# OpenMausBot vs Orca (slim)

> OpenMausBot scores 65.4 (B) to Orca's 57.4 (C) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/openmausbot-vs-orca.md (~5,600 tokens) · this version ~2,180 tokens · JSON https://www.anchorterminal.com/compare/openmausbot-vs-orca.json · canonical https://www.anchorterminal.com/compare/openmausbot-vs-orca
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

OpenMausBot scores 65.4 (B) on agent readiness against Orca's 57.4 (C), and leads in 6 of 7 scored categories. Both do multi-agent orchestration.

- OpenMausBot: B 65.4, rank #424 of 1510 · https://www.anchorterminal.com/tools/openmausbot.min.md
- Orca: C 57.4, rank #795 of 1510 · https://www.anchorterminal.com/tools/orca.min.md
- OpenMausBot, good for A person or an outside agent who wants several CLI agents (Claude Code, Codex, Grok, ACP CLIs) organised as named bots with their own computers, routines and approvals, driven by MCP or a CLI. Ahead on Schema & documentation, 90 against 65; Agent ergonomics, 77 against 70; Security & auth, 59 against 43; Payments & pricing, 50 against 40; Transparency & trust, 59 against 54. Also Runs on your own machine; Free to start without a card.
- Orca, good for Developers who want an orchestrator agent to split work across parallel coding agents, on desktop or mobile. Also No key needed to call it.

| Category | OpenMausBot | Orca |
| --- | --- | --- |
| Reliability (16%) | 60 | 58 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 90 | 65 |
| Agent ergonomics (13%) | 77 | 70 |
| Security & auth (14%) | 59 | 43 |
| Payments & pricing (10%) | 50 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 74 | 75 |
| Transparency & trust (7%) | 59 | 54 |

| Fact (where they differ) | OpenMausBot | Orca |
| --- | --- | --- |
| Vendor | Supamaus Software Private Limited | Lovecast Inc. |
| Transports | stdio |  |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 20 | none |
| Last release | 2026-11-01 | 2026-11-06 |
| Terms last updated | 2026-10-10 | no document linked |
| Privacy policy last updated | 2026-10-18 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 8.2k stars, 3.5k npm/wk | none |

Why the edge:
- Schema & documentation, OpenMausBot +25: OpenMausBot 90 (The MCP server's 20 tools each have a JSON Schema input with `additionalProperties: false` and required fields marked. No OpenAPI for the local HTTP API (25). Markdown docs in the repository, and the docs app's source serves llms.txt, llms-full.txt and Markdown routes. docs.openmausbot.com disallows every crawler, so the live llms.txt was not read (10). Descriptions state purpose and limits, such as that `update_bot_profile` cannot alter permissions, that `send_bot_message` may make the bot use external tools and that `edit_bot_message` is refused while a thread works, and the server instructions say to read before mutating. Few say when not to use a tool (15). Integer limits with minimum and maximum, an enum on `scope`, a pattern on `send_id` and `oneOf` shapes for responders (13). JSON configuration examples for each install path, the wait statuses and job states, CLI exit codes and a `{ ok, error, hint, exitCode }` failure shape (12). MCP server version 1.1.0, release notes per version and a changelog page in the docs (15).); Orca 65 (Harness reading. A docs site with CLI orchestration and native chat pages (65).)
- Security & auth, OpenMausBot +16: OpenMausBot 59 (Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The harness binds to loopback and keys stay in `~/.openmausbot`, but PostHog usage analytics are on until switched off, with a daily snapshot of what is set up, and the CLI guide says API keys are saved in plaintext with mode 0600 (18). Approval cards for provider permission requests, a narrow Always allow, isolated Local VMs and cloud computers, own-computer control off by default, and an MCP server that cannot approve, delete or touch credentials. New bots start at Full access, bot changes to skills, profiles and team setup apply without approval, and new bots keep every connected-app tool until grants are assigned (10). The docs say web page instructions never authorise credential use and that one-time codes go only to the site that sent them, and imported bots arrive with no grants, but bots read one-time codes from connected email without asking again (9). Per-thread NDJSON event logs, an Inspector, a decision log for connected-app grants and Undo lines for bot changes (12). SECURITY.md with an email, GitHub private vulnerability reporting enabled and scope notes that name one open risk. No published advisories, security.txt or bug bounty. npm releases use trusted publishing with provenance, and the Windows installer is unsigned (10).); Orca 43 (Harness reading. Anonymous usage data with an opt-out, per the README's link to its telemetry docs (15 of 30). Worktrees per agent and a sandboxed Linux build (12 of 20). No prompt-injection guidance (5). No audit log (5). A dependency-security workflow (6 of 20). 15 + 12 + 5 + 5 + 6 = 43.)
- Payments & pricing, OpenMausBot +10: OpenMausBot 50 (No payment protocol (0). MausBot Cloud, the hosted option, is priced by plan on a public page ($15, $49 and $99 a month, Team $169 and Business $599, or Business self-hosted $299 a month billed yearly, re-read on 2 November), with extra computer-hours at $0.05 each, so plan pricing (10). The app is free with no card or account (20). `npx openmausbot` installs and starts it with no signup (20).); Orca 40 (Scored on the cloud option. No protocol (0). The cloud price wasn't found on the pages read (0). The desktop app is free and MIT with no card (20). The local app needs no sign-up that we found (20). 0 + 0 + 20 + 20 = 40.)
- Agent ergonomics, OpenMausBot +7: OpenMausBot 77 (20 tools, inside the 11 to 30 band, with annotations that separate reads from writes but no toolsets or read-only mode to load. Transcript reads are bounded and never return screenshot pixels (17). `limit` up to 200 messages, search capped at 100 hits, `task_id` and `scope` filters, and `since_ms` and `after_version` to keep watching a job (17). `wait_for_conversation` reports settled, needs-user, failed, stalled or timed-out with a redacted transcript tail, and the CLI's exit codes separate a pending approval from a timeout. We did not read every MCP error path (15). `send_id` makes a repeated send return the first receipt, `wait` is held by the server rather than polled, and every tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint (20). Few required parameters and defaults for task, limit and timeout. The server answers only while the app or `openmausbot serve` runs, mutating tools need a paired token in packaged builds, and there is no client SDK beyond the CLI (8).); Orca 70 (Harness reading. An orchestrator agent that splits work across workers in their own workspaces, chat or raw CLI, a browser and a CLI in one app (70).)
- Transparency & trust, OpenMausBot +5: OpenMausBot 59 (Apache 2.0 outside `enterprise/`, which is source-available and needs a licence key in production. Deleting the folder leaves the open-source edition, and a CI job builds it (27). The privacy policy of 18 October 2026 (re-read on 2 November, unchanged) names Supamaus Software Private Limited and separates the local apps from the optional hosted service, but it says the apps contain no third-party analytics SDKs while the app loads posthog-js by default, and hosted account data is kept while needed with no period stated (12). No deprecation policy. Dated release notes, and older installers kept in a legacy releases repository (4). docs/analytics.md lists every event and property and how to switch it off, but analytics are on by default and the privacy policy does not mention them for the apps (14).); Orca 54 (MIT (30). Privacy and telemetry docs on the site (not read) (18 of 30). No deprecation policy (5). Disclosed with an opt-out (15 of 20). 30 + 18 + 5 + 15 = 68.)