Skip to main content
Reserving compute on Ornn means selecting a GPU deployment, choosing a date range, picking how many GPUs you need, and submitting a bid price per GPU-hour. Checkout creates the bid in Pending deposit and takes you in to pay the down-payment that backs your order; the bid moves into review once that down-payment settles.

​
Where you start

There are two entry points:
  • Reserve is the primary reservation surface. It lists deployments grouped by availability and routes you to the deployment-scoped reservation form.
  • Marketplace is geared toward browsing inventory. Listings on the marketplace can lead you straight to Checkout. See Browsing the GPU compute marketplace.

​
The reservation flow

1

Open Reserve and pick a deployment

Open Reserve. The page groups deployments under three tabs:
  • All GPU: every deployment, current and upcoming.
  • Available: deployments open for reservation now.
  • Upcoming: deployments opening soon.
Each card shows GPU model, quantity, operator, site/region, and an availability or countdown indicator. Use the filter bar to narrow by GPU model, Location, Operator, or Quantity.Click Reserve on a deployment row to open its reservation form at /reserve/[deploymentId]. Clicking the row itself opens the deployment detail panel.
2

Pick your date range on the calendar

The reservation form shows a calendar for the selected deployment. Today the calendar uses month/year block selection: pick the months that cover your desired term rather than individual days or weeks.The legend color-codes each month cell:
  • Available: open for reservation.
  • Selected: the months you have picked for your term.
  • Booked: already reserved.
Months outside the deployment’s availability window render as Not Available and cannot be selected. Use the calendar navigation controls to move between months.
3

Set your GPU count

Use the GPU count selector to set both your requested GPUs and Min. acceptable GPUs (the slider’s aria-label is “Minimum acceptable GPUs”): the smallest count you’d accept if the full quantity isn’t available. The web form requires this value. To require the full count, set the minimum equal to your requested count.
4

Enter a bid price

Enter your bid price per GPU-hour in USD. The bid summary alongside the deployment shows the buy-now price per GPU-hour. That price is the ceiling on your bid: you can bid up to it, but not above it.
5

Submit and continue to checkout

Review the order summary (total GPU-hours, estimated cost) and submit. The submit action takes you into checkout, where Ornn captures your billing details and generates a Stripe-hosted down-payment invoice payable by card or ACH.
Checkout creates the bid right away in Pending deposit. It’s visible and editable in Portfolio → Bids, but it doesn’t enter the review queue until the down-payment settles, at which point it becomes Active. See Completing checkout.

​
After submission: the lifecycle

StageWhat it means
Pending depositCheckout has created the bid. Settle the Stripe-hosted down-payment invoice to move forward.
ActiveDown-payment settled. The Ornn team reviews the bid.
AcceptedThe Ornn team accepted your bid. The accepted GPU count and price are locked in.
Reservation createdThe accepted bid was promoted to a confirmed reservation in your portfolio. From here you manage the reservation, not the bid.
Once the reservation exists, it carries its own status in your portfolio: it shows Active when the term has started (configure VM or Bare Metal on the reservation detail page to connect) and Completed when the term ends. You can edit or withdraw the bid while it is Pending deposit or Active, before it’s accepted. See Managing your bids for details. See How bid-based pricing works for the full lifecycle, including rejected, withdrawn, and expired states.

​
Reserve from the CLI

The Ornn Compute CLI mirrors the web flow once you’ve signed in with ornn login. Submit a bid for a listing: 
ornn bid create <listing-id> \
  --gpu-count 8 \
  --min-gpu-count 4 \
  --start-date 2026-06-01 \
  --end-date 2026-07-01 \
  --price 2.75
Add --no-open to skip the browser confirmation, or --json to capture the created bid plus the browser handoff fields (bid, opened, url). For a fixed-price listing, ornn buy jumps straight into the checkout flow for that listing: 
ornn buy <listing-id>
See the Ornn Compute CLI for the full command reference.

​
What’s next

checkout

Completing checkout

Pay the down-payment that moves your order into review.
bidding

How bid-based pricing works

See the full bid lifecycle, including update and withdraw.