Skip to content

Reserved Compute

View Markdown

Beta: this feature may change before general availability

Reserved Compute is Beta. Sign in at Nodus Reserved Compute, choose your organization, and open Requests → Request capacity. Enter the hardware, quantity, location, network, dates and maximum hourly price. Nodus reviews the request and follows up using the contact information you provide.

You can edit or withdraw your request. Editing it requires another review. Requests and contact details are private to your organization and Nodus operators. Capacity shows reviewed offers when available; advertised quantity is subject to confirmation. Self-service capacity listing is unavailable.

Owners and admins can review a proposal under Contracts, including the exact quantity, term, total and conditions. Confirm only if those terms are correct, or decline. Confirmation requires both parties and may fail if the offer expires, changes, or the capacity is no longer available.

Confirming a proposal records agreement on terms. It does not start compute, collect payment or replace a signed contract. Nodus coordinates the final agreement, cleared funding and delivery separately. For on-demand compute, use Compute console in the header.

Nodus supplies your reserved compute. A request describes the capacity and reservation window your project needs. It is separate from submitting a command for execution on Nodus Compute.

Requirement What to specify
Hardware Accelerator type or constraints, device count, and required memory
Application Training, fine-tuning, inference serving, or another compute task
Networking and location Required interconnect, network access, and location constraints
Reservation window Start date and duration, including any scheduling flexibility
Budget Maximum hourly price and the terms you need reviewed

Is reserved capacity available immediately?

Section titled “Is reserved capacity available immediately?”

Submitting a request does not allocate hardware. Nodus reviews the requirements and follows up when suitable capacity is available. Review the configuration, quantity, price, access, and delivery terms in the proposal. Confirmation records agreement on terms; final agreement, funding, and delivery are coordinated separately.

Choose Reserved Compute when you need capacity for a planned window. Choose Jobs when you want Nodus to run a command and return logs and outputs. If you need to call a hosted model instead of arranging hardware, start with Inference (Beta).

Worked planning example: eight accelerators for two weeks

Section titled “Worked planning example: eight accelerators for two weeks”

This is a hypothetical requirements brief, not an available offer or a customer result. Suppose a planned run needs eight accelerators for a continuous 14-day training window:

Detail Example requirement
Device memory At least 80 GiB per accelerator
Quantity Eight accelerators available together
Window 14 consecutive days, with exact UTC start and end times
Network State the required interconnect and whether the job spans hosts
Storage Specify dataset size, checkpoint storage, and persistence after the window
Acceptance Confirm the configuration, access method, delivery time, and agreed validation before the run

Eight devices × 24 hours × 14 days is 2,688 device-hours of planned capacity. That arithmetic is a sizing aid, not an invoice: the proposal determines the billable unit, reservation term, price, and other charges. Eight devices with 80 GiB each do not automatically behave like one device with 640 GiB of memory; your training framework and interconnect must support the required distribution.

Submit the brief through Request capacity. If dates or hardware are flexible, include acceptable alternatives. Nodus supplies the reserved capacity under the agreed terms; submitting a request alone does not guarantee availability or begin billing.

A MarketplaceEntry records your request, including its configuration, dates, budget and review status. After signing in with nodus login, update the dates and requirements in this example and submit it with nodus apply -f request.yaml:

request.yaml
apiVersion: nodus.dev/v1
kind: MarketplaceEntry
metadata:
name: reserved-training
spec:
intent: Demand
title: Reserved training capacity
company: Example Lab
contactEmail: [email protected]
hardware: H100 SXM
quantity: 8
memoryGiB: 80
region: US East
network: 400 Gb/s InfiniBand
startsAt: "2027-01-17T00:00:00Z"
endsAt: "2027-01-18T00:00:00Z"
minimumHours: 24
rateUSDPerUnitHour: "3"
state: Open

A MarketplaceContract is an immutable proposal prepared by Nodus after reviewing the request and available capacity. It contains the parties, configuration, reservation window, price, terms and confirmation history. Read your organization’s proposals with GET /marketplace/v1/contracts; the response contains items and an optional continue cursor. Continue with the returned cursor to read another page. An empty items array means no proposals are available on that page. Use Contracts to confirm or decline as a human owner or admin; API keys cannot confirm, and contracts cannot be created or edited with nodus apply.