Most colocation operators offer some form of remote hands or smart hands. You can also hire an independent provider to do physical work in the same facility. Both options put a person at your rack. They differ in scope, process, reporting and what happens when you run more than one site.
This guide explains the practical difference. It does not compare prices, because prices depend on the facility, the contract and the scope, and it makes no claim about any operator's service quality. Use it to decide which option fits a given situation and what to check in writing before you rely on either.
What is the difference between independent remote hands and a colocation provider's service?
The difference is who employs the engineer and who sets the rules. With the operator's service, the facility's own team works under the operator's scope, portal and contract. With an independent provider, you hire the engineer separately, set the scope and the report format yourself, and the facility treats that engineer as your authorized visitor.
Neither is better in every case. Many colocation operators describe a remote hands or smart hands service on their sites, with scope and charges defined by contract. Some split it into a basic tier and a more advanced one, and others use one name for everything. The terms for remote hands and smart hands are not standardized, so read how your operator uses them.
What do colocation operators typically offer?
Operators typically offer an on-site team that you reach through a ticket portal, a phone line or an account manager. Published service descriptions commonly list tasks such as power cycling, visual checks, cable moves, equipment receiving and simple installs, and they often say the work is subject to the operator's scope and security procedures.
Scope limits differ by operator and by contract. Some tasks are included, some are chargeable, and some are excluded. The only reliable source for your site is your own contract and service description, so read them before an incident, not during one.
- An on-site team, sometimes with round-the-clock cover.
- A ticket portal or phone route for requests.
- A defined task list, with a basic tier and an advanced tier at some operators.
- Operator rules for who may raise requests and who may touch equipment.
- Reports and photos in a format the operator chooses.
What is the operator's own service good at?
The operator's service is good at fast, routine work inside its own building. The engineers are already on site, they know the layout, and they know the access, escort and safety rules without being briefed.
- No travel and no wait for badge or escort arrangements, because the team is part of the facility.
- Familiarity with the building, the meet-me room, the risers and the loading dock.
- A straightforward route for simple tasks such as a reboot, a visual check or a like-for-like swap.
- One vendor for space, power and hands, which keeps billing and contracts simple for small footprints.
When does an independent remote hands provider fit?
An independent provider fits when your needs go beyond one operator's scope, process or building. The common triggers are listed below, and any one of them can be enough.
- You need work the operator does not cover, or covers only as a chargeable extra you would rather scope yourself.
- You run equipment in several facilities and want one process, one request template and one report format for all of them.
- You have your own work-order template and evidence standard, for example numbered steps, labeled photos and a closeout report.
- Your equipment comes from several vendors and the work needs someone who can follow your vendor-specific steps.
- You also have non-colocation sites such as branch offices and comms rooms, and want the same service there.
- You want a second source, so one operator's backlog or scope limit does not block an urgent job.
| Topic | Colocation operator's service | Independent provider |
|---|---|---|
| Where it works | That operator's facilities | Any facility, plus offices and comms rooms |
| Who sets the scope | The operator, through its contract | You, in a written scope |
| Request process | The operator's portal or phone route | Your template or the provider's, one for all sites |
| Reports and photos | The operator's format | Your evidence standard, if agreed in advance |
| Building knowledge | Strong, the team is on site | Built through site notes and repeat visits |
| Access | Part of the facility | Needs registration as your authorized visitor |
What should you check with either option?
Check the same list for both options, and get every answer in writing. A provider that answers clearly now is easier to work with when something fails at night.
- Scope list: which tasks are included, which are chargeable and which are excluded.
- Response times: what the number measures, for example time to acknowledge a ticket, time to arrive at the rack or time to complete the task.
- After hours: whether cover is on site or on call, and how it differs from business hours.
- Access and escort rules: who may be registered, how long approval takes and whether escort is required.
- Who may touch customer hardware: which tasks need your approval first and who on your side can give it.
- Photo evidence and reports: what you receive after each job, in what format and how fast.
- Parts and RMA handling: who receives parts, who stores them and who ships a failed part back.
- Liability and insurance: what the contract says in writing, not what a sales page implies.
- Billing basis: how time, tasks and minimums are counted, which the next section covers.
How are remote hands services billed?
Remote hands is usually billed in one of a few general models, and the model matters as much as the amount. Some operators publish the structure in their service descriptions. Rates and increments vary by facility and contract, so ask for yours in writing. The article on remote hands pricing explains the cost drivers in more detail.
- Per request: each ticket or task is billed on its own, often by time in set increments.
- Block of hours: you buy hours in advance and draw them down, and you should check what happens to unused hours.
- Monthly allowance: a set amount of support is included with the space or plan, and anything above it is billed separately.
- Mixed: a basic tier is included and an advanced tier is billed, or the reverse.
How do you decide between the two?
Decide by situation, not by habit. Start with the operator's service for simple tasks it covers, and add an independent provider where scope, consistency or coverage falls short. Many teams use both.
| Situation | Operator service fits | Independent fits | Ask |
|---|---|---|---|
| Reboot or visual check at your only site | Yes, the team is on site | Not needed | What does the ticket cost to open and how fast is acknowledgment? |
| Task outside the operator's scope | Only if the contract allows it | Yes, scoped by you | Can the engineer be registered, and who approves work? |
| Several facilities, several operators | Each differs in process and report | Yes, one process for all | Can you use one request template and report format? |
| Strict evidence standard | If the operator can meet it | Yes, agreed in advance | What photos, notes and closeout record come back? |
| Branch office or comms room | Not applicable | Yes | How do you reach local engineers there? |
| Urgent job and the operator is backlogged | May be slower | Yes, as a second source | Is the engineer already registered with the facility? |
How does Deploris work alongside a colocation operator?
Deploris provides independent remote hands and smart hands. We scope each engagement in writing, agree access and authorization before the first job, and return photos and a closeout record for every request. We do not claim any relationship with a particular operator, and we follow each facility's access and escort rules.
If the operator's own service covers a task well, use it. If you need the work done to your scope and your evidence standard, or across several sites, that is where an independent provider fits.
Key takeaways
- The operator's service is strong for simple, routine tasks inside its own building, because the team is already on site.
- An independent provider fits when you need work outside the operator's scope, one process across several sites, or your own evidence standard.
- Scope, response times, access rules and liability differ by operator and contract, so check yours in writing.
- Compare billing models, not just amounts: per request, block of hours or monthly allowance.
- Many teams use the operator for routine tasks and an independent provider for everything else.