Appearance
Turbo Server
Turbo Server delivers virtualized applications from your infrastructure to browsers and desktop clients. Applications run in isolated containers without local installation or elevated user privileges.
Turbo Server runs on Windows and Linux. Application hosts, which run user sessions, are Windows only.
What You'll Learn
- The four server roles and how they scale
- Where to start when planning a deployment
Server Roles
| Role | Count | Purpose |
|---|---|---|
| Controller | One active; optional passive standby | Runs the domain's background work: fleet scheduling, license management, federation, imports, and garbage collection. Hosts the admin, analytics, and release-management interfaces. |
| Hub | Zero or more | Stores and distributes content-addressed application layers. Serves the image API and peer-to-peer tracker. |
| Portal | Zero or more | End-user web interface for browsing and launching applications. |
| Application | Zero or more | Runs user sessions and streams them to browsers and clients. Windows only. |
Only one Controller is active in a domain at a time. For high availability, deploy an active-passive pair backed by external SQL Server or Azure SQL databases. Running sessions continue if the active Controller becomes unavailable.
The other three roles scale horizontally. You can co-locate all four roles on one host for evaluation or smaller deployments.
In This Section
- Setup and Deployment — Review prerequisites and plan CPU, memory, and storage for each role.
- Network and Ports — Plan public, internal, direct, and tunneled connectivity.
Earlier Releases
Turbo Server releases built on the .NET Framework platform are documented separately and are no longer updated. See the legacy platform documentation.