Liquid capacity lending terms — v1

Agreement revision: liquid-v1. These program terms apply when an organization owner or admin chooses Yes for Liquid capacity and accepts the terms displayed in the console.

Permission and control

You authorize Nodus to run compatible customers’ interruptible Jobs on qualified idle hosts in the selected Pool. Pool-wide permission covers current and future enrolled hosts. A recorded host-specific agreement covers only its listed hosts. Enrollment by itself grants no lending permission.

Your own Nodus Jobs and Workspaces targeting the Pool have priority. Choose No to stop new loans and reclaim borrowed hosts. The accepted stop notice is up to 30 seconds, followed by verified cleanup before reuse. Offline hosts and failed cleanup can delay return. A host remains unavailable until cleanup passes; elapsed time alone does not establish that it is safe to reuse.

Pricing and the 50/50 split

The owner receives 50% of eligible settled compute charges as Nodus credits. Nodus retains the other 50%. Storage, taxes, idle time, promotional funding and unpaid charges earn no owner credits. Work availability and earnings are not guaranteed.

The agreement records the complete hardware rate card and its pricebook version. GPU hosts use the static website-derived rate for the GPU model and total physical device count, even when a Job requests fewer devices. CPU-only hosts use the lowest proportional price from the accepted website CPU configurations: each configuration price is multiplied by the larger of the host-to-configuration CPU and usable-memory ratios, then the lowest result is used. Usable RAM excludes the host reserve and the separate scratch allocation. There is no separate GPU-host CPU or RAM surcharge. The console shows each enrolled host’s borrower rate and owner earning rate. Prices are a static snapshot of the lowest matching prices on Nodus’s configuration and Reserved Compute pages. A reservation-based price does not impose a reservation term on a liquid loan. Unknown hardware and device counts absent from the card cannot lend under that agreement.

Each loan freezes its whole-host rate before funded execution. Compute charges accrue by occupied time, with second-based metering; the owner share is rounded down to a micro-dollar on the eligible settled total. The accepted card also prices future hosts enrolled in the Pool. A later pricebook release does not change an existing agreement or loan. To accept a newer card, turn lending off, review the new terms, then choose Yes.

Settlement and corrections

Earnings are posted after final billing and successful cleanup. They are non-cash Nodus credits usable for Nodus services, not a cash payout or a purchased-credit refund. Outstanding owner debt is repaid first. Purchased credits and unrestricted, nonexpiring liquid earnings can fund a loan; promotional credits cannot. Refunds and reversed compute charges reduce the corresponding owner earnings. If those credits were already spent, the adjustment creates an owner balance owed, recoverable from purchased credits or later liquid earnings. Promotional grants cannot repay that liquid earnings debt.

Execution and data

Hosts must pass idle-state, isolation and cleanup qualification. GPU hosts additionally require supported NVIDIA devices, drivers, isolated CUDA execution and device-reset checks. Lending is exclusive to the whole host. Hosts with failed cleanup remain unavailable. You retain control over programs you start directly on your machine; do not run competing work while it is lent.

Supported work consists of compatible single-node interruptible CPU or NVIDIA GPU Jobs with denied Job egress and memory-backed scratch. Host owners can inspect Job data. Isolation protects the host from the Job; it does not provide confidentiality from the host owner. Jobs requiring private infrastructure, credentials or persistent volumes use other eligible capacity. Nodus preserves declared, successfully published checkpoint files and outputs; it does not restore process memory or guarantee progress written after the last successful checkpoint.

Nodus may pause new lending or withhold unqualified hosts. A pause does not grant permission to reuse a host before its active work has stopped and cleanup has passed. Your accepted agreement, consent time, rate card and subsequent revocation remain recorded in your Pool’s Liquid capacity view.