A clause to understand before a payment is ever late: when a host can hold hardware, what that requires, and how to keep it narrow.
Most fleet owners never read the lien clause closely, because on the day they sign, nothing is late and nothing is wrong. The clause only starts to matter on the day something is wrong, which is exactly the day you do not want to be reading it for the first time.
What the clause is for
A lien, in a hosting agreement, is the right for the operator to hold your hardware, or to refuse to release it, until a specific obligation is met. It is a collections tool, not a punishment. The obligation is usually unpaid invoices, and occasionally costs the operator has incurred on your behalf, such as removing and storing machines you did not collect within a stated window. A lien clause that is scoped to those two things is doing what a lien is meant to do. A clause that lets the operator hold your hardware for any breach of the contract, including ones that have nothing to do with money owed, is doing something broader, and that breadth should be noticed before you sign rather than after.
What should happen before a hold, not after
A well-drafted lien clause does not let the operator move straight from an unpaid invoice to holding the fleet. There is usually a sequence: a missed payment, a notice that the payment is overdue, a further period in which the customer can cure it, and only then a right to hold. Ask where each of those steps sits in your draft, and specifically whether the notice has to reach a named person rather than an inbox nobody checks. A contract that skips straight from due date to hold, with no notice and no cure period in between, is giving the operator a much faster trigger than the industry norm, and that is a fair thing to ask to have changed.
The form of the notice matters too. Does the contract say how it must be sent, and does it require the operator to state the amount owed and the specific invoices it relates to? A notice that just says the account is in arrears, without naming the figure, is harder for you to check against your own records and harder to resolve quickly.
Proportionality: what gets held, and against how much
The strongest version of this clause ties the value held to the value owed. If you owe a modest sum on one invoice, a lien over your entire fleet is a disproportionate response, and some contracts limit the hold to hardware whose value reasonably corresponds to the debt, or require the operator to release equipment once the outstanding balance is paid down to a level the remaining hold covers. Weaker drafts simply say the operator may hold "the hardware" without saying which part, which in practice means all of it, regardless of how small the arrears are relative to the fleet's value.
Check, too, whether the lien clause caps what can accrue while hardware is held. Storage or holding fees that keep compounding for as long as the dispute runs unresolved can turn a small original arrears into a much larger figure by the time it is settled, and a clause that caps those fees, or requires them to be reasonable and itemised, is doing you a favour that an open-ended one is not.
How this sits next to deposits and prepayment
A lien is not the same instrument as a deposit, and the two should not be read as substitutes for each other. A deposit is collateral the operator already holds and can draw on directly; a lien is a right to withhold something you still own until you pay what is owed. If your contract has both, ask how they interact: does the operator draw the deposit first and only move to a lien if that is insufficient, or can either be used at the operator's discretion regardless of order? We go through deposits and prepayment in more detail in deposits and prepayment, including the point that a security instrument is only useful to you if its trigger and its limits are written down rather than assumed.
The broader contract context matters as well. A lien clause sitting inside an otherwise carefully scoped agreement (one that defines capacity, pricing and termination clearly) is a different proposition from the same clause sitting inside a vague one. If the rest of the document is loose about definitions, the lien clause is unlikely to be the exception. Our hosting agreement guide walks through the document section by section, including the liability and collateral language that usually sits near the lien clause itself.
What to ask before you sign
Before you sign, find the lien clause and read it against these questions. If the draft in front of you does not answer one of them, raise it with whoever sent it rather than assuming the answer favours you.
- What specific obligations can trigger a hold: unpaid invoices only, or any breach of the contract?
- What notice is required before the hold starts, and how much time do you have to cure the missed payment first?
- Is the value held proportionate to the amount owed, or can the entire fleet be held against a small arrears?
- Do holding or storage fees accrue while hardware is held, and are they capped or itemised?
- How does the lien clause interact with any deposit the operator already holds?
A narrow, well-sequenced lien clause is not a red flag on its own; most serious hosts have one, because unpaid invoices are a real risk they have to manage somehow. What deserves attention is a clause with no sequence, no proportionality and no cap, because that is the version that turns a routine collections tool into open-ended leverage over your hardware.
Our own terms are set out in the service agreement, which comes with a quote from our hosting rate page. Reading it alongside any other draft you hold is a reasonable way to see where the two differ.
