Put every customer, cabinet, kW, connection and service in one place.
Cloud Colo connects your customer portal, operations, capacity, power, connectivity and commercial record in one place, without forcing you to replace the DCIM or systems you already trust.
WATCH THE 3-MIN OVERVIEWBuilt from 15+ years supporting customer operations inside colocation. Founder Member Programme now open to the first 10 qualifying sites.
The first 10 qualifying colocation sites get the commercial position we will not offer later.
Founder Members help shape Cloud Colo through structured feedback, roadmap input and reference value. In return, we take more of the implementation risk and give the founding site a protected commercial position.
62% BELOW PUBLISHED
Against the £15.00 published rate
£5.70 / CABINET / MONTH
Complete platform; no module tiering
36 MONTHS PROTECTED
Founder rate held through the committed term
YOUR FACILITY FIRST
We configure your suites, cabinets, customers, rate cards and service catalogue before the first proper review.
NOTHING SWITCHES OFF
Your existing systems remain live while Cloud Colo is proven alongside them.
YOU CHOOSE THE PILOT
You choose the first customers to move. Start with accounts you are comfortable using as a controlled pilot.
PAY FOR MIGRATION AFTER IT WORKS
Any agreed White Glove migration fee is only invoiced after successful acceptance and cutover.
This is an exchange, not a promotion.
The first ten sites give us direct operating input and reference value. They receive a commercial position, implementation access and roadmap influence that later customers will not receive.
Your customer should not need five systems and three inboxes to work with you.
Once a customer is live, the relationship becomes operational. They need access. Deliveries arrive. Cross connects change. Services are requested. Projects start. Cabinets expand. Power allocations matter. When that activity lives across email, tickets, spreadsheets and separate systems, the customer experience suffers and the operator loses visibility.
CX-01 · WHAT DO I HAVE
"Which cabinets are mine and what is in them?"
Their own cabinets and U positions, their assets, their circuits and their floor plan. Scoped to the sites where they hold equipment and nothing else.
CX-02 · HOW MUCH ROOM IS LEFT
"Am I close to my power limit?"
Contracted capacity against actual draw, per cabinet, with the headroom shown before they hit it rather than after.
CX-03 · CAN MY ENGINEER GET IN
"Can you approve Marek for Thursday at 7am?"
Access requests raised by the customer, approved by your team, with badge, escort requirement and vetting status carried through to the security desk.
CX-04 · HAS MY KIT ARRIVED
"Did the switches land? Are they in the cage yet?"
Deliveries booked in advance, logged at the dock, matched to the customer and visible to them without a phone call.
CX-05 · WHAT DID YOU ACTUALLY DO
"Can you confirm what the engineer did at 2am?"
Remote hands requested, scheduled and closed with a work-performed record and photo evidence attached to the ticket.
CX-06 · I NEED MORE
"Can I add a cross connect and another 16A feed?"
A service catalogue they can order from at eleven at night, routed straight into your provisioning queue.
CX-06 is the one operators underestimate. An existing customer ordering more is the cheapest revenue in colocation. No acquisition cost, no negotiation, no fit-out. A portal your customers actually log into is a sales channel that runs while your team is asleep.
See the customer operating layer in action.
Short, practical films on digital customer experience, remote hands, revenue and the systems that make colocation easier to run.
Colocation is a renewal business. Renewals are decided long before the renewal conversation.
A tenant who can see their own estate, order their own services and get their own engineer through the door on a Sunday does not spend the last quarter of their contract taking calls from your competitors. A tenant who emails your operations team four times a month to ask questions they should be able to answer themselves is already listening.
Contracts in this industry run for years. The service record you can show at renewal is built over all of them. Cloud Colo keeps that record without anyone having to remember to keep it.
WHAT IT PROTECTS
Contracted revenue you already have
WHAT IT GROWS
Orders from customers who are already in the building
WHAT IT REPLACES
A shared inbox, a spreadsheet and someone's memory
Know what every customer has, and what they may need next.
Cloud Colo connects the customer record to the infrastructure and services that matter commercially: cabinets, usable capacity, allocated kW, connectivity, projects and services. Commercial and operational teams get a shared view of the relationship rather than isolated records, and that combined view is where expansion, service and connectivity opportunities become visible.
CAP-01 · SPACE
Sites, halls, rooms, rows, cabinets and U positions. Occupied, reserved and available, with floor plans that reflect what is actually installed.
CAP-02 · POWER
Contracted draw against measured draw, per cabinet and per customer. Overage visible as it happens rather than at the end of the quarter.
CAP-03 · CONNECTIVITY
Cross connects, circuits, patch panels and ports documented end to end, from the customer cabinet to the meet-me room.
CAP-04 · IPAM
Address space allocated, assigned and tracked against the customer who holds it.
CAP-05 · NETBOX SYNC
Two-way sync on a schedule if NetBox is already your source of truth. Clashes surface as conflicts you review, not as silent overwrites.
Capacity data is only useful if the person quoting can see it. Occupancy sits next to the pipeline that fills it, so the sales answer and the engineering answer are the same answer.
Every customer interaction leaves a record.
Requests, approvals, deliveries, access activity, services, projects and changes all contribute to a permanent customer journal. That history gives management a reliable account of what was requested, what was approved, what happened and when. When the auditor arrives, or a customer asks who was standing at their cabinet on the fourteenth, the answer is a report rather than a week of reconstruction.
ACC-01 · SITE ACCESS
Requests raised by the customer or your team, approved with a named approver, carrying badge number, escort requirement, vetting status, check-in and check-out times on one timeline.
ACC-02 · DELIVERIES
Booked before they arrive, logged at the dock, matched to the customer and the cabinet, signed for, and visible to the customer without a phone call.
ACC-03 · PERMITS TO WORK
Hot work, electrical and confined space permits with validity windows and status, from pending through active to expired. No binder, no expiry dates watched by memory.
ACC-04 · THE AUDIT TRAIL
Every change on every record written automatically as the work happens. Not assembled afterwards, because evidence assembled afterwards is not evidence.
WHY THIS IS NOW A REGULATED RECORD
UK
Data centres were designated Critical National Infrastructure in 2024. The Cyber Security and Resilience Bill brings 1MW and larger facilities into scope as essential services, with statutory duties and incident reporting.
EU · NIS2
Data centres are in-scope digital infrastructure. Fines reach EUR 10m or 2% of global turnover, whichever is higher, with personal liability for senior management.
CERTIFICATION AND CONTRACT
SOC 2, ISO 27001 and PCI DSS all require controlled and logged physical access. A qualified audit finding is a notification event for every enterprise customer you hold.
Your customers are audited too. When their auditor asks for evidence of physical access controls at their colocation provider, you are the one who has to produce it. How quickly you can is a renewal factor whether or not it is ever discussed.
The operations manager's job, minus the parts nobody should be doing by hand.
Every facility has one person who knows everything. What breached, what is expiring, who is coming on site, what the engineer actually did at 3am, and what to tell the customer about it. That knowledge is expensive to hold and dangerous to lose. These are the parts of it Cloud Colo will do for them.
Every suggestion is reviewable before it goes anywhere. Nothing is sent to a customer without a person approving it. Everything stays in the record.
AI-01 · THE MONDAY BRIEF
Ask what needs attention this week and get one answer. SLAs about to breach, permits and contracts expiring, access requests pending approval, deliveries expected, healthchecks overdue. Assembled from the live record rather than from five tabs.
AI-02 · THE CUSTOMER UPDATE
Draft the update to the affected customers from what is already on the incident record. You read it, you change what you want, you send it. The version that goes out is the version attached to the ticket.
AI-03 · WHAT THE ENGINEER DID
Technicians talk. They do not write. Voice notes and rough site notes are turned into a structured work-performed record against the right ticket, the right cabinet and the right customer, so the job is documented and billable without anyone chasing anyone.
AI-04 · ASK THE FACILITY
Plain questions, straight answers. Which customers are within ten percent of contracted power. Who was in Suite 2 on the fourteenth. Which cabinets have four or more free U with power headroom in the same row. No report builder, no export to Excel.
AI-05 · THE THINGS NOBODY NOTICED
Healthcheck readings drifting outside pattern. A customer whose remote hands usage has doubled. Contracted services with no matching invoice line. Surfaced as a flag with the underlying records attached, for a person to judge.
AI-06 · THE WRITE-UP
Incident summaries, post-incident reviews and site visit reports drafted from the timeline that already exists. The half day after an incident that always gets spent on documentation, spent on something else instead.
None of this replaces your operations manager. It removes the administrative tax on being good at the job, and it means the knowledge sits in the system rather than in one head that might resign.
A customer operating layer, not another isolated tool.
Cloud Colo connects the operational systems around a facility so that the customer, the support team and the site team are working from the same record. Keep the specialist tools that already serve you well and connect their important events to the customer relationship.
ACCESS CONTROL
Connect Genetec, Paxton or Gallagher workflows to access requests, people, groups and doors. Events can be reconciled against the customer record instead of being left in a separate security console.
SERVICE DESK
Synchronise tickets and service requests with HaloITSM, Jira Service Management, ServiceNow or your own webhook endpoint, while keeping the customer-facing request and status in one place.
IDENTITY
SAML single sign-on and SCIM provisioning keep customer access aligned with the identity provider they already use, including user and group changes.
POWER AND AUTOMATION
Use SNMP or Redfish to bring cabinet and device readings into the power dashboard. Outbound webhooks let operational events feed the automations and notifications around your business.
The customer portal is only half of the platform.
Behind the customer experience is an operational workspace for the people who assign work, manage capacity, maintain the service record and keep customers informed. The same events that customers see are available to staff with the controls and context needed to act on them.
SERVICE OPERATIONS
Ticket assignment, SLA tracking, inspection forms, response templates, escalations and on-call routing.
FACILITY OPERATIONS
Remote hands, permits, deliveries, assets, floor plans, rack positions, circuits and power-device administration.
CUSTOMER MANAGEMENT
Account health, feedback, renewals, contracts, invoices, broadcast messages and a live incident and status feed.
GOVERNANCE
Audit trails, custom fields, knowledge articles, portal visibility controls, scheduled reports and exports.
AI OPERATIONS
Review AI conversations, feedback, triage outputs and anomaly scans, with configuration and cost controls in the same workspace.
TENANT MANAGEMENT
Manage customers, team members and shared platform settings across the operator estate.
DCIM manages the data centre. Cloud Colo manages the customer relationship around it.
| CAPABILITY | PSA SUITESHaloPSA · ConnectWise · Autotask | DCIM SUITESSunbird dcTrack · Nlyte · Hyperview | CLOUD COLOOne platform for colocation operators |
|---|---|---|---|
Customer sees their own cabinets, U positions and floor plan | NO | PARTIAL | CORE |
Customer sees contracted capacity against actual power draw | NO | PARTIAL | CORE |
Customer raises site access requests and visitor passes | NO | NO | CORE |
Customer books deliveries to the dock and tracks them | NO | NO | CORE |
Customer orders new services from a catalogue | NO | NO | CORE |
Customer books remote hands and receives photo evidence | PARTIAL | NO | CORE |
Permits to work with validity windows and status | NO | NO | CORE |
Service desk with SLA matrices and escalations | CORE | NO | CORE |
Cabinet and U-position inventory with floor plans | NO | CORE | CORE |
Per-customer energy and carbon reporting (EU EED) | NO | PARTIAL | CORE |
Two-way NetBox sync | NO | PARTIAL | CORE |
Cloud Colo starts with the customer and connects them to their infrastructure, services and operational history. It can sit alongside the systems you already use for facility management, monitoring and ticketing, providing the customer operating layer they were not designed to deliver.
CORE means a primary, documented capability of the product class. PARTIAL means available in some products or in a limited form. NO means not part of the product class. Compared by product class rather than by individual edition, based on public vendor documentation. Products change. Check the vendor's own material for current capability.
Built from 15+ years inside the realities of colocation customer operations.
Cloud Colo grew from a platform used for more than 15 years to support customer operations at Volta Data Centres. The original system helped customers manage service requests, deliveries and access while giving the operator a clear journal of activity.
Cloud Colo takes that proven customer-first model further, connecting the customer to cabinets, capacity, power, connectivity, projects, services and sustainability information. What began with service requests, deliveries, access and activity history has evolved into a broader customer operating system for modern colocation providers.
What is built in, and a straight answer about what we do not have yet.
Two-factor authentication, role-based permissions, an automatic audit trail, tenant isolation and strict separation between staff and customer portal sessions are built into the product. Encryption in transit and at rest comes from the managed infrastructure the platform runs on.
For operators who need the control plane inside their own estate, Cloud Colo can be deployed on-premises so tenant data never leaves your network.
Look at your own facility, not a demo tenant.
SEE IT WITH YOUR OWN DATA
Thirty minutes. No slide deck. We build your floor plan before the call and you look at that.
BOOK A DEMOOR JUST HAVE A LOOK NOW
A live portal, logged in as a customer of a fictional facility. No form, no email address, nothing to install.
EXPLORE A LIVE PORTAL