Termination read from both sides: what a minimum term protects, where the asymmetry usually sits, and what an orderly exit looks like.
Why does a hosting contract lock you in for a minimum term at all, and whose interest does that term serve? The instinct is to treat it as protection for the operator alone, a guaranteed revenue floor regardless of what happens to the market. That is only half the picture. A minimum term is also what lets an operator commit power, rack space and staff time to your fleet specifically, instead of treating the allocation as available to whoever asks first. Read it as a mutual commitment before you read it as a constraint, and the rest of the clause makes more sense.
What the minimum term protects
On the operator's side, a minimum term is how the cost of connecting and preparing a site for a specific fleet gets recovered over a known period rather than an open one. Switchgear, cabling and rack fit-out are sized to a load before that load ever arrives, and a term gives the operator a horizon to plan power procurement and staffing against. On your side, the same clause is what stops your allocation from being reassigned later to a different customer willing to pay more for the same rack space. Read the term length together with how price is set for that period, since a short term paired with an unindexed rate behaves very differently from a short term where the rate can move at will. We went through that pairing in more detail in our guide to the whole agreement, and the two clauses are best read side by side rather than on their own.
Notice periods and why the length matters
Most contracts do not simply expire at the end of the minimum term. They renew automatically onto a further period unless one side gives notice by a stated date, and the length of that notice window is where the practical risk sits. A long notice window is a different commercial position from a short one, particularly if your own downstream commitments, financing or fleet redeployment plans run on a longer timeline than the contract allows for. Ask plainly: how much notice does non-renewal require, is it counted from the end of the term or from the date the notice is given, and does either side owe the other anything if the deadline is missed? A related question is whether the notice period is the same length for both sides. An operator free to decline renewal on short notice while you are locked into a longer one is a legal but lopsided arrangement, and it is the kind of asymmetry that only becomes visible on the day you need to move.
What triggers termination for cause
Separate from the ordinary end of term, most agreements list specific grounds for either side to end the contract early. On the customer's side, that usually means non-payment beyond a stated cure period, a breach of site rules, or a safety violation. On the operator's side, it can mean a failure to deliver the energised capacity that was promised, or a sustained failure to meet an availability commitment. The clause to read closely is the cure period: does a breach trigger termination immediately, or does the party in breach get a defined window to fix it first? A contract with no cure period at all, on either side, should be flagged before you sign rather than after a dispute starts. Ask, too, whether termination for cause is treated differently (in compensation and notice) from termination for convenience, where either side simply chooses to end the relationship without alleging a breach.
What happens to the hardware and any security posted
This is the question that matters most on the day it comes up, and the one most often left vague in a draft. If the contract ends, does the operator have a right to hold your hardware against unpaid invoices, and if so, what is the process and the timeline for that hold? Ask for a specific window during which you can inspect and collect the fleet after termination, and what happens if it is not collected within that window. The same section should address any deposit or security you posted at the start of the agreement: whether it is returned in full, applied against any amount you owe, or held for a further period after the machines have already left the site. Ask the question from both directions, since a draft that describes the operator's rights over your hardware in detail and says nothing about the return of your own security has left one side of the ledger unwritten.
What to ask before you sign, and how to leave in good order
Write down a short set of questions and get them answered before a minimum-term clause goes from paper to practice:
- How much notice does non-renewal require, and is it the same length for both sides?
- What specific events trigger termination for cause, and is there a cure period?
- Does the operator hold a right over the hardware for unpaid amounts, and what is the process?
- How is a security deposit returned, and on what timeline after the machines leave?
- What does an orderly handover involve: access windows, packaging, and who arranges transport?
You do not need a dispute to ask any of these. They are ordinary operational detail, and an operator with a straightforward answer to each one will generally just give it to you in writing.
Our own notice periods and exit mechanics are set out in the service agreement, which comes with a quote from our hosting rate page. Where a specific scenario needs walking through against your own fleet, that conversation belongs before the contract is signed, not after.
