The 2 a.m. reboot that costs $330

A server at your colo stops responding. You can't SSH in. The management interface won't load. You open a ticket with the facility and ask someone to walk over and power cycle it.

Somebody does. It takes them about four minutes, including the walk. You get billed for two hours because it's after midnight and the after-hours minimum is two hours.

That's the part nobody budgets for. Not the rate itself, which is public and reasonable enough, but the gap between the work performed and the work invoiced.

What remote hands actually costs in 2026

Rates vary by market, provider, and how urgently you need someone moving. Published figures across the industry land in a fairly consistent band:

Service tier	Typical hourly rate	Notes
Remote hands	$50 to $150	Basic physical tasks. Reboots, cable swaps, drive pulls, checking indicator lights.
Smart hands	$150 to $300	Certified technicians. Configuration, firmware, diagnostics, reading network diagrams.
After-hours	1.5x standard, or flat premium	Frequently carries a 2-hour minimum per incident.
Emergency, 15-min SLA	$1,500 to $3,000 per incident	Plus a monthly retainer. Premium facilities only.

Sources: published rate cards and industry pricing guides, 2025 to 2026. 

A few specifics worth knowing. One published provider policy lists $165 an hour flat, billed in 30-minute increments, with a two-hour minimum after hours. Another lists $75 an hour billed in 15-minute increments. Enterprise smart hands engagements commonly run $150 to $300 an hour for per-incident work.

The billing increment matters more than the rate. At $165 an hour with a 30-minute minimum, a four-minute reboot costs $82.50. The same reboot at 2 a.m. under a two-hour minimum costs $330.

What people actually call remote hands for

This is where the math gets interesting, because the ticket list splits cleanly into two groups.

Genuinely physical work. Swapping a failed drive, reseating a card, running a cross-connect, racking or de-racking, accepting a hardware delivery, replacing a power supply. Somebody has to be standing there. No device changes that.

Work that only needed a console. Power cycling a hung host. Reading an error message off a screen. Getting into BIOS to change a boot order after a failed update. Watching a machine POST to see where it stops. Booting from installation media. Confirming whether a box is actually on.

The second group is the one worth examining, because those tickets don't need hands. They need eyes and a keyboard. You're paying a technician $165 an hour to be your monitor.

The break-even math

Take a modest scenario. One rack, one colo, and console-type incidents that don't require physical work.

Console-only incidents per year	At $165/hr, 30-min minimum	With after-hours 2-hr minimums on half
4	$330	$825
8	$660	$1,650
12	$990	$2,475
24	$1,980	$4,950

Assumes a single incident consumes one billing increment during business hours. In practice tickets often run longer, because a technician following instructions over the phone is slower than you would be at the console yourself.

Against that, a cellular remote KVM is a one-time hardware cost plus a small monthly data line. The device sits in the rack doing nothing until you need it.

Somewhere between the third and sixth console-only incident, the hardware has paid for itself. After that the tickets are free, and more importantly they're immediate. No queue, no response SLA, no waiting three hours for someone to get to your request.

Where remote hands still wins

This isn't an argument for cancelling your remote hands agreement. A KVM cannot pick anything up.

•    Hardware replacement. Drives, memory, power supplies, fans, anything that involves opening a chassis.

•    Physical layer work. Cross-connects, patch cables, cable management, anything on the front of the rack that needs a hand.

•    Racking and de-racking, and receiving shipments.

•    Anything involving the facility itself. Power, cooling, access, escorting your own staff in.

•    First install. Somebody has to plug the KVM in too.

The right read is that remote hands and a KVM cover different halves of the same problem. Most teams are currently paying remote hands rates for both halves because that is the only tool they have.

Remote hands vs. smart hands, briefly

Worth clearing up since the terms get used interchangeably and they aren't.

Remote hands is basic physical work performed to your instructions. The technician follows a checklist. They are not expected to diagnose anything.

Smart hands is technical work requiring judgment. Configuration, firmware, reading a network diagram, actual troubleshooting. It costs roughly double.

The failure mode that costs real money: you open a remote hands ticket for something that needed smart hands, the tech does it wrong or incompletely, and you pay for a smart hands visit on top to fix it. A console session in front of the problem removes the guesswork that causes that sequence in the first place.

The part that isn't about money

Remote hands SLAs typically run one hour for standard business-hours response, two hours after hours. Some providers use best-effort language and cite three hours. Premium tiers get you to fifteen or thirty minutes and cost accordingly.

If your recovery objective is under four hours, a three-hour response to a ticket has already consumed most of your window before anyone touches the machine. A console you can reach yourself has no response time. You are looking at the screen the moment you decide to.

What to do with this

Pull your last twelve months of remote hands tickets and sort them into two piles: the ones that needed a person to physically touch something, and the ones that needed somebody to look at a screen and press keys.

If the second pile is bigger than three or four tickets, the arithmetic is already against you. If any of them were after hours, it isn't close.

Katalyst Pilot is a remote KVM with 5G built in, so it reaches you even when the site's network is the thing that failed. BIOS-level control, virtual media for reinstalls, and remote power cycling with an ATX board. It's the half of the problem that doesn't need a person.

Learn more about Pilot  →  www.katalystbrand.com/pages/pilot 

 

FAQ 

What is remote hands?

Remote hands is a service where data center staff perform basic physical tasks on your equipment on your behalf. Rebooting a server, swapping a cable, pulling a drive, reading an indicator light. The technician follows your instructions rather than diagnosing anything themselves.

What is the difference between remote hands and smart hands?

Remote hands is basic physical work performed to a checklist, typically $50 to $150 an hour. Smart hands is technical work requiring judgment, such as configuration, firmware updates, and diagnostics, and typically runs $150 to $300 an hour. Opening a remote hands ticket for work that needed smart hands often means paying for both.

How much does remote hands cost?

Rates commonly run $50 to $150 an hour for remote hands and $150 to $300 for smart hands, billed in 15 or 30-minute increments. After-hours work often carries a premium plus a two-hour minimum per incident. Emergency response tiers with a 15-minute SLA can run $1,500 to $3,000 per incident on top of a retainer.

Can a KVM replace remote hands?

Not entirely. A remote KVM handles anything that needs a console: power cycling, BIOS access, reading error screens, reinstalling an operating system. It cannot replace physical work like drive swaps, cross-connects, or racking. Most teams need both, but currently pay remote hands rates for the console work too.

How many remote hands tickets justify buying a KVM?

Roughly three to six console-only incidents a year, depending on your facility's rate and billing increment. At $165 an hour with a two-hour after-hours minimum, a handful of overnight reboots covers the hardware.

What is the typical remote hands response time?

Standard SLAs generally run one hour during business hours and two hours after hours. Some providers use best-effort language with a three-hour target. Premium tiers guarantee 15 to 30 minutes at significantly higher cost. If your recovery objective is under four hours, response time may matter more than the hourly rate.