About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When your office servers reach the end of their life, the choice is not only "cloud or not". This article compares three ways to move them into a data centre by one question: who owns the hardware and who carries the risk when it fails or ages. In colocation, you still own and replace the servers. In the kind of managed private cloud compared here, a provider runs hardware dedicated to you; not every offer called private cloud uses dedicated hardware. With virtual servers on a provider's shared platform, replacing and repairing the hardware becomes the provider's job under the contract, and you pay for capacity.
Why it matters
Hardware risk does not disappear in a data centre; it moves. A failed disk controller, a host that no longer receives firmware updates, or a five-year refresh that nobody budgeted for will land on someone. If the contract does not say who, you may find out during the failure itself.
How it works
Three models side by side
The table is our editorial summary of the typical split; the contract decides the real one.
| Question | Colocation | Managed private cloud on dedicated hardware | Virtual servers on a shared platform |
|---|---|---|---|
| Who runs the building, power, cooling and data centre network? | The colocation provider, as the contract sets out; the servers, storage and your own network equipment are yours | Provider | Provider |
| Who owns the servers and storage? | You | The provider or you, depending on the contract; dedicated to you | Provider |
| Who replaces a failed part? | You or your hardware support contract | Provider | Provider |
| Who patches firmware and the virtualisation layer? | You (if you run a virtualisation layer at all) | Provider | Provider |
| Who funds the next hardware refresh? | You, as a capital purchase | Provider, recovered in fees and term | Provider, invisible to you |
| Can you add capacity without buying hardware? | Within spare capacity in the hardware you have installed, then a purchase | Within the dedicated hardware, then a purchase | Yes, within the platform |
| Is the hardware shared with other customers? | No | No | Yes, separated by virtualisation |
"Private cloud" can describe very different offers, and not all of them run on hardware dedicated to one customer. In this article the term means the dedicated-hardware kind. Our article What "private cloud" means: shared hardware, dedicated hosts and the questions to ask covers the definition and the isolation levels. This article looks only at the hardware lifecycle: ownership, failures, firmware and refresh.
What a provider takes on
The Australian Signals Directorate's guidance for small and medium businesses says the cloud provider is responsible for providing cloud services that are securely designed, set up and operated, and that "this includes the security of underlying infrastructure and all third parties involved in providing the cloud services". In colocation, the servers, storage and any virtualisation layer are yours; the colocation provider still carries the facility duties its contract names, typically the building, power, cooling, physical access and any network connection it supplies.
Ageing hardware is a security matter, not just a performance one
Australia's Information Security Manual treats unsupported equipment as a risk to remove. It states that "unsupported applications, operating systems, network devices and networked IT equipment should be removed or replaced", and it sets timeframes for firmware fixes, including firmware patches "applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist" (that control applies at Essential Eight maturity level three). ASD describes the ISM as "a cyber security framework organisations can use to protect information and operational technology systems from cyber threats"; a business may choose to adopt these expectations. If it does, whoever owns the hardware owns the job of meeting them, out of hours if needed.
What to choose and why
Colocation suits you when
- You have recent hardware with years of vendor support left and staff who can run it.
- You need hardware a provider will not supply, such as a specialised appliance.
- You accept that a failed part is your call, your spare and your engineer's trip to the data centre.
A managed private cloud on dedicated hardware suits you when
- You need hardware that is not shared with other customers, for a contractual, regulatory or performance reason you can name.
- Your workload is steady enough to fill dedicated hardware for the contract term.
- You want the provider to carry part failures, firmware and refresh, and you accept a longer commitment in return.
Virtual servers on a shared platform suit you when
- You want to stop owning hardware altogether.
- Your capacity needs change, and you want to add or remove resources without a purchase.
- You are satisfied with the provider's isolation and evidence, and have no specific reason to need dedicated hardware.
A hypothetical decision
A 40-person engineering firm has two four-year-old servers and a storage array whose support contract ends in 18 months. Moving them into colocation would buy time, but the array's support end date would still arrive, and the firm has no in-house engineer to attend failures. Unless it can name a reason for dedicated hardware, virtual servers on a shared platform remove the coming hardware refresh from the firm's own budget and to-do list; a managed private cloud would also remove it, at the cost of a commitment sized to the hardware. The example is illustrative.
Questions to ask
- Who owns each piece of hardware on day one, and at the end of the term?
- Who attends a failure, how quickly, and is a spare part on site?
- Who applies firmware and virtualisation updates, and on what schedule?
- When the hardware reaches the end of vendor support, who pays to replace it?
- In a private cloud, what happens if your needs shrink below the dedicated hardware you are paying for?
Read next
Related articles you may want next.
- HostingManaged, co-managed or self-managed hosting: choosing how much of the server you runHow a business decides which layers of a hosted server it hands to a provider and which it keeps, using staff time, the need for administrator access and the evidence it must produce.Read article
- HostingWhat "private cloud" means: shared hardware, dedicated hosts and the questions to askHow the standard definition of private cloud differs from the way the term is used in hosting offers, what shared tenancy, dedicated instances and dedicated hosts each isolate, and the questions that establish what an offer actually provides.Read article
- HostingShared SAN, hyperconverged or local disks: choosing storage for a private cloudHow the storage design of a private cloud decides whether servers restart after a host failure, how maintenance works and what adding capacity involves, compared across a shared array, hyperconverged storage and local disks.Read article
Risks and limits
- Colocation keeps the refresh cycle. Moving old servers into a better building does not extend their vendor support.
- Dedicated hardware has a fixed ceiling. Growth beyond it needs a hardware purchase and lead time, whoever pays.
- Shared platforms depend on isolation. Ask what separates your workloads from other customers and what evidence the provider gives.
- Data, accounts and backups stay your responsibility in every model. ASD notes you cannot outsource the risk of losing your data.
- Ownership terms vary by contract. This article describes illustrative arrangements, not any provider's terms.
Sources
Opened 15 November 2026.
- Australian Signals Directorate: Cloud shared responsibility model: Guidance for individuals and small and medium businesses, October 2025 publication.
- Australian Signals Directorate: Information security manual overview page, opened 16 November 2026.
- Australian Signals Directorate: Information Security Manual, Guidelines for system management, September 2026 edition.
Related article: What "private cloud" means: shared hardware, dedicated hosts and the questions to ask.
Related service: Cloud hosting.
Learning notes
- Hardware risk moves with the hosting model; it does not vanish.
- In a managed private cloud on dedicated hardware, check the contract for who owns the dedicated hardware.
- The ISM expects unsupported equipment to be removed or replaced; a business may adopt that expectation.
- Colocation keeps refresh costs with you; virtual servers on a shared platform remove them from view.
- Ask who owns, repairs, patches and refreshes each piece of hardware.
This article was originally published on .