Skip to main content
Track submitted bids from the My GPUs Bids page, view bid details and lifecycle status, update or withdraw editable bids, and understand what happens after acceptance. Every bid you submit through the reservation flow is tracked under My GPUs. The Bids page gives you a full view of submitted and in-flight offers so you can monitor their progress, update them while they’re still editable, or withdraw them before they’re reviewed.

​
The Bids list

Open My GPUs → Bids to see all bids your tenant has submitted. Each row shows:
  • GPU label and quantity: the GPU model and node count you bid on.
  • Operator and site: the provider and facility associated with the inventory.
  • Term: the start and end dates you requested.
Selecting a row previews the bid in the right-hand panel, where the current lifecycle status appears as a chip and as a State field (see below). The row’s View link and the panel’s View full bid link both open the full bid detail page.
If you have no bids yet, the page shows an empty state with a Reserve now link. Browse inventory to submit a new bid.

​
Bid lifecycle and statuses

Bids move through a defined lifecycle. The web app and CLI both surface the underlying status value. The web UI renders underscores as spaces and capitalizes the first letter.
Submitting a bid from the reserve form does not take payment or hold capacity. Some bids require a down payment through the existing-bid checkout flow at /checkout?bid=<bid-id> before they advance from Pending deposit to Active and become reviewable. Acceptance itself is a status change only — Ornn does not automatically charge the remaining balance or create a reservation. A confirmed reservation is created separately, after you sign the reservation agreement following acceptance.

​
Bid detail page

Click View on a bid row to open the bid detail page. It shows the full record:
​
number
The price per GPU-hour you offered, in USD.
​
integer
The number of nodes you requested in the bid.
​
integer
The minimum node count from your Min/Max bid range — the smallest count you’d still accept. The Ornn team can fill any whole-node count between min_node_count and node_count when accepting. Older bids may carry null or a value equal to node_count (all-or-nothing).
​
date
The requested start date for the reservation term.
​
date
The requested end date for the reservation term.
​
string
The current lifecycle status (pending_deposit, active, accepted, or rejected).
​
datetime
When the bid was accepted. null if it has not been accepted.
​
integer
The node count locked in at acceptance. This falls within your Min/Max bid range (between min_node_count and node_count). null if not yet accepted.

​
Updating a bid

You can update a bid while it is Pending deposit or Active (that is, before it’s accepted or rejected).
1

Open the bid detail page

Open My GPUs → Bids and click View on the bid you want to change.
2

Edit the bid terms

Update the node count, start date, end date, or price per GPU-hour.
3

Save your changes

Submit the form. All bid fields are saved together; partial updates aren’t supported.

​
Withdrawing a bid

To withdraw an editable bid, open the bid detail page and click Withdraw bid. The bid is removed from the review queue; withdrawn bids cannot be reopened.
Update and withdraw are only available while the bid is Pending deposit or Active. Once it’s Accepted or Rejected, no further changes are possible.

​
What happens after acceptance

When the Ornn team accepts a bid:
  1. The status changes to Accepted and accepted_at and accepted_node_count are recorded.
  2. Acceptance does not by itself charge you, create an invoice, or consume the listing’s capacity.
  3. The Ornn team follows up to sign the reservation agreement. Once the agreement is in place, a confirmed reservation is created and appears in My GPUs under the Active or Upcoming view, with details at /portfolio/[reservationId], where you can configure access.
Bids submitted from the current reserve form carry a Min/Max range, so accepted_node_count falls between min_node_count and node_count.

​
CLI equivalents

Every action on this page maps to an Ornn Compute CLI command:
ornn bid remains an alias for ornn exchange. Use --json on any read command for scripted workflows. See the Ornn Compute CLI for full syntax.

​
Secondary market

Ornn supports resale of confirmed reservations through a secondary market. If you hold a reservation you no longer need, you can list it for sale and recover spend on the unused portion. See Resell reservations on the secondary market for the full workflow.

​
What’s next

portfolio

My GPUs overview

View your active reservations, check connection details, and monitor GPU utilization.
usage-and-billing

Track GPU usage and invoices

Understand GPU-hour utilization, recent job history, and how to find and pay your invoices.