Knowledge centre

Choose a hosting operating system and supported image

Match Linux, Windows, storage and GPU images to the exact OmbraHost plan, application compatibility, maintenance lifecycle and licence requirements.

3 min readEnglish

Content revised · English

At a glance
Guide type
Operate & secure
Examples
Illustrative, environment-specific
Integration scope
No remote machine connected
01

Let application support narrow the choice

Start with the software’s supported distributions, CPU/GPU requirements and package versions. Compare the actual image list on the selected plan. The newest release number is not always the best choice for an application that depends on a particular supported runtime.

02

Read the image list for the selected product

The Umbra VPS range lists Ubuntu, Debian, AlmaLinux, Rocky, Fedora and Whonix. Dusk RDP lists Windows images. Vault storage lists Ubuntu, Debian, AlmaLinux and TrueNAS. GPU images are tier-specific: Spectre 4090 lists Ubuntu 22.04 + CUDA 12, Debian + CUDA 12 and Custom; the A6000 and H100 list Ubuntu 22.04 + CUDA 12 and Custom. A family name does not identify an exact release or guarantee that every application is supported.

03

Use the distribution’s maintenance model

Ubuntu LTS and Debian are familiar choices for long-lived Linux services; AlmaLinux and Rocky Linux suit software expecting an Enterprise Linux environment. Fedora has a different update cadence. These families still require patching, repository trust and an upgrade plan.

Choose a maintenance approach
FamilyUseful questionResponsibility
Ubuntu LTS / DebianDoes the application support this release?Patch packages and plan release upgrades
AlmaLinux / Rocky LinuxDoes the vendor target Enterprise Linux?Check repository and panel compatibility
FedoraCan the project keep pace with releases?Budget for the release cadence
WindowsIs the image and licence included?Patch, secure RDP and verify session rights
Privacy-focused imageDoes its architecture fit this service?Read the project model and maintain both components
04

Treat specialised images as architecture choices

A privacy-focused image such as Whonix has a specific design and resource requirements. It is not a general guarantee that every server process is anonymous. GPU software requires a compatible driver, CUDA stack and framework, while a control panel can impose its own operating-system restrictions.

05

Check what a custom image would require

A custom ISO needs an agreed import format, console access, networking and licensing. Availability on one product does not imply availability everywhere. The local configurator only records a listed image; it does not upload or boot an ISO.

06

Record the choice before you deploy

Keep a brief note of the selected release, application version, update policy and recovery procedure. A future rebuild should use an independently tested backup, not an assumption that the image includes the application’s data.

BEFORE THE NEXT STEP

Leave with a verifiable result.

  • Let application support narrow the choice.
  • Record the choice before you deploy.
  • Keep recovery information and secrets outside public files.
A LITTLE MORE CONTEXT

Questions, answered.

Can I select Windows on an Umbra VPS?

The prepared Umbra VPS selector lists Linux-oriented images only. Windows images belong to Dusk RDP and some dedicated configurations. Use the exact product's image list and validate licence eligibility before launch.

Which Linux release should I use?

Choose a release supported by the application and distribution, with sufficient maintenance coverage for the intended term. Confirm the exact image version and package coverage. The catalogue's generic Ubuntu or Debian label does not by itself specify a release.

Does Custom mean I can boot any ISO immediately?

No. Custom is a prepared request that requires image format, driver, console, network and licensing checks. The local configurator records listed choices; it neither uploads nor boots an ISO.

GO TO THE PRIMARY SOURCEUbuntu · release and security maintenance modelDebian · releases and lifecycle