> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ornn.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Supply long-term capacity

For reserved Bare Metal capacity on a long-term contract, Ornn works through four steps with you before committing. These checks confirm that the site, hardware, networking, and access can support customers for the full term.

Submit your capacity through **Listings → Create listing** (or choose **Primary listing** from its arrow menu) in the [supplier portal](https://supply.ornn.com). The editor page groups fields into sections, with labels and guidance beside inputs on larger screens. **Cancel** and **Submit for review** remain available in the bottom action bar. Use the **Listings** breadcrumb to return to Listings; unsaved changes are discarded. Your submission starts as a proposed listing, hidden from buyers while Ornn reviews it. Approval makes the same listing available; if it is rejected, you can edit and resubmit it.

Primary and Short-term have separate forms. Primary describes a whole-cluster commitment; Short-term uses enrolled capacity. Confirm the attestation again after switching listing types.

Choose an existing facility, or add a new location with a display name and optional region and zone. New locations are saved with your submission and can be reused for later offers. Enter the hardware specifications directly in the form. Your offer name, notes, requested down payment, and listing price are submitted for review. Enter **Price** per GPU-hour. For a negotiated booking, your take-home amount is calculated from the accepted offer price; the advertised listing price stays unchanged. Ornn confirms the down payment when approving the offer.

Use the **Primary** and **Secondary** tabs to browse your listings. **Primary** holds your submissions and other primary listings; **Secondary** holds your secondary and on-demand listings. The table shows the GPU type and full node/GPU capacity beneath each listing name, with separate Status, Location, Availability, Rate, and Actions columns. On smaller screens or beside an open detail panel, rows stack their fields so you can read listing details and reach actions without scrolling sideways. Availability dates use your local time zone. Open a listing in the side panel to review capacity and listing terms. Use the expand control to open the full detail page.

Filter your listings by **Status**, **GPU type**, or **Location**. Status includes the review and publication states present in your listings. Search matches listing names, references, locations, and GPU types. Use a filter’s clear control to remove it.

Select listing checkboxes to work with multiple rows. **Select all visible listings** selects the current filtered results. **Export selected** downloads those selected results as a CSV; **Clear selection** clears the selection.

## Qualification process

**1. Sign a mutual NDA**

Put a signed mutual nondisclosure agreement in place before either side shares customer
demand, site details, or hardware specifications. Ornn can send its standard agreement or
review yours. Return a countersigned copy to Ornn.

**2. Complete site diligence**

Share the power, network, and bandwidth details below. Use quantitative descriptions where
possible.

**3. Complete hardware diligence**

Provide the reserved node specifications, topology, and any available CPU nodes or high-speed
storage.

**4. Agree access and support**

Confirm public addressing, private management access, technical and commercial contacts, and
the support escalation path.

## Site diligence

| Requirement | What to share |
| - | - |
| Power redundancy | Number and capacity of utility feeds; redundancy level (N, N+1, or 2N); UPS capacity and runtime in minutes; generator capacity and on-site fuel runtime in hours; contracted IT power per rack in kW. |
| Network redundancy | On-site carriers and how many are diverse; number of physically diverse fiber entry points; redundant edge and core routing; failover handling. |
| Front-end bandwidth | Committed bandwidth per host and in aggregate in Gbps; dedicated or shared uplinks; traffic limits, burst terms, and any ingress or egress charges. |
| Layout (optional) | Floor plan or rack layout, the hall, cage, or rows containing the capacity, and cooling type. |

## Hardware diligence

| Requirement | What to share |
| - | - |
| Full specifications | Per node: GPU model, count, and memory; CPU model and core count; system RAM; local NVMe; boot drive; NICs; server vendor and model. Include the total reserved node count. A full bill of materials is preferred. |
| Network topology | Intra-node GPU connectivity, including NVLink, NVSwitch, or PCIe; back-end compute fabric, including InfiniBand or RoCEv2, throughput, topology, and oversubscription ratio; storage and front-end networks. Include a topology diagram if available and preferably a full bill of materials. Standalone nodes are fine. |
| CPU nodes | Whether CPU-only nodes are available for head nodes or control planes, with their count and specifications. |
| High-speed storage | Availability, provider and filesystem, usable capacity, throughput and IOPS, operator, and pricing. |

## Access expectations

| Requirement | What to agree |
| - | - |
| Public IP | Ideally, one static public IPv4 address per server. |
| Out-of-band management | BMC access through IPMI or Redfish over a private management network or VPN. Remote console access is used primarily for power control and reimaging. |
| Contacts and support | Named technical and commercial contacts, a 24/7 support and escalation path, and agreed response times. |

> [!NOTE]
>
> If a requirement is a blocker, contact your Ornn contact to work through a resolution.

## Supplier agreement

[Download the supplier MSA and SLA (PDF) ↗](https://compute.ornn.com/legal/supplier-msa-sla-october-rev1.3.pdf)

October revision 1.3. Includes the Master Services Agreement, Service Level Agreement, working node standard, and appendices.

## Manage your listings

Open **Listings** in the supplier portal. Use the listing-type tabs or search
to find a listing, then select its name to open listing details.
Use **Primary** and **Secondary** to switch between your primary listings and your secondary and on-demand listings. Select a row to open its listing details. Published listings show their **Reservations** (status, capacity, period, and your rate; renters are never shown) and their **Nodes**. Expand a node to see its recent telemetry; nodes that have not reported show **No telemetry available**. Checkboxes select listings for bulk actions without opening the details.
Choose **Create listing** to enter hardware, availability, and your requested price
in one form with capacity and availability, hardware, and pricing sections. Review or revise any section before submitting. You can edit pending or rejected submissions and resubmit them
for review. Published listings remain read-only; contact Ornn to discuss changes.

Use **Edit rate** to apply one USD GPU-hour rate to selected pending or rejected requests. Confirm that their capacity and terms remain accurate before applying the change. Published listing rates cannot be edited here.

Use **Withdraw** to remove selected published listings from new bookings. Confirm the selected listings before proceeding: withdrawal ends running Spot reservations, and active non-Spot reservations prevent withdrawal. Ineligible selections are skipped, and each failed action shows its error for retry. Withdrawal preserves the listing record; it does not permanently delete it.

Status, GPU type, and Location filters support multiple selections. Search within each dropdown to find options. Listings match any selected value within a filter and must match all active filter categories. Clear a filter to include all its values.

New primary listings default to one node and one GPU per node. Use the minus/plus controls or enter quantities directly. Both commitment dates start blank; choose a start and end date before submitting. Start shortcuts set the start to 1, 3, or 12 hours from now. End shortcuts set the end to 1, 7, or 30 days after the selected start.

## Listing messages

Open a listing and use **Messages** to read its conversation or send a message about that listing. Messages remain available after publication. New messages refresh automatically while the listing is open; select **Refresh messages** to check immediately. If sending fails, your text stays in the box so you can retry.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.