Two bills for one job
A growing business often ends up with several places where its websites, applications and files are hosted. The company website sits with a local web host. The booking system runs on a rented server somebody set up in 2021. A test copy of the customer portal lives in a cloud account. A reseller package bought for a client project is still being paid for. Each decision made sense when it was taken. Together they mean the business is paying several times for capacity that, in many cases, one properly sized environment could provide.
This article is about duplicated hosting that could be consolidated: separate servers, plans and accounts that do overlapping work. It is different from servers running that nobody remembers the reason for, where the issue is purpose. Here every environment may have a purpose; the question is whether each needs to be separate.
How duplication builds up
- One project, one environment. Every new system gets its own host because that is the quickest way to launch, and nobody revisits the arrangement later.
- Different people, different suppliers. Marketing chose a host for the website, a developer chose another for the app, and finance pays both invoices without seeing the connection.
- Safety margins that never shrink. A server sized for a peak that happened once is paid for at that size every month.
- Staging and test copies. Copies made for a project keep running after it ends, a problem explored in idle test and development systems.
- Fear of touching what works. Moving a site feels risky, so duplicates persist. This is the same reluctance that keeps old applications alive, as described in old applications kept because migration feels difficult.
Why consolidation is often possible
Many hosting products are designed to share resources. In Microsoft's Azure App Service, for example, an App Service plan defines a set of compute resources, and whatever apps you put into the plan run on those resources. Several modest applications can therefore share one plan instead of each paying for its own. Other providers offer similar arrangements through shared servers, virtual machines hosting multiple sites, or container platforms.
Cloud architecture guidance treats this as a normal part of cost management. The cost optimisation pillar of the AWS Well-Architected Framework describes a cost-optimised workload as one that fully utilises its resources and meets its functional requirements at the lowest possible price point. Microsoft's Azure Well-Architected cost optimisation guidance lists consolidation among its approaches to optimising component costs, alongside reviewing environments and scaling. Neither document says every business should consolidate everything. Both say that utilisation should be examined deliberately instead of left to accumulate.
Consolidation has limits. Some workloads must be separate for good reasons: a payment-processing system may need isolation, a client may contractually require its own environment, and a production site should not share a failure with an experimental one. The aim is to separate by reason, not by accident.
Where the financial impact lands
Direct hosting fees
The visible cost is the sum of the invoices. When these arrive from different suppliers on different dates, in rand and in dollars, nobody adds them up. Exchange rate movements on dollar-priced services make the total harder to forecast.
Idle capacity
If three servers each run at a small fraction of their capacity, you are paying for the unused remainder three times. The waste is not visible on an invoice; it shows up only in usage metrics, which many small businesses never open. A related pattern is overprovisioned server capacity.
Duplicated administration
Every environment needs patching, backups, monitoring, certificate renewals and access control. Four environments mean four sets of each task, or, more commonly, one set done well and three done occasionally.
Risk concentrated in the neglected copies
The environment that nobody likes to touch is the one that falls behind on updates. Unpatched software and forgotten administrator accounts are exposure the business is paying for without benefit.
An illustrative cost model
The figures below are illustrative assumptions for a hypothetical Pretoria software and services firm with 40 staff. They are not benchmarks.
| Assumption | Value |
|---|---|
| Separate hosting environments in use | 6 |
| Combined monthly hosting cost | R19,500 |
| Environments that could share capacity without a technical or contractual reason to stay separate | 4 |
| Estimated saving from consolidating those four | 35% of their combined R11,000 a month |
| Administrator hours a month on patching, backups and renewals across the six | 18 hours at R450 |
| Hours saved if four become two | about 6 a month |
On these assumptions, the hosting saving is R3,850 a month, or R46,200 a year, and the administration saving is R2,700 a month, or R32,400 a year. That is R78,600 a year. Against it, the firm would carry a one-off migration cost, perhaps R25,000 to R60,000 in contractor time and testing. The payback is within a year, but only if the review is done carefully. Your numbers will differ; the point is to run the calculation rather than leave the question open.
A sensible way to review
- List every environment, its supplier, monthly cost, purpose and business owner.
- Collect 30 days of usage figures for each: processor, memory, storage and traffic.
- Mark each environment as keep separate, candidate to merge, or candidate to retire, and write down the reason.
- Plan the move with a tested backup, a rollback path and a cut-over outside trading hours.
- Cancel the old environment only after a stable period, and confirm that renewals and domain records have been updated.
Overlapping tools and overlapping infrastructure often grow together. If this pattern sounds familiar, a software environment that grew by accident describes the wider effect on complexity and productivity.
What to ask suppliers
Before moving anything, ask each current provider three questions: can this plan be merged with another on the same account, is there a lower tier that fits measured usage, and what notice or termination fee applies. Many suppliers will adjust a plan to keep a customer, and the answers set the real size of the saving. Also ask what is included in the price, such as backups, email and security certificates, so that a cheaper plan does not quietly remove something you rely on.
Practical next actions
- Build a single list of every hosting account, server and plan, including the ones paid for by individual departments or on personal cards.
- Assign each environment a named business owner who can say what it is for and what would break without it.
- Pull 30 days of usage data for each and identify the two or three with the lowest utilisation.
- Ask your current providers whether plans can be combined or downsized, and request quotes for sharing capacity.
- Run one low-risk consolidation first, such as moving a small internal site onto an existing server, and record the saving.
- Set a yearly review date so that new environments are checked against existing capacity before they are created.
Sources and further reading
- Cost Optimization Pillar - AWS Well-Architected Framework - Cost Optimization Pillar (last verified 10 October 2026)
- Cost optimization quick links - Microsoft Azure Well-Architected Framework
- Azure App Service Plans - Azure App Service
Related Mellorca reading
- Paying for Tools You Already Own: The Cost of Underused Software Platforms
- Paying Twice: What It Costs When Nobody Knows What Your Plan Already Includes
- Automatic Software Renewals: The Cost of Paying for Yesterday's Requirements