> ## 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 short-term capacity

Provide dedicated Bare Metal servers. Ornn manages virtualization, GPU allocation, and customer environments. Before making capacity available, agree the hardware, access, networking, and support requirements with Ornn.

Open the arrow beside **Create listing** and choose **Short-term listing**, then select a **Node**, then set your price, **Available from**, and **Available for**. Hardware and location come from that node. **Submit listing** stays at the top of the editor; the close button returns to Listings.

## Servers and access

The supplier portal opens on **Overview**, which links to these guides: enrolling short-term capacity, managing your capacity, and getting paid.

| Requirement | What you provide |
| - | - |
| Dedicated hardware | Physical servers with no other customer workloads or shared resources. |
| Operating system and access | SSH with root or unrestricted sudo, an agreed Ubuntu LTS image, and permission for Ornn to install its agent, drivers, and virtualization software. |
| Public IP | One stable public IPv4 address per physical server. |
| Firewall | Management SSH plus the customer access, application, and outbound ports agreed with Ornn. Opening port 22 alone is not enough. |
| Network | Target 10 Gbps or better per host. Confirm guaranteed bandwidth, shared uplinks, traffic limits, and egress charges. |
| Storage | Healthy local NVMe drives. Confirm usable capacity and performance, and agree which disks hold the OS and customer data. |
| GPU specifications | GPU model, count, and connectivity, including NVLink or NVSwitch where present. |

## Virtualization and isolation

| Requirement | Configuration and verification |
| - | - |
| CPU virtualization | Enable Intel VT-x or AMD SVM/AMD-V in BIOS. Ornn verifies Linux virtualization flags and access to `/dev/kvm`. |
| GPU isolation | Enable Intel VT-d or AMD IOMMU/AMD-Vi and interrupt remapping. Ornn verifies that assigned GPUs are isolated from the host and other customers. |
| PCIe settings | Enable Above 4G Decoding for GPU address space and ACS where supported for device isolation. Software ACS overrides do not prove hardware isolation. |
| SR-IOV | Enable it if the agreed setup needs virtual functions, such as sharing network adapters. It is not required for every whole-GPU passthrough setup. |
| Virtualization setup | Ornn installs and manages the virtualization software, assigns GPUs, and validates the configuration after reboot. |

Ornn validates GPU virtualization and customer isolation before the capacity is used.

## Recovery and ongoing availability

Provide a tested private management controller for remote console, power, and reinstall access, or 24/7 supplier support with an agreed response time.

Provide healthy hardware and agree acceptance tests. Ornn tests GPU workloads, customer-data cleanup, and reuse without disrupting other customers.

Agree the available capacity, maintenance notice, support contacts, replacement times, and reclaim rules. Customer launches should not require a supplier ticket.

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

## Earnings

When creating a listing for an enrolled host, enter **Price** per GPU-hour. Your entered price becomes the listing price; Ornn adds no markup on approval. Each new reservation saves your take-home rate and the fee separately. Their sum equals the listing price for a fixed-price booking, the accepted offer price for a negotiated booking, or the matched execution price for Spot. Spot trades execute at the resting order’s price, which can exceed your ask when it crosses a higher waiting bid. Later price or fee changes do not alter existing reservations. After settlement, earnings for that listing reflect your take-home amount. Existing agreed prices and recorded earnings remain unchanged.

In the [supplier portal](https://supply.ornn.com), approved organizations can open **Earnings** to see earnings and settlements for a selected period. The view starts with recent transactions. Select **Load older transactions** to add earlier records and months. Use **Month** to choose a month from the loaded activity; the current month is selected by default. The total and settlement history use UTC dates. Earnings are split into **Primary listings** and **Secondary listings**, and each settlement names its listing. The amount covers loaded transactions for the selected month and may be incomplete while more history is available. Select **Refresh** to restart from the newest transactions. Earnings appear after billing periods settle; this view does not track bank payouts.

Your earnings records are scoped to your supplier organization. They do not include renter identities, customer payment details, or other organizations’ balances.

## 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 enrolled hosts

Eligible nodes show a persistent **+** action. Hover or focus it to see **Create a short-term listing for this node**, then select it to open the listing editor with that node selected. The action appears only for your enrolled Bare Metal nodes with GPU inventory and is hidden in read-only views.

Open **Nodes** in the supplier portal. **Enroll host** opens an enrollment
panel. If your organization has custom setups, **Enrollment setup** starts on
**Standard** and lets you choose a custom setup instead. With no custom setups, create
the standard command directly. Select **Create enrollment command**, then run it as root
on your host. The command expires in 90 minutes. Changing the setup requires creating
a new command. After running it, the panel shows progress for that command’s newest enrollment, including failed-step logs or a completion message. While the host has not connected, it shows a waiting message. The **Enrollment history** icon in the drawer header opens the history page. Open **Enrollment history** from the Nodes header to see a table of hosts, statuses, start times, and progress, newest first. Search enrollment runs by host address, run ID, or status, and use **Status** to select one or more states. Search and status filters work together. Clear the search or filter to show all matching runs. Choose **View details** to expand a run’s setup steps and logs. Use **Refresh** to check for updates and the **Nodes** breadcrumb to return. Runs remain visible until their enrollment token expires. Select a host to inspect telemetry
and its VMs in a side panel. Expand a Customer VMs row to see a six-hour history of GPU, CPU, and memory metrics. Hover over a chart or focus it and use the arrow keys to inspect readings. Missing telemetry does not indicate an idle host.

To offer an enrolled node, open the arrow beside **Listings → Create listing**, choose **Short-term listing**, then select a **Node**. Type in the dropdown’s search field to narrow the host list. Select an on-grid node with GPU inventory, set your rate and availability, and submit it for review. Both short-term and long-term submissions appear in **Listings**; **Nodes** is for hardware enrollment and management.
Open **Developers** from the bottom of the sidebar for API keys and documentation. Search the top bar by page or task, such as **API keys**, **enroll a host**, or **pending listings**. Search tolerates common typos and opens matching pages, forms, or listing filters. Use the arrow keys to choose a result, Enter to open it, and Escape to close search. Search covers portal pages and actions, not individual host or listing records. Use the top bar to get help. Create a listing from **Listings → Create listing**. The account menu opens **My profile**, **Organization**, **Notifications**, and **Team & invitations** inside the supplier portal. Update your name and job title, your organization’s website, industry, and address, or its shared email preferences. Email and organization name are read-only. In **Team & invitations**, invite a teammate by email, review pending invitations, revoke invitations, or remove another member after confirmation. All organization members have equal access. **Log out** ends your session.

The supplier workspace opens on **Overview**, which links to the supplier documentation and guides for enrolling short-term capacity, managing your capacity, and getting paid. Use **Nodes** to enroll hosts and monitor their health, and **Listings** to manage your capacity offers.
Use **Developers** for API keys and integration guidance.

The portal sidebar can be resized or collapsed to icons. On smaller screens, use **Open navigation** to switch between Overview, capacity, listings, and developer tools. Details open alongside the current page.

## Get help

Select **Help** in the supplier portal to contact support or open relevant guides. Approved organizations can select **Contact support**, enter a subject and message, and select **Send request**. The form shows the page context included with your request. **Email support** is available as an alternative, including while your organization awaits approval.


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