Where you start
Listings (/reserve) is the reservation surface. It lists deployments grouped by availability and routes you to the deployment-scoped reservation form.
The reservation flow
1
Open Inventory and pick a deployment
Open Inventory (the
/reserve route). The page groups deployments under three tabs:- All: every deployment, current and upcoming.
- Available now: deployments open for reservation now.
- Upcoming: deployments opening soon.
/reserve/[deploymentId]. Clicking the row itself opens the deployment detail panel. (The sidebar label is Inventory, but the route path is /reserve.)2
Pick your reservation window
Set the Coverage Length using the start and end fields in the reservation rail. Each end of the window has a date input (
MM/DD/YYYY) and a time input, and both are captured as explicit UTC instants — the quote is priced against those exact instants, so the total you see in the summary equals what commerce bills for the term. If the listing’s availability window has already started, the start renders as Now rather than the past availability date.Because the window is instant-based rather than whole-day, you can book same-day partial-day terms (for example, a single afternoon) and the quote reflects only the hours you selected. A one-day window is priced as 24 GPU-hours — the previous inclusive +1 day that doubled short windows has been removed.Date filters on the reserve list use the same formatter, so the chip labels match what the form accepts. Changing the window refetches inventory against it — the previous rows stay on screen while the new results load.3
Set your node count
Use the slider to pick how many nodes you want. The slider is node-denominated — it steps in whole nodes, not individual GPUs — because Ornn sells GPUs in whole nodes. For a deployment of 8-GPU nodes, valid requested counts are 1, 2, 3 nodes (8, 16, 24 GPUs), and so on. Checkout rejects a partial-node requested count with a
400.In Bid mode, when more than one node is available, the form collects a Min and Max node range: your maximum is what you’d like to reserve, and the minimum is the smallest count you’d still accept. The Ornn team can then fill any whole-node count within your range when accepting. When the listing has a fixed quantity (a single option), no range is offered and the bid is all-or-nothing for that count.The reserve list only shows deployments with GPUs available for your selected date range. Sold-out listings, empty listings, and listings whose availability window doesn’t overlap your date range are omitted. If a listing you expected doesn’t appear, widen the date range or clear filters.4
Pick Buy now or Bid
Toggle Buy now to reserve at the listing’s published rate, or Bid to enter your own price per GPU-hour. Switching modes doesn’t shift the summary — the price slot holds a fixed height for both.Enter your bid price per GPU-hour in USD. The Rate placeholder shows the deployment’s buy-now price as a reference — you can bid below, at, or above it. Every bid lands as Pending deposit, advances to Active (immediately, or after the required down payment settles), and waits on Ornn team review, so bidding above buy-now does not auto-convert into a reservation. If you want the listing at its published rate with no review step, pick Buy now instead. If the listing publishes a floor, the reserve form blocks a bid below it before submission and names the minimum acceptable rate. If the listing has no published buy-now price, the rate field shows a placeholder and you set the price you’re offering.If the operator has disabled either Buy now or Bid on this listing, the unavailable toggle is grayed out and you can only continue with the mode that’s enabled.
5
Submit the order
Review the order summary (total GPU-hours, estimated cost) and submit. Both modes route through the same checkout form to collect your company and billing details, then diverge at the final step:
- Buy now ends in a payment step (card or ACH) and places a 15‑minute hold on the listing’s capacity for the duration of checkout. See Completing checkout.
- Bid skips the payment step in the reserve form. The Review bid screen states that nothing is charged; clicking Bid now submits the bid and takes you to a confirmation reading “Your bid was submitted. If it is accepted, the reservation will appear in your portfolio.” No payment method is collected from the reserve form and no capacity is held. The bid lands as Pending deposit — if a down payment is required, complete it through the existing-bid checkout flow to advance the bid to Active. Track the bid in My GPUs → Bids.
After submission: the lifecycle
For a Buy now reservation, once payment settles the reservation is confirmed and appears in My GPUs. For a bid, the record moves through four states:
Once a confirmed reservation exists in My GPUs, it carries its own reservation status (distinct from the bid status): 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 a bid while it is Pending deposit or Active, before it’s accepted or rejected. See Managing your bids for details.
See How bid-based pricing works for the full bid flow.
Sharing a listing
Use the Copy link action on a listing to grab its share URL. Every share link points at/reserve/{listingId} — the same URL whether the recipient has an Ornn account or not. Legacy /listing/{listingId} URLs still work and permanently redirect to the canonical /reserve/{listingId} path.
What the recipient sees depends on their account state:
- Not signed in: a read-only listing page with the GPU model, quantity, operator, availability window, term, and price, plus a Reserve button that returns them to the same listing after login.
- Signed in, tenant pending approval: the same read-only listing page, so they can review the offer while approval is in flight.
- Signed in with an approved tenant: the reservation form for that listing, unchanged from the normal Inventory flow.
- Open Graph preview image at
/listing/{listingId}/og.png— used by Slack, iMessage, and other link unfurlers to render a rich preview card. - Spec sheet PDF at
/listing/{listingId}/spec.pdf— a downloadable one-pager summarizing the listing’s hardware and terms.
Sharing exposes only the fields visible on the public listing page. Bid history, tenant identity, and any operator-private notes are never included in the shared view, the OG image, or the PDF.
Reserve from the CLI
The Ornn Compute CLI mirrors the web flow once you’ve signed in withornn login.
Submit a bid for a listing:
ornn bid remains an alias for ornn exchange.
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:
What’s next
Completing checkout
Pay for a Buy now reservation by card or ACH.
How bid-based pricing works
See the full bid lifecycle, including update and withdraw.