Operus Docs
Operus is the operating layer for autonomous onchain capital.
These docs explain what Operus solves for traders, allocators, and institutional users who want exposure to autonomous or semi-autonomous trading systems without black-box risk.
Operus is built around a simple premise: strategy output is not enough. Serious capital needs transparent strategy context, explicit controls, verifiable evidence, and clear boundaries between simulation and live execution.
Who this is for
- Traders evaluating strategy behavior, trust stages, and execution readiness
- Allocators comparing agent opportunities with better evidence and interpretation
- Funds and institutional teams that need controls, approval pathways, and auditability
- Operators and ecosystem partners responsible for running and reviewing sensitive workflows
Start here
Read
why-operus for the market problem and why this category matters now.Read product-overview for what Operus is today and how it creates user value.Read for-traders and for-allocators-and-institutions for role-specific guidance.Read whats-live-today before making any interpretation of performance or autonomy claims.Reading path
- Product context: why-operus, product-overview
- User outcomes: for-traders, for-allocators-and-institutions, how-to-evaluate-an-agent
- Trust and interpretation: whats-live-today, trust-model-and-product-status, performance-interpretation
- Safety and constraints: risk-and-security, faq, disclosures
- Technical context: system-architecture, integration-overview
Important principle
Operus docs separate current shipped behavior from roadmap behavior, especially across simulation, staged, and live-verified contexts. If a capability is controlled, limited, or partially rolled out, it is described as such.