Compare
Most frameworks orchestrate. AEOESS enforces.
Agent frameworks help you build agents. AEOESS handles what happens when those agents act in production: who they are, what they're allowed to do, and what the audit trail looks like when they violate a constraint.
Cross-Impl Interop
Same fixture, byte-match.
Six independent implementations. One reference fixture set. SHA-256 byte-match across all of them.
The mesh, animated
Where the protocol lives.
Frameworks orchestrate; the protocol binds. Agents, humans, services connected by signed delegations and receipts that any auditor can verify without aeoess in the loop.
Capability comparison
| Capability | AEOESS | LangChain | AutoGen | CrewAI |
|---|---|---|---|---|
| Cryptographic identity | Ed25519, BYO DID | – | – | – |
| Scoped delegation | Narrow-only chains | Manual | Manual | Manual |
| Cascade revocation | Tree-wide, instant | – | – | – |
| Signed action receipts | RFC 8785 envelopes | – | – | – |
| Commerce pre-flight | 4-gate spending control | – | – | – |
| Cross-vendor audit | Verify without aeoess | – | – | – |
| Framework lock-in | None, works alongside any | Tight | Tight | Tight |
| Open governance | Apache-2.0 + IETF draft | MIT | MIT | MIT |
| Production gateway | Hosted + self-host | – | – | – |
| Independently cited | UBC PDR, Microsoft | – | – | – |
Comparison reflects published OSS surface as of May 2026. Frameworks ship orchestration; AEOESS ships enforcement. They compose.
For AI agents: llms-full.txt · MCP descriptor