GPUs and depreciating assets

Compute hardware — GPUs, and the servers and racks built around them — is priced differently from the rest of Barkr’s asset classes. It depreciates on a predictable curve, quickly, and a single figure for a multi-year term would be wrong for almost all of it.

So these assets are priced per year of the contract, against a depreciation schedule, and several rules follow from that.

What changes

	Most asset classes	Depreciating hardware
Contract term	Up to 12 months	Up to 5 years
Pricing	One valuation for the term	A figure for each year
Valuation type	Standard	Depreciation — set automatically
Payment	Pay in Full, Quarterly or Monthly	As usual, except server-level pricing

Submitting them

Nothing special is required of you. Select the relevant asset type on the submission form and the portal sets the valuation type to depreciation itself — it is the only way these assets can be priced, so there is no choice to make.

What does matter is the detail you supply. Depreciation is modelled per unit, so the parsing step needs to establish exactly what you hold:

• Exact model designations. Generation and variant both move the curve.
• Unit counts, not line counts. A row reading “8× H100” is eight units, and the valuation is built on the eight.
• Purchase or commissioning dates. Depreciation runs from a date, and guessing it is the largest avoidable error in this asset class.
• Configuration, where units are racked or clustered — see server-level pricing below.

Reading a multi-year valuation

The valuation table shows a figure for each year of the term rather than one number. Read it as the schedule it is: what the collateral is worth in year one is not what it is worth in year three, and the contract reflects that.

Totals shown against a depreciation-derived asset list are full-term figures — the whole contract, not one year of it. Check which you are looking at before comparing against a loan balance.

Server-level pricing

Where hardware is valued at the rack or server-system level rather than per card, two things follow:

• The valuation covers the system as a unit.
• Payment must be Pay in Full. Server-level pricing is collected upfront, so the portal locks the payment plan rather than offering monthly or quarterly.

The portal states this on the acceptance form: Server-level pricing is collected upfront, so it must be paid in full.

Amending one of these contracts

Adding depreciating assets to a live contract re-runs the depreciation schedule. That can change the per-year figures, not just the totals — so review the whole schedule when the amendment pricing comes back, rather than only the new lines.

The mechanics are the same as any amendment. See Adding or removing assets.

Choosing a term

Match the loan, as always. The longer terms exist because compute lending often runs multi-year, not because a longer term is better — and the further out the schedule runs, the more of the valuation rests on projected depreciation rather than observed market data.

If you are unsure which term suits a particular facility, ask before accepting. See Contacting support.