Linux and Windows Builds
Learn about the Linux and Windows build targets available on AppMana, when to use each, and how to configure them.
AppMana supports two server-side build targets for streaming your Unity project: Windows and Linux. Each has different capabilities, hardware access, and use cases.
Windows Builds
Windows builds run on Windows Server nodes with DirectX support. This is the default and most capable build target.
When to use Windows
- Your project uses DirectX 11, DirectX 12, or DirectX DXR (raytracing)
- You rely on Windows-only Unity plugins or native libraries
- You need NVIDIA DLSS, AMD FSR, or Intel XeSS features that require DirectX
- Your project uses HDRP with DXR ray tracing
Capabilities
- DirectX 11, DirectX 12, DirectX DXR (raytracing)
- Full GPU hardware access via NVIDIA and AMD cards
- HDRP with ray tracing support
- Windows-native plugin compatibility
Gradle task
The Windows build runs the prepareContextWindows Gradle task, which builds a StandaloneWindows64 player and packages it as a container image.
Linux Builds
Linux builds run on Linux nodes and produce a StandaloneLinux64 player using Mono or IL2CPP as the scripting backend. Linux builds use Vulkan or OpenGL for rendering.
When to use Linux
- You want lower hosting costs — Linux instances are generally cheaper
- Your project does not depend on DirectX-specific features
- You use Built-In Render Pipeline or URP (HDRP without DXR is also supported)
- You need OpenGL or Vulkan rendering
- You are targeting deployments on Linux-based cloud infrastructure
Capabilities
- Vulkan and OpenGL rendering
- Mono scripting backend (default) — faster iteration, larger binary
- IL2CPP scripting backend (optional) — better runtime performance, smaller binary
- Compatible with most cross-platform Unity plugins
Scripting backend
The default scripting backend for Linux builds is Mono. To use IL2CPP, enable it in your project's build settings in the AppMana dashboard.
Gradle task
The Linux build runs the buildProject_editor_StandaloneLinux64 Gradle task, producing a Linux container image.
Configuring builds in the dashboard
In the Builder Settings page for your project, you will find Windows Build and Linux Build checkboxes:
- Windows Build — enabled by default for new projects
- Linux Build — opt-in; produces a separate Linux image alongside (or instead of) Windows
You can enable both targets simultaneously. Each produces an independent container image that can be deployed separately.
Choosing between Linux and Windows
| Windows | Linux | |
|---|---|---|
| Rendering | DirectX 11/12/DXR | Vulkan / OpenGL |
| Ray tracing | ✓ (DXR) | — |
| HDRP | ✓ | ✓ (no DXR) |
| URP | ✓ | ✓ |
| Built-In RP | ✓ | ✓ |
| IL2CPP | ✓ | ✓ (optional) |
| Typical cost | Higher | Lower |
If you are unsure, start with Windows. Switch to or add Linux once you have verified your project renders correctly on Vulkan.
