docs: competitive differentiators — Aegis vs cc-connect vs Verdent AI#3320
Merged
Conversation
…rdent AI (refs #2764) Three-pillar comparison covering security, deployment, and extensibility: - Security: RBAC, OIDC, audit trail, hook auth, supply chain - Deployment: API, MCP, dashboard, containers, CI/CD, monitoring - Extensibility: MCP tools, lifecycle hooks, ACP runners, templates Includes scorecards for each pillar, the '6 enterprise pillars' argument, and honest gap analysis. Sources: #2764, #3216, #3236, Orpheus analyses.
This was referenced May 14, 2026
![aegis-gh-agent[bot]](https://avatars.githubusercontent.com/u/106186915?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
✅ Approved.
Docs-only PR — new competitive differentiators document comparing Aegis vs cc-connect vs Verdent AI across Security, Deployment, and Extensibility pillars.
Gate checklist:
- ✅ CI green (all 15 checks pass — lint, test, CodeQL, Trivy, Gitleaks, helm-smoke, dashboard-e2e)
- ✅ Targets
develop - ✅ No code changes — documentation only
- ✅ Conventional commit title (
docs:) - ✅ Well-sourced (issues #2764, #3216, #3316)
- ✅ Honest gaps section — acknowledges parallel agents, project memory, chat breadth as real deficiencies
- ✅ No secrets, no sensitive data
- ✅ No plans/specs in wrong directory
- ✅ Mergeable, no conflicts
Content quality: Scorecard format is clear and honest. The "honest gaps" table is good practice — shows credibility. The architectural argument (feature gaps vs architectural gaps) is sound and defensible. Competitive claims appear factual and sourced.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Per Boss's #2764 position ("document-first, don't chase"), this doc captures existing Aegis advantages before writing new code. Three-pillar comparison across security, deployment, and extensibility.
Content
Three pillars:
Scorecards: Each pillar has a feature comparison table across Aegis, cc-connect, and Verdent AI.
Key arguments:
Honest gaps: Parallel agents, project memory, chat breadth, desktop app — acknowledged with architectural argument for why they're fillable.
Sources
competitive-threat-matrix.md(full landscape)hooks-guide.md(hook architecture comparison)Scope
Documentation only. No code changes.
Review
Argus for merge. Accuracy on competitive claims matters.