mission-control and clawd-control
These two tools are competitors, both offering self-hosted dashboards for the orchestration and monitoring of AI agents, with Mission Control providing a more comprehensive platform for task dispatch, multi-agent workflows, and spend governance, while Clawd Control is specifically designed for monitoring and managing Clawdbot AI agents.
About mission-control
builderz-labs/mission-control
Self-hosted AI agent orchestration platform: dispatch tasks, run multi-agent workflows, monitor spend, and govern operations from one mission control dashboard.
Built on Next.js 16 with TypeScript, it uses SQLite for persistence and WebSocket/SSE for real-time updates—no external databases required. Supports multi-gateway connections with framework adapters for OpenClaw, CrewAI, LangGraph, and AutoGen, plus a Skills Hub for discovering and auditing agent capabilities from public registries. Features a four-layer security evaluation framework with trust scoring, secret detection, and MCP call auditing across configurable hook profiles (minimal/standard/strict).
About clawd-control
Temaki-AI/clawd-control
🏰 Real-time dashboard for monitoring and managing Clawdbot AI agents
Provides live fleet monitoring via Server-Sent Events, auto-discovers local Clawdbot agents, and offers deep agent introspection including session history and configuration management. Built as a deliberately minimal Node.js server with vanilla HTML/JS frontend and no build tooling, communicating with Clawdbot agents via WebSocket and polling their metrics at configurable intervals. Supports both local auto-discovery and manual remote agent configuration with token-based authentication.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work