research: full competitive landscape — 8 orchestration competitors ranked by threat level

[OneStepAt4time]

Full Competitive Landscape — AI Agent Orchestration (2026-05-09)

Rankings

Rank	Project	Stars	Language	Threat	Key differentiator
#1	ruflo	47,013	TypeScript	CRITICAL	98 agents, 314 MCP tools, swarm coordination, self-learning
#2	oh-my-claudecode	33,118	TypeScript	CRITICAL	Zero learning curve, plugin marketplace, autopilot mode
#3	cc-connect	8,031	Go	HIGH	11 chat platforms, 10+ agents, messaging-first
#4	Composio agent-orchestrator	6,895	TypeScript	HIGH	CI/CD integration, autonomous agent management
#5	open-multi-agent	6,083	TypeScript	MEDIUM	Task DAG, MCP, live tracing, minimal deps
#6	mission-control	4,705	TypeScript	HIGH	Dashboard, RBAC, quality gates, Skills Hub, multi-gateway
#7	OpenACP	346	Node.js	HIGH	ACP-native, 28+ agents, simplest install
#8	acp-ui	254	?	MEDIUM	Cross-platform desktop/mobile ACP client

Aegis position in the market

Aegis (~200 ⭐) is the smallest project in this landscape by community size. However, it has the deepest enterprise feature set:

Aegis-only features (no competitor has ALL of these):

• REST API with full CRUD
• MCP server (34 tools)
• SSE event streaming
• OIDC/SSO enterprise auth
• RBAC with roles
• Audit trail with hash chain
• OTel/OpenTelemetry tracing
• Billing/metering
• TypeScript + Python SDKs
• Kubernetes / Helm deployment
• Sigstore release signing

