Xur

Installation + first sign-in

Set up Xur from your phone.

Install Xur on your GPU host, then use your phone’s browser to create an account and load your first profile.

The USB installer runs on the host’s screen with a keyboard. After reboot, your phone becomes the web-manager client. The screenshots below show the real Xur interface at a phone-sized viewport, with example data.

1. Gather what you need

  • A UEFI-capable x86-64 host with a target disk of at least 64 GiB. Allow extra storage for models, games and container images; check the release notes for tested hardware.
  • A screen and keyboard connected to the host, Internet access for installation, and a USB drive of at least 16 GB.
  • A computer to write the installer USB. The download page includes Windows instructions using Rufus and links for other operating systems.
  • A phone with a browser and a Wi-Fi connection to the same local network as the host. The host can use Ethernet or Wi-Fi.

Back up first. Writing the installer erases the USB drive. Installing Xur erases the host disk you select. Xur is in early development; keep recovery media available.

2. Install on the host

  1. Download the online installer ISO and write it to USB. In Rufus, use GPT, UEFI (non CSM), FAT32 and ISO Image mode when prompted.
  2. Boot the host from the USB’s UEFI entry. Open Setup and installation, save a server name, then configure Ethernet or Wi-Fi. Use the host’s keyboard to move through the console with Up/Down and Enter.
  3. Choose Continue to disk selection. Check the disk’s identity and erase plan, then choose Yes to install. No is selected by default.
  4. Wait for installation to finish, confirm reboot and remove the USB. Saved networking, including Wi-Fi, carries over to the installed system.

Leave the installed console visible: it shows the HTTPS web-manager address and initial access code. For static networking or a USB answer file, see Network settings and answer YAML.

3. Open Xur on your phone

  1. Connect your phone to the same local network as the host. Avoid a guest Wi-Fi network that blocks access to other devices.
  2. Open your phone’s browser and enter the exact HTTPS address displayed on the console, including :8443. For example, https://192.0.2.10:8443 shows the format; use your host’s address.
  3. LAN access uses a self-signed certificate. Check that the address matches your console, then use the browser’s certificate-warning option to continue to this host. The warning’s wording depends on your browser.
  4. Enter the console’s Access code and tap Sign in.

The initial code remains usable until the administrator account is created. It is a setup credential; keep it private.

If the page will not open, check that the host has rebooted into the installed system, that both devices are on the same network, and that you included https:// and port 8443. A self-signed-certificate warning is expected on the LAN.

Phone-sized Xur sign-in page with an empty Access code field and a Sign in button.
Enter the code from the host’s console. No real access code is shown. Tap the screenshot to enlarge.

4. Create your administrator account

  1. On Create your account, enter a username or email and a password of at least eight characters.
  2. Use your phone’s password manager to suggest and save a strong password. Suggestions depend on your browser’s settings and trust in the site.
  3. Tap Create account. Use this username and password for future sign-ins.

Account creation disables the initial access code and setup-only sessions. Keep the saved password available before closing the browser. If setup fails, the page offers Download setup logs.

Phone-sized Create your account page with empty Username or email and Password fields and a Create account button.
Create the required administrator account in your phone’s browser. The fields are empty in this example.

5. Make your first profile

  1. Open Profiles and tap Create profile. You can also create a profile from Home when none exist yet.
  2. Tap Rename to give it a descriptive name, such as Gaming desk, then tap Done. Start with a single workload so you can check its setup before adding more.
  3. Choose Workstation under Workload type. Under Workstation, choose New workstation or reuse an existing one. For a new workstation, enter its name and choose an existing User or tap Add user. A named user keeps its home and game logins across profiles.
  4. Select the GPU for the workload. Each GPU belongs to one workload at a time. For multiple workstations, use distinct GPUs and users.
  5. Review the controller and USB options below the GPU selection, then tap Save profile.

The example shows one workstation and one GPU. For model workloads, follow Models and APIs; for desktop streaming and peripherals, use the workstation guide.

Xur profile editor at phone width, showing the Gaming desk profile, workstation and GPU selectors, and Save profile button.
A single-workstation profile in the real editor, reusing an example desktop. Scroll to review device options, then tap Save profile.

6. Load the profile and check it

  1. Return to Home, select your saved profile and tap Load profile. Saving a profile alone does not start it.
  2. Allow time for the first start, especially when model files or container images need downloading. Open Profiles to follow the change and review any errors.
  3. Tap More, then Monitoring to check resource use and running workloads. For a desktop, use More → Workstations to manage its identity and Moonlight pairing.

Your phone manages the host through the web interface. To stream a workstation desktop, follow Workstations and Moonlight.

For access away from home, open More → Tailscale, authorize the installed host and use its HTTPS Serve address from a client connected to your tailnet. Keep the LAN URL for local access.

Phone-sized Xur control panel with Gaming desk selected in the saved-profile picker and a Load profile button.
Select your profile on Home, then tap Load profile. This example shows the host before a profile is loaded.

Continue with Getting started for everyday navigation, files and profile switching, or Updates and recovery to keep the host current.