Colocation Pricing and Contract Structure What Buyers Should Verify Before Signing
Colocation quotes are rarely comparable at first glance. One provider prices per rack unit, another per cabinet, a third bundles power and network into a single figure that obscures what is actually being purchased. The confusion benefits the seller, not the buyer. Reboot Monkey’s pricing structure is built around a small number of verifiable commitments: prices are quoted per facility and rack size, free space and power are confirmed before a building is named, and engineer time is billed in defined increments with no hidden retainer . For procurement teams evaluating colocation agreements, understanding what to verify before signing is as important as understanding the rate itself.
Pricing Per Facility and Rack Size
Reboot Monkey does not publish a rate card. Colocation prices are quoted per facility and rack size, and they depend on the customer and the scope of the job . This is not evasiveness; it reflects the reality that a rack in Frankfurt Reboot Monkey and a rack in Cyberjaya carry different power costs, different facility fees, and different network availability. A generic price list would either overcharge low-cost markets or underprice high-cost ones. The quote a customer receives corresponds to the specific facility and rack configuration under consideration, which means the figure on the agreement is the figure the customer will actually pay for the rack they will actually occupy.
What matters for verification is the sequence. Before Reboot Monkey names a building or a date, it confirms free space and power in the facility . This step is not a formality. A quote issued against capacity that has not been verified is a quote that may not be deliverable. Customers should ask whether the quoted facility has confirmed the rack and power allocation, and whether the confirmation is documented. If the answer is vague, the quote is provisional regardless of how it is presented.
Engineer Time: Increments, Minimums, and What Counts
Colocation pricing covers space, power, and network. It does not cover the physical work of installing, maintaining, and removing equipment. That work is billed separately as engineer time. Reboot Monkey bills per hour in each market, with a one-hour minimum per dispatch and fifteen-minute increments after that . The structure is straightforward, but the minimum matters. A task that takes ten minutes still bills as one hour. For customers with frequent small tasks, the minimum can accumulate; for customers with occasional large projects, it is negligible. Procurement teams should estimate the expected volume of dispatches before signing, rather than assuming that hourly rates alone determine the total cost.
The billing structure also clarifies what is not included. There is no monthly retainer embedded in the colocation agreement. A customer who dispatches no engineers in a month pays no engineer fees that month. This differs from managed services agreements, which charge a monthly fee regardless of incident volume and typically require twelve- or twenty-four-month commitments . For enterprises with unpredictable physical support needs, the per-dispatch model removes the risk of paying for capacity that goes unused.
What the SLA Covers and What It Does Not
Reboot Monkey advertises a one-hour, around-the-clock incident response SLA, with on-site times agreed per site and a fifteen-minute premium response available where technicians are stationed on-site . The critical distinction is that the SLA covers Reboot Monkey’s engineers, not the building. If a facility’s power system fails, Reboot Monkey’s response time is irrelevant to the outage itself. What the SLA governs is how quickly a qualified engineer arrives at the customer’s rack to assess, diagnose, and act on the equipment inside it.
Customers should verify three things about the SLA before signing. First, whether the response time applies to their specific facility or only to deployed cities. Second, whether the premium fifteen-minute tier is available at their site and what the add-on cost is. Third, what constitutes the start of the response clock: the submission of a validated work order or the initial request. The difference between these definitions can be hours in practice.
Contract Scope and Exit Terms
The colocation agreement bundles four components: rack space, network connectivity including IP transit and leased IP addresses, data center hardware, and the service that delivers, installs, and supports it . For procurement teams accustomed to separate contracts for space, connectivity, and support, the single agreement simplifies vendor management but requires careful review of what happens at termination. Because Reboot Monkey does not own the facility, the hardware inside the rack belongs to the customer. The documentation trail—equipment manifests, chain-of-proof records, and serial number logs—travels with the customer rather than remaining with the provider . Customers should confirm in writing that these records will be delivered on request and that equipment removal is coordinated under the same terms as installation.
The pricing and contract structure that Reboot Monkey offers is not the cheapest on paper. It is structured around verified capacity, transparent engineer billing, and a narrowly defined SLA. For buyers who have been burned by quotes that did not survive contact with reality, or by retainer agreements that charged for capacity never used, that structure is worth more than a lower headline rate.