mission-control and clawforge
These two tools are competitors, with Mission Control offering a more comprehensive self-hosted AI agent orchestration platform while Clawforge provides a simpler dashboard for managing AI assistants.
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 clawforge
ClawForgeAI/clawforge
One dashboard for all your AI assistants
Provides centralized policy enforcement, skill governance, and audit logging for OpenClaw instances, with features like tool allow/deny lists, emergency kill switches, and heartbeat monitoring across distributed deployments. Integrates SSO/OIDC providers (Okta, Auth0, Entra ID) alongside native auth, and exposes a queryable audit trail of all tool calls and LLM interactions. Deployed via Docker Compose, it communicates with OpenClaw gateways to enforce policies and track policy version compliance across the fleet.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work