Choose one of four paths
Orchestris Chat is the user-facing application. Orchestris Server adds shared identities, provider administration, model access through groups, usage reporting, and conversation synchronization. Choose the smallest path that provides the controls you need.
| Path | Choose it when | Data and administration |
|---|---|---|
| Chat with a direct provider | One person wants to connect Chat directly to a compatible provider or local endpoint. | Provider credentials and conversations stay in the local Chat profile. There is no server-managed group access, reporting, or cross-device server sync. |
| Community Edition | A small team wants a free, self-hosted control plane. | One organization, up to 8 organization users, one server node, and a local SQLite database. No license key or licensing-portal connection is required. |
| Managed workspace | An organization wants Orchestris to operate the workspace and server environment. | Orchestris operates the service. Available plans, accounts, and regions are shown by the current website and your order—not by a static documentation promise. |
| Private Deployment | An organization needs a licensed self-hosted environment or a dedicated managed environment. | The deployment is planned with Orchestris. Licensed self-hosted servers validate entitlements with the Orchestris licensing portal. |
- Path
- Chat with a direct provider
- Choose it when
- One person wants to connect Chat directly to a compatible provider or local endpoint.
- Data and administration
- Provider credentials and conversations stay in the local Chat profile. There is no server-managed group access, reporting, or cross-device server sync.
- Path
- Community Edition
- Choose it when
- A small team wants a free, self-hosted control plane.
- Data and administration
- One organization, up to 8 organization users, one server node, and a local SQLite database. No license key or licensing-portal connection is required.
- Path
- Managed workspace
- Choose it when
- An organization wants Orchestris to operate the workspace and server environment.
- Data and administration
- Orchestris operates the service. Available plans, accounts, and regions are shown by the current website and your order—not by a static documentation promise.
- Path
- Private Deployment
- Choose it when
- An organization needs a licensed self-hosted environment or a dedicated managed environment.
- Data and administration
- The deployment is planned with Orchestris. Licensed self-hosted servers validate entitlements with the Orchestris licensing portal.
- View current downloadsSee the artifacts and exact versions available right now.
- Compare access plansReview the plans currently offered by Orchestris.
- Start a managed workspaceContact Orchestris to confirm the current managed onboarding path.
- Explore Private DeploymentReview self-hosted and dedicated managed options.
Start with Chat and a direct provider
- 1
Install Chat
Open /download and choose an artifact that matches the platform, architecture, and minimum operating system shown there.
- 2
Add a direct provider
In Chat, open Settings → API Providers, add the provider configuration for your endpoint, and save the credential in the platform's protected credential store.
- 3
Select a model
Open the model picker and choose a model returned by the configured provider.
- 4
Understand the boundary
Direct-provider conversations are local-only. Add an Orchestris server later if you need shared administration and server synchronization.
Start with an Orchestris server
- 1
Choose who operates the server
Choose Community Edition for a free single-node small-team server, a managed workspace for an Orchestris-operated service, or Private Deployment for a planned licensed environment.
- 2
Initialize the organization
Community Edition uses a one-shot local initialization. Managed and Private Deployment onboarding follows the account or delivery workflow supplied for that environment.
- 3
Configure providers and access
An organization admin adds providers and models, creates aliases when stable names are useful, and grants models or aliases to groups.
- 4
Connect Chat
Desktop Chat users open Servers, choose Add Server, sign in, and let the client load the organizations and models allowed for that account. Hosted Chat is already bound to the server that serves it.
Know which surface you are using
| Surface | Purpose | Do not confuse it with |
|---|---|---|
| orchestris.com website and account portal | Public downloads, plan/account management, and licensed deployment records. | The administration console for a running Orchestris Server. |
| Orchestris Chat | Conversations, projects, files, search, and the model picker. | Server-wide provider, user, group, security, and operations settings. |
| Orchestris Admin | Providers, aliases, users, groups, API keys, usage, audit, operations, and server settings. | The public website account portal. |
| Hosted Chat at /app/ | The browser build packaged with a server release. | A separate Flutter development server or the Admin application. |
- Surface
- orchestris.com website and account portal
- Purpose
- Public downloads, plan/account management, and licensed deployment records.
- Do not confuse it with
- The administration console for a running Orchestris Server.
- Surface
- Orchestris Chat
- Purpose
- Conversations, projects, files, search, and the model picker.
- Do not confuse it with
- Server-wide provider, user, group, security, and operations settings.
- Surface
- Orchestris Admin
- Purpose
- Providers, aliases, users, groups, API keys, usage, audit, operations, and server settings.
- Do not confuse it with
- The public website account portal.
- Surface
- Hosted Chat at /app/
- Purpose
- The browser build packaged with a server release.
- Do not confuse it with
- A separate Flutter development server or the Admin application.