Skip to main content
Use the My GPUs section to track active, upcoming, and past reservations, review bids, check connection details, and monitor utilization. My GPUs (the /portfolio route) is your central view of every GPU reservation your tenant holds. Use it to track current activity, see what’s coming up, review your bids, and look back at past reservations.

My GPUs tabs

My GPUs has four tabs:
Access setup is not a My GPUs tab. You configure VM or Bare Metal from the reservation detail page itself. See Choose how to access your Ornn compute.

What each reservation row shows

Each row in Active and Upcoming displays:
  • GPU label and quantity: for example, H100 SXM · 8x.
  • Operator and site: the provider and facility where the GPUs are located.
  • Term: the start and end dates of the reservation.
Selecting a row opens the detail panel on the right side of the page with summary information for that reservation. Click View on the row to open the full detail page at /portfolio/[reservationId].

Reservation statuses

The web app uses a reservation’s underlying status, start date, and cancellation state to determine whether it appears in Active, Upcoming, or History.

Reservation detail page

The full detail page at /portfolio/[reservationId] is where you manage everything tied to a single reservation: configure access, review connection details, and monitor utilization. Confirmed and active reservations also show a Sublet capacity button in the page header that lists the reservation on the resale market. See Resell reservations on the secondary market.

Access setup

Access mode (VM or Bare Metal), SSH key attachment, and launch/relaunch live on this page. The legacy /portfolio/access URL redirects here. See Choose how to access your Ornn compute for prerequisites and the full flow.

Connection details

Once access is launched, the detail page shows:
  • SSH access: the SSH Host, User, and Port fields for connecting to your allocated machines.
  • Quick Connect: a ready-to-run SSH command you can copy to your clipboard.

Utilization, Spend, and SLA Uptime

The detail page’s Utilization and SLA Uptime panels render a placeholder until real telemetry has been received; Ornn no longer estimates either on the client from elapsed wall-clock time. Spend follows the commerce contract: for a booking with explicit start/end instants it accrues from the wall-clock term (clamped at cancelled_at for cancelled reservations), so a reservation that has started shows a live figure before any telemetry reports; otherwise it shows a dash until telemetry or an admin override lands. Spend accrues directly from the commerce contract for reservations with timestamped start and end times: hours elapsed between the contract start and the earlier of now or the contract end, multiplied by GPU count and the contract’s per-GPU-hour rate. This follows Commerce’s accrued-cost calculation; it is an estimate of cost accrued so far and may be lower than a checkout or down-payment invoice that reflects the full contract amount. If a reservation is cancelled, Spend stops accruing at the cancellation time rather than running through the original end date. Admin-provided Spend overrides, when present, remain authoritative and replace the accrued value. The Total commitment figure below the Spend value is the full contract cost across the entire term (GPU count × rate × exclusive term hours). It stays visible even before telemetry lands. A pending_payment reservation shows a placeholder in the Spend value slot and moves the commitment to the subtext, consistent with the other unmeasured statistics.
The reservation detail page reads GPU quantity, per-GPU-hour rate, and term from the commerce contract. If you booked, for example, 16× B200 at $7/GPU-hr for a one-week term, the detail page shows those exact numbers rather than any internal deploy defaults on the underlying compute rows.
When telemetry starts flowing, the Utilization panel reads <used>/<total> GPU hours (for example, 120/960 GPU hours), with the total derived from GPU count and term length. A secondary line below the value shows the recent-jobs synced count and a staleness figure.
For a deeper breakdown of usage data and invoices, see Track GPU usage and invoices.

CLI equivalents

Inspect reservations from the Ornn Compute CLI:
--open launches the reservation detail page in your browser. See the Ornn Compute CLI for full syntax.

What’s next

managing-bids

View and manage your bids

Track submitted bids and manage editable offers from the Bids tab.
access

Choose your access mode

Configure VM or Bare Metal access from the reservation detail page.