When reviewing a VPS platform, a dedicated server fleet or colocated hardware, compare the environmental evidence for the service you need. A lower electricity bill, lower PUE and smaller lifecycle carbon footprint are different results. This guide explains data center CUE and a hypothetical keep-or-replace calculation, then connects those results to cooling, water, renewable supply, hosting architecture and the questions to ask a provider.
No facility measurements or DCHost environmental performance results are presented here. The numerical examples are invented inputs for learning the method, not benchmarks or expected savings. For a broader introduction, see how green infrastructure shapes modern hosting. For choosing between providers, use our guide to assessing hosting sustainability evidence.
What CUE Measures—and What It Leaves Out
Carbon Usage Effectiveness (CUE) relates a data center’s annual operational greenhouse gas emissions to its annual IT equipment energy. Use kilograms of CO₂ equivalent per kilowatt-hour of IT energy, written kgCO₂e/kWh. IT includes computing, storage and in-facility networking. The numerator and denominator must cover the same facility and period.
CUE = Annual operational emissions attributable to the data center / Annual IT equipment energy
The Green Grid’s introductory CUE framework covers Scope 1 and Scope 2 operational emissions; equipment manufacturing and shipping are outside it. Its electricity-only shortcut assumes the entire facility runs on grid electricity without local emissions. On-site generators and other energy sources require an expanded emissions calculation. See The Green Grid’s CUE paper and the U.S. Department of Energy design guide, section 8.
Keep the PUE Boundary Consistent
Annual PUE divides total facility energy by IT energy over that year. The following power formula instead describes a simultaneous snapshot:
PUE = Total Facility Power / IT Equipment Power
For example, a hypothetical total facility draw of 1.4 MW with 1.0 MW going to IT gives an instantaneous ratio of 1.4. Grid import alone is not necessarily total facility power if generation or other energy inputs exist. The difference includes necessary support systems such as cooling and power conversion; calling all of it avoidable waste is misleading.
Do not multiply an annual electricity factor by a best-hour PUE and present the result as measured annual CUE. Record the year, meter coverage, treatment of shared buildings, energy sources, greenhouse gases and factor provenance. Mark estimates and missing data explicitly.
A Worked Electricity-Only CUE Example
Assume a hypothetical all-electric facility uses 1,000,000 kWh for IT and 1,500,000 kWh in total over one year. Assume an applicable electricity factor of 0.4 kgCO₂e/kWh, constant for this example, with no other operational emissions. Then:
- Annual PUE: 1,500,000 / 1,000,000 = 1.5.
- Operational emissions: 1,500,000 × 0.4 = 600,000 kgCO₂e.
- CUE: 600,000 / 1,000,000 = 0.6 kgCO₂e/kWh of IT energy.
Here CUE also equals PUE × electricity factor: 1.5 × 0.4 = 0.6. This equality follows from the stated boundary. With multiple supplies, calculate each applicable energy quantity and factor, include other in-scope operational emissions, and divide their total by IT energy. Do not silently omit diesel-generator testing or treat battery discharge as newly generated renewable energy.
Why a Better Ratio Can Mislead a Hardware Decision
CUE uses IT energy, not successful transactions or completed jobs, as its denominator. Consider another hypothetical comparison with the same completed work and electricity factor of 0.4. Before a change, IT energy is 1,000 kWh and total facility energy is 1,500 kWh. Afterward, IT energy is 600 kWh and total energy is 1,000 kWh.
| Measure for the same example period | Before | After |
|---|---|---|
| PUE | 1.5 | About 1.67 |
| CUE, kgCO₂e/kWh of IT energy | 0.6 | About 0.67 |
| Total operational emissions, kgCO₂e | 600 | 400 |
Both ratios increase while total operational emissions fall by 200 kgCO₂e. This is arithmetic, not a measured project outcome: fixed or unevenly changing facility overhead can make ratios move differently from totals. Retain total energy, total emissions, completed work and service quality in the decision record. Neither PUE nor CUE supplies the missing hardware manufacturing impact.
Choose and Disclose the Electricity Accounting Method
Location-based electricity accounting uses the relevant grid emissions factor. Market-based accounting uses qualifying supplier or contractual data under the applicable rules. Keep the two results separately labeled where both are reported. Check whether a factor covers CO₂ alone or CO₂ equivalents, its year and geography, and whether its boundary fits the calculation. A factor in gCO₂e/kWh must be divided by 1,000 before use with kgCO₂e quantities.
Under the GHG Protocol Scope 2 Guidance, contractual instruments must meet quality criteria. A PPA does not by itself prove that the customer holds the environmental attributes or caused additional generation. Annual certificate matching also does not show that the site’s electricity physically came only from renewable generators in every hour. The Scope 2 questions and answers distinguish allocating emissions in an inventory from proving an action’s wider impact.
If a report adds hourly matching, record the matching region, time resolution and treatment of unmatched hours. Greater time detail can clarify the claim; it does not by itself establish avoided emissions. Keep a proposed method change separate from a measured improvement. The relationship between new capacity and electricity procurement is discussed in our article on data center expansions and green energy.
Include Cooling, Water and Local Energy in the Comparison
A CUE result helps describe operational carbon; it does not decide whether a facility’s water use or cooling arrangement suits your project. Keep these questions in the same hosting decision. A server refresh, a move to another site and a cooling retrofit can affect different resources, so compare the complete proposed service rather than selecting whichever option reports the lowest single ratio.
Check Aisle Containment and the Actual Cooling Path
Hot- or cold-aisle containment separates server exhaust from the air supplied to equipment intakes. A useful inspection asks whether rack orientation, blanking panels, cable openings and return paths maintain that separation. Equipment with side exhaust or a nonstandard airflow direction needs an appropriate arrangement. The DOE design guide, section 4.2, describes these details. A photograph of a contained aisle does not establish its measured energy saving.
Record rack inlet temperatures and humidity at representative loads, together with fan and cooling energy and any hot spots. Use the equipment’s environmental limits when assessing setpoints. Air-side economization depends on outdoor temperature, humidity, contaminants and filtration; water-side economization depends on the installed heat-exchange system and outdoor conditions. Neither is a promise of year-round compressor-free operation. For colocation, establish who owns airflow changes inside the rack and who controls the room’s cooling, so the proposed density and maintenance arrangements can be assessed together.
Evaluate Water Stewardship alongside Energy
Ask for annual site water use as well as site-based WUE: annual site water divided by annual IT energy, in litres per kWh. Use the same site and period and state what the water meters include. The DOE guide’s section 8.3 distinguishes this from source-based WUE, which also considers water used off-site to produce the energy consumed on-site. CUE and PUE do not supply either water result. Include the water source, seasonal demand and local supply constraints when comparing locations.
For evaporative cooling, review makeup water, blowdown, leaks, water treatment and the operating conditions that control water demand. The DOE’s data center cooling-water guidance explains these operating issues and the tradeoffs of treatment and cooling options. Changes to water chemistry and controls need a qualified operating plan; reducing blowdown without managing mineral concentration can compromise the system. A closed loop near a server also does not prove that the final heat-rejection stage consumes no water.
Reclaimed water, condensate or other suitable non-potable supplies may reduce demand for potable water, but the choice needs evidence about source quality, treatment, storage and distribution. PNNL’s review of water reuse for cooling towers describes these requirements. Include the energy and maintenance needed for the selected treatment and the availability of that source during the site’s operating conditions. Report a reduction in potable-water demand separately from a reduction in total water use.
Separate On-Site Solar, Storage and Backup Claims
For on-site solar, ask for measured generation, the reporting period, usable site area, and how much generation the facility consumed or exported. Compare the generation profile with the facility load; panel capacity alone does not describe annual coverage or power available at night. Keep on-site generation, purchased electricity and contractual renewable attributes distinct in the carbon record, and avoid counting the same energy benefit twice.
A battery shifts energy in time; it is not a new renewable generator. The DOE’s solar and storage explanation distinguishes power capacity from energy capacity and notes conversion losses. Request usable storage capacity, charge source, operating limits, discharge power, expected duration at the protected load, and the reserves needed for the contracted service. Include replacement and maintenance assumptions when comparing lifecycle impacts.
Backup power needs its own design and test evidence. Solar panels and a battery do not by themselves prove that a facility can operate through a grid outage. Confirm the required controls, isolation, switching and ability to support the intended loads, plus the role of UPSs and generators. The DOE’s microgrid islanding example illustrates why coordinated equipment and operating sequences matter. Assess the actual facility’s arrangement rather than treating that example as a site certification or runtime guarantee.
Compare Keeping and Replacing a Server
First Establish an Equivalent Service
Before calculating carbon, define the work both options must perform: throughput, latency, data volume, retention, availability and recovery objectives. Include peak demand and maintenance capacity. A new server that handles less work is not an equivalent comparison, and retiring redundancy does not count as an efficiency improvement for the same service.
Measure whole-system energy at representative loads, including idle periods and the selected power-management configuration. New CPU generations or NVMe devices may improve performance; their names do not establish lower energy for the required work. For capacity inputs, see how many vCPUs and how much RAM you need. A smaller virtual allocation does not itself prove a physical host consumed less power or was removed.
Separate Future Operational and Hardware Impacts
Use the same remaining planning period for both options. Keeping equipment includes its future electricity and any required repair or replacement parts. Replacing it includes the new equipment’s manufacturing and transport, migration effects, future electricity and the old equipment’s actual destination. The old server’s past manufacturing emissions have already occurred; do not count them as a new avoided emission simply because you retire it.
Request a product carbon footprint or lifecycle assessment for the actual configuration, with its boundary, assumptions, geography and uncertainty. A supplier’s full-lifecycle figure may already include estimated electricity use: adding that entire figure to your own operational estimate can double count it. Separate the relevant stages before comparing. The GHG Protocol Product Standard describes lifecycle stages and the role of product rules in comparison. Two declared footprints are not automatically comparable without compatible boundaries and rules. Keep purchase cost, support risk and carbon results in separate columns.
A Hypothetical Three-Year Decision
Suppose an existing server and a replacement meet exactly the same service requirement. Their hypothetical average IT power draws are 300 W and 200 W, respectively, over 8,760 hours each year. Assume PUE stays at 1.5, the electricity factor stays at 0.4 kgCO₂e/kWh, and there are no other operational emissions in this example.
Assume replacing now adds 1,200 kgCO₂e of future non-operational impact relative to keeping. This invented net input includes the modeled differences in manufacturing, transport, repairs, migration-related non-operational impacts and retirement. It excludes electricity already calculated below. Both options are assumed serviceable for all three years, no replacement or repair occurs in the keep option, and no reuse credit is claimed. Assume migration adds no material electricity beyond the modeled consumption.
| Hypothetical input or result | Keep | Replace now |
|---|---|---|
| Average IT power | 0.3 kW | 0.2 kW |
| Annual IT energy | 2,628 kWh | 1,752 kWh |
| Annual facility energy allocated using PUE 1.5 | 3,942 kWh | 2,628 kWh |
| Annual operational emissions at 0.4 kgCO₂e/kWh | 1,576.8 kgCO₂e | 1,051.2 kgCO₂e |
| Additional future non-operational impact in this comparison | 0 kgCO₂e | 1,200 kgCO₂e |
| Three-year modeled total | 4,730.4 kgCO₂e | 4,353.6 kgCO₂e |
The modeled annual operational difference is 525.6 kgCO₂e. Dividing 1,200 by 525.6 gives an illustrative carbon break-even time of about 2.28 years. Over three years, replacement is lower by 376.8 kgCO₂e under these assumptions. This is not financial payback, a universal refresh interval or evidence about any real server.
Multiplying server energy by a facility’s average PUE is an allocation estimate. Removing one server does not necessarily reduce chillers, UPS losses or other support loads in that proportion. To claim an actual saving, use the measured facility response or an explicitly justified model, and account for changes in workload, cooling and utilization.
Test Whether the Result Survives Different Assumptions
Keep the same hypothetical inputs but lower the electricity factor to 0.1 kgCO₂e/kWh. The annual operational difference becomes 131.4 kgCO₂e, and the break-even time becomes about 9.13 years. The three-year totals are 1,182.6 kgCO₂e for keeping and 1,988.4 kgCO₂e for replacing. Replacement is now higher by 805.8 kgCO₂e within the planning period.
Repeat with credible ranges for power, equipment impact, service life and electricity factors. If the operating difference is zero or negative, this simple model has no positive operational carbon break-even. If support ends before the calculated point, the keep scenario must change; unsupported equipment cannot be assumed indefinitely serviceable. When factors or power change over time, add each period’s emissions instead of extending a constant annual saving.
Reuse and Procurement Need Their Own Evidence
Give Reused Equipment a Defined Destination
Reuse can extend service life, but moving a retired server into an unnecessary lab adds a load. Record the receiving workload, owner, expected hours, support requirements and next review date. Establish which purchase or active machine it replaces. Include transport, refurbishment and the receiving site’s electricity. Report an avoided purchase as an explicit comparison assumption, not an automatic credit for every reused unit.
For storage, tiering can match access and recovery needs without assuming that a slower disk or object storage service uses less total energy. Include copies, redundancy, retrieval frequency and the systems serving each tier. Our hot, cold and archive storage strategy for backups provides the operational context.
Buy Equipment You Can Maintain and Retire Responsibly
Procurement should request repair instructions, component replacement options, support and spare-part availability, suitable sanitization functions and a documented end-of-life route. Confirm the actual model and contracted terms. The UNEP sustainable procurement guidelines for data centres and servers address serviceability, recycling design and preparation for reuse; they are guidance, not proof that a particular supplier or product meets your requirements.
A useful purchase record contains the delivered configuration, measured workload-energy results, environmental declaration boundary, warranty and support dates, repair path and disposal responsibilities. These records make later keep-or-replace calculations reproducible. An energy label or a recycling logo cannot fill gaps in the actual equipment record.
Verify Sanitization Before Transfer or Reuse
Reformatting or deleting files should not be treated as universal evidence that a drive is safe to transfer. Choose a method for the medium, data sensitivity and intended destination under the organization’s sanitization policy. NIST SP 800-88 Revision 2 distinguishes clear, purge and destroy methods and requires attention to both completion and effectiveness. A purge technique may preserve reuse; destruction does not.
Inspect completion status and errors, then validate whether the result is acceptable for the data and medium. Record the device identity, method, technique, tool version, date, responsible people and destination. A tool reporting success is insufficient if its method was unsuitable. For example, degaussing does not sanitize flash SSDs. Use qualified handling and an appropriate recycling route for equipment that cannot be safely reused.
Choose Hosting Architecture for the Required Service
Before comparing server replacements, check whether the workload belongs on the proposed hosting architecture. Shared hosting, VPS, dedicated servers and colocation offer different control and responsibility boundaries. None is automatically the lowest-carbon option. Use measured CPU, memory, storage and network demand, together with isolation, recovery, support and data-location requirements, to define an equivalent service.
| Option | When to evaluate it | Evidence needed for this decision |
|---|---|---|
| Shared hosting or a modest VPS | A workload fits the supported platform and its isolation and resource limits | Peak demand, contention limits, upgrade path, service responsibilities and available energy-allocation method |
| A larger VPS or dedicated server | Measured load, isolation or software-control requirements justify additional capacity | Representative utilization, whole-service energy, idle periods, support window and maintenance headroom |
| Multiple servers or regions | Availability, recovery or workload distribution requires more than one node or location | Replication, failover capacity, network/storage overhead and behavior during maintenance or a site failure |
| Colocation | You need to operate your own hardware within a contracted facility service | Rack power and cooling responsibilities, equipment lifecycle, remote support, metering and network/backup dependencies |
A consolidation proposal should identify which physical hosts can actually be powered down or which purchase can be avoided while preserving the required service. Reducing a VM’s allocation or moving tenants does not prove that the underlying facility uses less energy. Conversely, a well-utilized dedicated server may suit a sustained workload better than an unsuitable shared arrangement. Compare the complete service and the evidence available, rather than ranking plans by product name.
Choose regions with the same care. A latency-sensitive frontend may need proximity to users; a batch or backup workload may tolerate a different location. Evaluate transfer volume, replication, recovery time, data-location obligations and the relevant energy/carbon data before moving it. A lower regional electricity factor is one input, and does not make a slower, noncompliant or insufficiently recoverable service equivalent.
Keep Operational Changes Connected to the Decision
Before buying hardware, assess whether a smaller workload can meet the same requirements. Review unused environments and retention schedules with their owners; preserve legal holds, required logs, restore points and backup dependencies. Deleting a backup that is still needed for recovery is not an acceptable capacity reduction. See the backup storage tiering guide when planning retention and restore access.
Apply privacy and data-location constraints separately from carbon targets. Our guide to KVKK, GDPR and hosting location provides context; a lower-emission region alone does not establish compliance. Include transfer and recovery costs when considering another site.
Caching and media optimization can reduce repeated work. Exclude personalized, session, cart, checkout and account responses from shared caching, and verify freshness and invalidation. Include any additional CDN and network resources in an end-to-end energy comparison. Lower origin CPU utilization, HTTP/2, HTTP/3 or TLS 1.3 alone is not proof of fewer physical machines or lower carbon emissions.
Cooling and power changes alter the assumptions behind a hardware comparison. Measure equipment inlet temperature and humidity, use manufacturer limits, and account for climate and filtration when considering free cooling. Compare UPS efficiency at the actual load and mode while preserving resilience. Liquid cooling needs assessment of the whole heat-rejection system, including pumps, fans and water.
Heat reuse also needs a nearby demand, useful temperature and delivery infrastructure. Record the heat actually used, additional pumping or heat-pump electricity and the treatment of any claimed displaced energy. Do not simply subtract all exported heat from CUE. An annual accounting improvement, a physical energy saving and a wider avoided-emissions claim need distinct evidence.
Ask the Provider for Evidence That Can Change the Decision
Use the following questions with DCHost or any hosting or colocation provider. Request answers for the actual site and service under consideration, with a date and accountable owner. Missing data should remain a stated uncertainty in the comparison; a broad company-wide sustainability statement cannot supply a site’s measurements.
| Decision area | Question | Useful evidence |
|---|---|---|
| Energy and carbon | What are annual facility and IT energy, PUE and operational emissions for this site? | Year, meter boundaries, factor units and provenance, accounting method and treatment of other energy sources |
| Water | What water sources and annual quantities support this cooling system, and what does reported WUE include? | Site/source distinction, potable and reused-water quantities, seasonal context and operating plan |
| Renewable supply and storage | What is generated on-site, what is purchased or matched contractually, and what can the backup system actually support? | Generation/use/export records, attribute ownership and matching period, storage power/energy and tested backup scope |
| Cooling and power delivery | How are containment, economization, UPS efficiency and the proposed rack load managed? | Inlet conditions, actual load/mode results, operating limits and responsibility for changes |
| Hardware lifecycle | What supports repair, an appropriate refresh interval and a verified reuse or retirement route? | Configuration-specific lifecycle boundaries, support dates, spare parts, sanitization and destination records |
| Architecture and operations | Can this plan meet peak demand, isolation, retention, recovery and data-location requirements without unnecessary capacity? | Measured demand, maintenance/failover headroom, backup and retention responsibilities, and the method used to allocate shared impact |
| Independent assurance | Which claims have been checked, for which sites and periods, and what remains outside that check? | Audit or certificate scope, issuer, period, findings and limitations; no inference that a badge proves every environmental outcome |
Compare responses on a common boundary and period, and keep targets separate from achieved results. Make the provider-selection consequence explicit: accept the evidence for the defined requirement, request a missing measurement, revise the architecture, or retain the current option while investigating. This keeps the checklist connected to the CUE and lifecycle calculation rather than turning it into a collection of green labels.
Leave a Reproducible Decision Record
- Scope: facility, asset, workload, service requirements and planning period.
- Energy: meter boundaries, representative operating hours, actual or modeled PUE, and treatment of shared infrastructure.
- Carbon: factor units, geography, year, accounting method and other included operational emissions.
- Hardware: stage-separated product impact, support window, repair assumptions and destination of retired equipment.
- Decision: keep, replace or reuse; alternatives considered, uncertain inputs, owner and next review trigger.
The record should show what would change the decision, such as a support deadline, a failed component, a workload increase or an updated emissions factor. Our operational sustainability guide covers ongoing measurement and improvement. Related reading includes The Quiet Revolution in the Server Room. Broader data center sustainability trends can suggest candidates for review, but they cannot supply the missing measurements for your fleet.
Use CUE for its defined operational boundary and a separate future-impact comparison for hardware. Evaluate water, cooling, local energy and architecture alongside those carbon results. Select a hosting option only after its capacity, support, recovery and data-location requirements are satisfied, and retain the evidence and uncertainties that explain the decision.
