/portfolio/[reservationId]).
Available access modes
Two access modes are implemented today:Confirmed reservationset per reservation on the detail page
| VM | Bare Metal | |
|---|---|---|
| Use case | Most ML training and inference workloads | Workloads that need direct hardware control or maximum throughput |
| Performance profile | Near-bare-metal; slight virtualization overhead | No virtualization, direct physical host |
| Image options | Ornn base image (Ubuntu + CUDA + PyTorch) or an approved custom image | No image; you manage the software environment directly |
| Recommended for | Most Ornn customers | Advanced users who need full hardware control |
Need a cluster instead of a single machine? You can also launch a managed
Kubernetes or Slurm
cluster across your reserved GPU nodes from the Clusters page.
Prerequisites
Before you can configure an access mode for a reservation, the following must be true:- The bid has been promoted to a confirmed reservation, and the reservation is visible in your portfolio.
- Checkout and payment for the reservation are complete. Access cannot be launched or changed on a reservation with outstanding payment.
- Your account has at least one active SSH public key registered. Add keys from the SSH keys tab on the Account page or with
ornn ssh-keys add. See Manage SSH keys.
Configure the access mode
Open the reservation detail page
From your Portfolio (
/portfolio), click View on the reservation you want to configure. The
detail page opens at /portfolio/[reservationId]. The legacy /portfolio/access URL redirects
here.Choose VM or Bare Metal
Pick the access mode you want from the access section. VM and Bare Metal cannot run
simultaneously on the same reservation.
Add an SSH key and launch
In the SSH Keys section, click Add Key to add a key to the reservation, or confirm one
is already there. Then launch. Ornn authorizes the reservation’s active keys on the host.
The CLI’s
ornn access commands (activate, show, push-keys) cover Bare Metal only. ornn access activate <reservation-id> --ssh-key-id <key-id> performs the initial Bare Metal launch and installs the first key. VM access is configured and launched from the reservation detail page in the web app; there is no ornn access equivalent for VM.Connecting over SSH
Once the host is ready, connect with your preferred SSH client:Save the connection in ~/.ssh/config
For repeated access, add a Host entry to your local SSH config:
ssh ornn-h100.
Port forwarding
Forward a local port to a service running on the host (for example, a Jupyter server on port 8888):Copying files
Move data on and off the host withscp or rsync:
After you connect
Verify the GPUs are visible to the host:Adding more keys to a running reservation
If a teammate needs to connect to the same host, or if you want to rotate keys, push another registered key onto a launched reservation:Switching access modes
You can switch between VM and Bare Metal on the same reservation, but it tears down the current environment. To switch: open the reservation detail page, pick the other mode, make sure the reservation has an active SSH key, and launch.Data persistence
Ornn does not snapshot or back up data stored on the host. Treat the host as ephemeral within the reservation term:- Persist datasets and checkpoints to your own object storage (S3, GCS, R2, etc.) regularly.
- Save before switching access modes; switching tears the environment down.
- At the end of the reservation term, the host is released and any data on it is no longer accessible.
Troubleshooting
Permission denied (publickey)
Permission denied (publickey)
The SSH key you’re connecting with isn’t authorized on the host. Confirm the key you attached to the reservation matches the private key your SSH client is using:To push a different registered key onto the host, run
ornn access push-keys <reservation-id> --ssh-key-id <key-id>.Connection refused or timed out
Connection refused or timed out
The host may still be provisioning. Check the reservation detail page. If the SSH Host field
isn’t visible yet, wait a few minutes and retry. If the host is shown but unreachable, verify your
local network allows outbound SSH on the listed port.
Host key changed warning
Host key changed warning
If you reconnect after switching access modes or relaunching, the host key may change. Remove the old entry from
~/.ssh/known_hosts and reconnect:`nvidia-smi` shows no GPUs
`nvidia-smi` shows no GPUs
On the Ornn base image this should never happen; file a support ticket. On a custom image or Bare
Metal, confirm NVIDIA drivers are installed and loaded (
lsmod | grep nvidia) and that the kernel
matches the driver build.The access section is grayed out
The access section is grayed out
Access setup is gated on completed checkout/payment and at least one registered SSH key. Confirm both: check Account → Billing for outstanding invoices, and the SSH keys tab for at least one active key.
Learn more

VM access
Launch a managed VM with the Ornn base image or an approved custom image.

Bare Metal access
SSH directly into the GPU host for maximum performance with no virtualization overhead.

Manage SSH keys
Register the public key you’ll attach to a reservation before launch.

Completing checkout
Finish payment so access mode changes are unlocked for your reservation.

