Appearance
Prerequisites
Review the platform, runtime, privilege, and database requirements for each Turbo Server host before installation. For capacity planning, see Sizing and Capacity.
What You'll Learn
- Which operating systems and runtimes Turbo Server requires
- What the Application role configures during installation
- Which database providers Turbo Server supports
Host Platforms
Turbo Server publishes release packages for x64 Windows and Linux hosts. The Application role runs only on Windows Server; the Controller, Hub, and Portal roles can run on either platform.
| Platform | Validated Environment | Host Requirements |
|---|---|---|
| Windows Server | Windows Server 2022. Automated installation validation covers the Controller, Hub, and Portal roles. | x64 architecture and local administrator rights for installation and service registration. |
| Linux | Ubuntu. Automated installation validation covers the Controller, Hub, and Portal roles. | x64 distribution with systemd and the getent, useradd, and chown utilities. Run the provisioner as root or through sudo. |
The validation environments identify the platforms exercised by the release workflow; they do not establish compatibility with every Windows Server version or Linux distribution. Automated Windows installation validation excludes the Application role because activating Remote Desktop Session Host restarts the host. Confirm production-platform support with Turbo Support before deployment.
Install the ASP.NET Core 10 Runtime before installing Turbo Server. On Windows, install the Hosting Bundle from the .NET 10 download page. The Windows installer checks for the x64 ASP.NET Core 10 Runtime and stops before copying files if it is missing.
The .NET SDK is not required on production hosts. Install it only on development systems that build or run Turbo Server from source.
Turbo Server does not publish a macOS release package.
Application Hosts
Application hosts run user sessions and therefore require x64 Windows Server. In addition to the common host requirements, plan for the following:
- Local administrator rights during installation
- A restart to activate the Remote Desktop Session Host feature
- Remote Desktop Services licensing appropriate for the expected user and device population
- Network connectivity to the Controller and from the gateway to the Application host, as described in Network and Ports
- Any operating-system components, hardware, drivers, and licenses required by the applications you publish
The Turbo Server provisioner installs and activates Remote Desktop Session Host when you select the Application role on Windows Server. Application-host first-run setup also installs the bundled Turbo Client and configures the local RDP and RDP proxy components. You do not need to install these components separately.
WARNING
Remote Desktop Services licensing is separate from Turbo Server licensing. Configure RDS licensing before placing an Application host into production.
Applications can add requirements beyond the Turbo Server baseline. For example, an application that performs GPU rendering requires a compatible GPU, driver, and licensing configuration supported by the application publisher. See Application Hosts for capacity-planning guidance.
Databases
Turbo Server maintains configuration, analytics, and operations databases. The provisioner creates and migrates these databases automatically.
| Provider | Use |
|---|---|
| SQLite | Default for a single-Controller deployment. The database files reside under the Turbo Server data root. SQLite cannot provide the shared database required by a Controller failover pair. |
| SQL Server or Azure SQL | External database for production deployments that require Controller high availability. |
| PostgreSQL | Supported external database provider for single-Controller deployments. |
The analytics database grows with session and usage volume. Monitor database and volume capacity, and expand them before they approach provider or edition limits. Do not delete records directly from Turbo-managed database schemas unless Turbo Support instructs you to do so.
Capacity Planning
Turbo Server does not enforce a universal CPU, memory, or disk minimum because Application and Hub requirements depend on workload. Use the conservative starting configurations in Sizing and Capacity, then validate the design with representative applications, concurrency, security agents, and monitoring tools before production rollout.