Pick a GPU class, a node count and a horizon. The planner prices it at every known neocloud, builds the owned-hardware case with hosting and depreciation, and runs the buy gate from the Compute Management Policy.
One row per line of compute. Rows can overlap: a rendering node runs alongside the training nodes. Start is the month the row begins; a new row starts when the previous one ends. In Compare, mark rows Rent or Own to build a mixed plan.
| Name | GPU | Nodes | Start | Months | Util % | Sourcing | Vendor | $/GPU-h |
|---|
Policy default is rent. Buy only when every line of the gate passes in writing, with CEO approval.
| GPU | USD / node | kW / node |
|---|
Policy section 5.1. All lines must pass, in writing, with CEO approval. Owned nodes are depreciated over 3 years and hosting is charged to the same envelopes.
Per row, then run rates. Effective cost divides what is paid by what is used, the policy's unit metric.
| Period | GPU | Nodes | Start | Months | Util | GPU-h used | Rent | Own: burst rent | Plan | Plan cost |
|---|
Vendor list from "Romoya Compute Planning - Vendors"; list prices re-checked on each vendor site on Oct 7, 2026. Click a row to price the scenario there. Edit a price to override it; overrides persist in this browser.
| Vendor | Region | Fabric | Status · commitment terms | Other GPUs, $/GPU-h | $/GPU-h on-demand | $/GPU-h reserved | Node-month | Horizon |
|---|