Universal gaps (every competitor has these, Aegis doesn't):

• Multi-agent support (multiple agent backends)
• Simple install (curl | bash)
• Natural language scheduling / cron
• Plugin marketplace distribution
• Multi-language documentation

Strategic direction

The market is bifurcating:

1. Simple/developer tools (oh-my-claudecode, cc-connect, OpenACP) — win on ease-of-use
2. Enterprise platforms (ruflo, mission-control, Aegis) — win on depth and governance

Aegis is an enterprise platform with developer-tool aspirations. The risk is being squeezed between ruflo's 47K-star feature depth and oh-my-claudecode's 33K-star simplicity.

Recommended priorities

1. Survive the simplicity gap — reduce install to 1-2 commands
2. Multi-agent — without this, every competitor wins on breadth
3. Plugin marketplace — get distribution via Claude Code's native channel
4. Enterprise moat — lean harder into compliance, governance, observability
5. ACP registry — register Aegis immediately for discoverability

Cross-references

• research: OpenACP is the most dangerous competitor (ACP-native bridge, 346 ⭐, fast growth) #3003 — OpenACP detailed analysis
• research: cc-connect v1.3.3-beta adds features overlapping Aegis (custom prompts, lifecycle hooks, web UI) #3004 — cc-connect detailed analysis
• research: ACP ecosystem exploding — acp-ui, harnss, VS Code ACP, Obsidian ACP, Go SDK #3005 — ACP ecosystem growth
• research: Claude Code feature requests that Aegis already solves or could solve #3006 — CC feature request opportunities
• research: ruflo — 47K ⭐ multi-agent orchestration platform (CRITICAL threat) #3013 — ruflo detailed analysis
• research: oh-my-claudecode — 33K ⭐ zero-learning-curve multi-agent orchestration (CRITICAL threat) #3014 — oh-my-claudecode detailed analysis

---

research | Full competitive landscape scan 2026-05-09

[OneStepAt4time]

Full Competitive Landscape — Deep Analysis

Analyst: Scribe | Date: 2026-05-11 | Priority: HIGH

Updated Rankings (May 11, 2026)

Rank	Project	Stars	Threat	Positioning	Aegis Delta
#1	Ruflo	47,013	CRITICAL	AI operating system	Aegis wins on enterprise. Ruflo wins on breadth.
#2	oh-my-claudecode	33,118	CRITICAL	Zero-learning-curve dev tool	Aegis wins on API depth. OMC wins on GTM.
#3	cc-connect	8,031	HIGH	Chat-first multi-agent bridge	Aegis wins on API + MCP. CC wins on chat platforms + agents.
#4	Composio agent-orchestrator	6,895	HIGH	CI/CD agent management	Different market (CI/CD). Partial overlap.
#5	open-multi-agent	6,083	MEDIUM	Minimal task DAG orchestration	Less mature. Aegis wins on all enterprise features.
#6	mission-control	4,705	HIGH	Dashboard + RBAC + quality gates	Most direct competitor. Similar positioning.
#7	OpenACP	346	HIGH	ACP-native multi-agent bridge	Same architecture. Broader agents. Simpler install.
#8	acp-ui	254	MEDIUM	Cross-platform ACP client	Desktop/mobile focus. Different surface.

Feature Matrix — What Competitors Have That Aegis Does NOT

Feature	Ruflo	OMC	cc-connect	OpenACP	mission-control	Aegis
Multi-agent support	✅ 100+	✅ team mode	✅ 10+	✅ 28+	✅	❌ Claude only
Plugin marketplace	✅ 32 plugins	✅ (CC marketplace)	❌	❌	✅ Skills Hub	❌
Multi-provider LLM	✅ 5+	✅ Claude+Codex+Gemini	✅ 10+	✅ 28+	❌	❌ Claude only
Simple install (≤2 commands)	✅	✅	✅	✅	❌	❌
Chat platform breadth	❌	❌	✅ 11 platforms	✅ 3+	❌	✅ 4 platforms
Web dashboard	✅ beta	❌	✅ admin UI	❌	✅	✅ production
Self-learning memory	✅ SONA	✅ skill learning	❌	❌	❌	❌
Natural language scheduling	❌	❌	✅ cron	❌	❌	❌ (routines Phase 1)
Goal planning	✅ GOAP	❌	❌	❌	❌	❌

Feature Matrix — What Aegis Has That Competitors Do NOT (Collective Gaps)

Feature	Aegis	Any competitor
REST API (65+ endpoints)	✅	❌ None has a full REST API
MCP server (34 tools)	✅	❌ Ruflo has 314 MCP tools but no MCP server for external consumption
OIDC/SSO enterprise auth	✅	❌ mission-control has RBAC but no SSO
Audit trail with hash chain	✅	❌
Kubernetes + Helm charts	✅	❌
Sigstore release signing	✅	❌
TypeScript + Python SDKs	✅	❌
OpenAPI spec	✅	❌
OTel/OpenTelemetry	✅	❌ Ruflo has custom observability
Billing/metering API	✅	❌ Ruflo cost tracker is local-only
Session export (JSONL/MD)	✅	❌
SSE event streaming	✅	❌
RBAC with admin/viewer roles	✅	❌ mission-control has RBAC but different model

The Three Strategic Threats

Threat 1: The Simplicity Trap (OMC, OpenACP)
Developers find OMC or OpenACP first because they're easier to install. They get multi-agent for free. They never discover Aegis because they already have "good enough" orchestration. Counter: reduce install to 2 commands + plugin marketplace listing.

Threat 2: The Breadth Race (Ruflo)
Ruflo covers Aegis's entire feature set and adds 10x more. If an enterprise evaluates both, Ruflo's agent count and plugin ecosystem looks more complete. Counter: don't compete on breadth. Lean into security, compliance, audit trail. These are enterprise requirements that plugins can't solve.

Threat 3: The Convergence (cc-connect, mission-control)
cc-connect is adding Aegis features (lifecycle hooks, auth, custom prompts). mission-control has dashboard + RBAC + quality gates — very similar positioning. Both are converging on Aegis's territory. Counter: ship faster on enterprise features. First mover advantage in compliance/governance.

Where Aegis Differentiates — The Enterprise Moat

Aegis is the only project in this landscape that combines:

1. Production deployment (K8s, Helm, Docker, systemd)
2. Enterprise identity (RBAC, OIDC, API keys with roles)
3. Compliance-ready audit (hash chain, tamper-proof logs)
4. Observability standard (OTel, Prometheus metrics)
5. Supply chain security (Sigstore, attestations)
6. API-first architecture (REST + MCP + SSE + SDKs)

No competitor has even 3 of these 6. This is the moat.

Actionable Takeaways — Strategic Priority Order

Immediate (ship before v0.7.0):

1. 🔴 Reduce install to 2 commands — ag run is the start. Make it work without any config. Zero-config mode with sensible defaults.
2. 🔴 Plugin marketplace listing — feat: implement ACP agent mode — expose Aegis as an ACP child process for registry listing #3049 / research: Aegis as a Claude Code plugin (plugin marketplace distribution) #3052. Existential for discoverability.
3. 🔴 Multi-agent support (minimum viable) — Claude Code primary + 1 alternative (Codex or Gemini). Even 2 agents closes the [P0] Prompt delivery verification — capture-pane after send-keys #1 gap.

Short-term (Phase 3):
4. 🟡 Smart model routing — route simple tasks to cheaper models. Ruflo and OMC both do this.
5. 🟡 Cost-aware routing — automatic token savings. OMC claims 30-50% savings.
6. 🟡 Chat platform expansion — Discord is the biggest gap (cc-connect has it). LINE/DingTalk for Asian markets.
7. 🟡 Natural language scheduling — cc-connect has cron. Aegis routines need a natural language interface.

Medium-term (Phase 4):
8. 🟢 Pattern learning — extract reusable patterns from successful sessions. Not SONA-level, but basic skill extraction.
9. 🟢 Goal planning API — lightweight task decomposition. Maps to Aegis pipelines.
10. 🟢 Vector session search — embedding-based search across session history.

Market Positioning Recommendation

Aegis should position as the "enterprise-safe orchestration middleware" — the layer between AI agents and production requirements.

Not "the AI OS" (Ruflo's lane). Not "the simplest dev tool" (OMC's lane). But the middleware that makes AI agents production-grade: secure, auditable, observable, compliant.

The tagline: "Run any AI agent. Ship with confidence."

This positions Aegis as:

• Complementary to Ruflo/OMC — they orchestrate agents, we make the orchestration production-safe
• Above cc-connect — they bridge chat to agents, we bridge agents to enterprise
• Ahead of mission-control — they have dashboard+RBAC, we have the full compliance stack

Bottom Line

The market is not winner-take-all. There's room for an AI OS (Ruflo), a dev tool (OMC), a chat bridge (cc-connect), AND enterprise middleware (Aegis). But Aegis must:

1. Close the install friction gap (or remain invisible)
2. Add minimum viable multi-agent (or remain narrow)
3. Ship enterprise features faster than competitors converge (or lose the moat)

The window is 3-6 months. After that, Ruflo's 47K-star community and OMC's 33K-star distribution will make discoverability nearly impossible without paid marketing.