How you pay
Ornn has two ways to pay, used in this order where they apply:- Ornn credits: your organization’s credit balance. Proceeds from capacity you relist are added here, Ornn may also add or remove courtesy credit, and credits pay for your spot hours first.
- Saved card: charged automatically for spot hours that credits do not cover.
Save a card
In Billing, enter your card under Saved card and click Save card. Wait for the Card saved confirmation before leaving the page. Saving another card replaces the one on file. Ornn charges this card off-session; you do not confirm each charge. Spot bids need a saved card unless your Ornn credits cover them. If you bid without one, Ornn takes you to Billing to add a card, with a link back to where you were. Scheduled reservations do not automatically charge the saved card.Spot hours
Each spot hour is prepaid when it starts. Ornn credits pay first, then your saved card pays the rest. The card has a 0.50, Ornn charges $0.50 and keeps the difference as Ornn credits. When a spot VM ends partway through an hour, the unused part of the hour goes back to your Ornn credits. Startup time is not billed; failed starts return the unused prepayment as Ornn credits. If an hour cannot be paid, the spot run ends and a running VM is stopped. See How spot ends.Market purchases
Scheduled reservations do not automatically create invoices or charge your saved card. Payment arrangements are handled separately. Ending a scheduled reservation early does not automatically return unused time as Ornn credits. Spot unused-hour credits are separate and remain available.Reservations
Scheduled reservations do not automatically create invoices or charge your saved card. Payment for a reserved window is handled separately, and any existing invoices remain visible under Invoices in Billing. Ending a scheduled reservation early does not automatically return unused time as Ornn credits. Your saved card is still charged automatically for Spot hours. Starting or stopping a VM during a reserved window does not change what you pay; the window is billed whether or not you launch.Invoices in Billing
The Billing page in the sidebar is the source of truth for billing activity on your organization. It shows:- Billing overview: your open balance and paid invoice totals for this month and last month, shown separately by currency, and your available Ornn credits. Monthly totals use the invoice service period, or the payment date when there is no service period; draft and void invoices are excluded.
- Payment & invoicing: payment method information.
- Saved card: add or replace the card charged for spot hours.
- Overdue: a highlighted section that appears only when one or more open invoices are past their due date.
- Recent invoices: your latest invoices with date, kind (down payment, period invoice, or prepayment for a wire-paid Market purchase), amount, and status, plus actions to pay or download.
- History: per-reservation GPU-hours and usage cost for the part of each reservation that falls in the dates you choose, using your reserved GPU count and agreed price. Spot usage starts when the VM is ready and ends when the reservation stops; startup and cleanup time do not count, and a VM that never becomes ready has no usage. Reserved windows count whether or not you launch a VM; cancelled reservations have no usage. This is informational, not a new charge.
Invoice statuses
Overdue is not a separate status: it marks an Open invoice whose due date has passed.
Paying an invoice
Recent invoice rows show actions based on the invoice state:- Pay now: open invoices. Opens the Stripe-hosted invoice page.
- Pay overdue: open invoices past their due date.
- Download: when a PDF copy is available.
Only organization admins can pay invoices and use billing actions. Members can view the Billing page.
ornn reservations invoices --reservation-id <reservation-id>.
GPU usage
Usage for a reservation is shown on its detail page (/portfolio/[reservationId]) once telemetry from the hardware arrives. The Utilization panel reads <used>/<total> GPU hours (for example, 120/960 GPU hours), where the total comes from the GPU count and the reservation’s length. A line below shows the recent-jobs synced count and how stale the data is, for example “12 recent jobs synced · 45s stale”. From the CLI, ornn check <node-id> reports the same telemetry and logs.
Until telemetry arrives, Utilization and SLA Uptime show placeholders. Ornn does not estimate either from elapsed time.
Paying an invoice
Recent invoice rows in Billing expose actions based on the invoice state and whether the underlying URLs are available:- Pay now: shown for open invoices. Opens the Stripe-hosted invoice page.
- Pay overdue: shown for open invoices past their due date. Opens the Stripe-hosted invoice page.
- Download: shown when a PDF copy is available.
Only organization admins can pay invoices and use billing actions. Members can view the Billing page but cannot launch payment.
Read billing through the API
Read invoices, totals, usage cost, and Ornn credits from your own tooling with an API key. These endpoints are read-only. Save a card in Billing; open an invoice’shostedInvoiceUrl to pay it.
- CLI
- REST
- Python
open invoice past its dueDate is overdue. Invoices in transition between issuing and payment can report other statuses; treat values you do not recognize as processing. Usage cost from showback is informational, computed from your reserved GPU count and agreed price, and is not an invoice. Ornn credits are the negated ORNN_CREDIT balance, because the credit account is negative while credits are available. Account reads require an approved organization.
What’s next

Spot
Rent VMs with 1, 2, 4, or 8 GPUs by the hour.

Nodes
Find a reservation’s detail page and its utilization.