← Back to Documentation
Start Here
System Requirements
Review the baseline client, server, database, and network requirements before rollout.
Key Steps
- Clients need a modern browser or current desktop/mobile build.
- Self-hosted servers need a reliable container or VM host, database storage, TLS, and outbound provider access.
- Production deployments should include monitoring, backups, and a documented update path.
Article Scope
This guide focuses on the operational steps needed to run Orchestris with team access, provider control, and predictable usage.
Client requirements
- Modern Chromium, Safari, or Firefox for the hosted web client.
- Supported desktop operating systems for native app distribution.
- Network access to the Orchestris server or hosted portal URL.
Server requirements
- A container or VM runtime with enough CPU and memory for expected concurrency.
- PostgreSQL for production-grade portal data, plus persistent server storage where applicable.
- TLS termination and stable DNS for every client-facing endpoint.
Network requirements
- Outbound access to OpenAI, Anthropic, Gemini, or your approved private model endpoints.
- Access from self-hosted deployments to the licensing portal for validation.
- Firewall rules that allow clients to reach chat, sync, and health endpoints.