Reserved GPU nodes
A GPU reservation gives your account whole GPU nodes of one type, in one region, for a fixed term — for example 4 nodes of 8 × RTX PRO 6000 in Atlanta for 12 months. The nodes are yours alone: nobody else's workloads run on them, and you never wait for capacity someone else is using.
Reservations are set up by EcoLink as part of an enterprise contract. There is nothing to buy in the console; once your reservation is active, the console and the API simply work against your nodes.
Pricing is agreed with each customer, depending on the terms: how many nodes, for how long, and how you pay. To ask for a quote, open a request from Support in the console (from the dashboard: Reserved nodes → Contact us) or see Contact sales.
What changes when your account has a reservation
You launch exactly as before — the same wizards, templates and API calls. The difference is where workloads run and how they are paid for:
- Everything with a GPU runs on your reserved nodes: GPU instances, GPU clusters, model instances and fine-tuning jobs. The launch wizards offer only your reserved regions and GPU types and show how many of your GPUs are free.
- No hourly charge. The price line reads Included in your reservation, and nothing is held from your credit at launch. Responses from the API carry
"billing": "reserved"for these workloads. - Your nodes are the limit. When every reserved GPU is in use, a new launch is refused with "No free GPUs in your reservation" until something stops — it does not spill onto other capacity. Add nodes through your account team.
- No spot option. Reserved capacity is never stopped for anyone else, so the Spot choice is hidden.
- Platform models are unchanged. Calls to platform models (chat, embeddings, images, audio, video) and the teacher model that generates synthetic data keep their per-token prices and are paid from your credit as usual.
Storage
Your reservation includes a quota of cloud-drive and shared-filesystem storage in its region. Inside the quota there is no daily storage charge; the storage dialogs show N of M GiB used instead of a price. A drive or filesystem that would go over the quota is refused — ask your account team for a larger quota.
Storage you already had in that region when the reservation started counts towards the quota.
The Reserved Nodes page
Compute → Reserved Nodes appears in the sidebar once your account has a reservation. For each reservation it shows:
- Status and term — start and end date, and how it is billed (monthly or quarterly). A reservation waiting for its first invoice shows Awaiting first payment, with a link to pay it (account owners).
- GPUs in use out of your reserved GPUs, and storage used out of the quota.
- A card per node, named node-1, node-2, …, with the GPUs in use and the workloads running on it (each links to its page). A node is one of:
| Node state | Meaning |
|---|---|
| Ready | Available for your workloads |
| Preparing | Being made ready for you; its GPUs become available shortly |
| Under maintenance | Being repaired or replaced; you keep the capacity on a replacement node |
- Payment schedule — account owners only: the rate, each period's amount, what the advance covers, and the status of every payment.
The node cards refresh every 30 seconds. Reservations that have ended are listed under Previous terms.
How a reservation is paid for
A reservation is billed by period — a month or a quarter — not by the hour. Each period costs your reserved GPUs × the hours in the period × your contracted rate, plus any storage included in the contract.
Your contract sets one of these ways to pay:
- By invoice, starting with a first invoice (most contracts). When your reservation is set up you receive one invoice: the advance plus the first period. Your nodes are held for you, and the reservation starts the moment that invoice is paid — the term is counted from the payment, so no days are lost while it is being paid. Until then the Reserved Nodes page shows Awaiting first payment and launches on your reserved nodes wait. After that, each period is invoiced when it starts.
- By invoice, with the advance paid up front. The advance is paid into your account's credit before the reservation starts; each period is then invoiced when it starts.
- From your credit. The advance (if any) and each period are taken from your account's credit when they start. Keep enough credit in the account for the next period — the payment schedule shows the date and amount; auto-recharge keeps it topped up.
The advance pays for the last periods of the term. Some contracts let you start using the nodes before the first invoice is paid; it is then due like any other invoice.
Invoices come from Stripe by email, to the account's billing email. Pay them any time under Billing → Invoices with the Pay button — by card, or the other payment methods the invoice offers — up to the due date in your contract. Once the reservation has started, your workloads run normally while an invoice is open.
If the first invoice is not paid by its due date plus the grace period in your contract, the reservation is cancelled and the nodes are released; the invoice is withdrawn. Ask your account team to set it up again.
Notices about upcoming and missed payments are emailed to the account owner and to the billing contact, if your account has one.
If a payment is missed
- Past due — a period could not be paid: your credit was too low when it started, or its invoice was not paid by the due date. A banner appears in the console for everyone in the account, and new launches on your reserved nodes are paused. Workloads already running keep running.
- Suspended — if the payment is still missing after the grace period in your contract (3 days unless agreed otherwise), workloads on your reserved nodes are stopped.
- Paid — as soon as the payment arrives, the reservation is active again and you can launch. Workloads that were stopped stay stopped; relaunch them (templates make this one click).
An account owner settles a past-due period from Billing → Invoices (invoiced periods) or by adding credit (periods paid from credit — the period is taken automatically within the hour). Other members see a note to contact the account owner.
End of term
You are reminded 30, 7 and 1 day before the term ends. At the end date, workloads on the reserved nodes are stopped and the nodes leave your account; your account then uses the standard pay-as-you-go GPU capacity and prices again.
Your cloud drives and shared filesystems are kept. After the term they are billed daily at the standard storage rates, like any other storage — delete what you no longer need, or renew the reservation through your account team.