← Back to Documentation
Operations
Usage Analytics
Track requests, tokens, latency, and estimated cost across users, providers, and models.
Key Steps
- Use the dashboard for quick operational health and the usage report for deeper review.
- Export reports for finance, operations, and provider budget discussions.
- Compare provider and model trends before changing defaults or quotas.
Article Scope
This guide focuses on the operational steps needed to run Orchestris with team access, provider control, and predictable usage.
Visual Reference
What to review
- Monthly request and token volume.
- Estimated spend by provider and model.
- Latency trends that could affect user experience.
Cost review workflow
- Review top models and high-usage teams before invoices close.
- Look for sudden changes after onboarding waves or model-default changes.
- Export snapshots for finance when usage needs explanation outside the portal.
Operational signals
- High latency may indicate provider issues, network placement, or overloaded private model hosts.
- Unexpected provider mix may mean default routing needs adjustment.
- Low usage after rollout may mean users need onboarding or client access help.
Related Topics
Operations
Conversation Management
Help users organize work while keeping shared policies and retention expectations clear.
Operations
Multi-device Sync
Keep the same workspace, conversations, and model access available across client platforms.
Operations
Performance Tips
Improve perceived latency, provider reliability, and private model throughput.