Skip to content

Cut cloud costs by moving always-on workloads to hardware you control.

Workloads that run all day, every day, cost less on hardware you control in a data center than on hourly cloud rates. We find the ones that qualify, price the move with every assumption shown, and run it.

The workloads that cost less on owned hardware

Three kinds of workload are billed by the hour for a service that never stops. These are the workloads that cost less on owned hardware in a data center.

Always-on VMs and databases

In the cloud
Always-on instances are billed by the hour whether busy or idle, and a managed database sized for production costs more than the compute it runs on.
In your cabinet
The same cores and memory on owned servers in a cabinet, virtualized with Proxmox VE or VMware, cost a fixed amount a month and nothing extra at 3 a.m.

Storage, backup and egress

In the cloud
Large data sets are billed by the gigabyte every month, then billed again as egress each time the data is read from outside the cloud, restored or moved.
In your cabinet
Owned storage in your cabinet is paid for once, backed up to a second site with Veeam or Proxmox Backup Server, and read as often as you like over your own circuits.

Virtual desktops

In the cloud
Hosted desktops are priced per user per month on top of the compute, storage and licensing they consume, and the bill tracks headcount forever.
In your cabinet
Citrix or Microsoft Remote Desktop Services on your own hosts in a data center serves the same users from hardware you own, on Windows Server session hosts with remote desktop user licenses.

How the comparison is built

Each side includes every cost, not just the headline rate. The cloud side is based on your invoices and usage exports, and the colocation side on a priced footprint and a hardware list.

The cloud side

  • Compute hours at on-demand or reserved rates, including the idle hours
  • Storage by the gigabyte-month, by tier
  • Egress and inter-region transfer
  • Managed database, load balancer and backup charges
  • Support plan, and licensing billed through the cloud provider

The colocation side

  • Cabinet or partial rack, with A and B power
  • Metered power at the facility rate
  • Transit, cross-connects and the private WAN to your offices
  • Hardware: bought outright and costed over five years, or supplied monthly
  • Telnetrix management: patching, monitoring and backups, with remote hands around the clock included in the colocation fee

Every comparison we produce shows each of these costs with the figures and assumptions behind it, so you can check it item by item against your invoices.

Three ways to own the hardware

Every comparison prices the hardware all three ways, so you can decide on cash flow as well as total cost. Hardware run by us, whether bought or supplied monthly, is our managed hosting product.

Buy it outright

Telnetrix sources and installs the servers and storage and arranges their parts support; you own them and depreciate them over three to five years.

  • Lowest total cost over the life of the hardware
  • Capital expense; the asset is yours
  • Refresh on your schedule

Supplied monthly

Hardware is included in a monthly managed colocation fee, so the move is operating expense like the cloud bill it replaces, with no upfront purchase.

  • No capital outlay
  • One predictable monthly amount
  • Hardware, spares and licensing in one fee

Mixed

Own the long-lived core and rent what may change, for example owned storage with monthly compute, and see both on the same comparison.

  • Buy what pays to own, and take the rest monthly
  • The comparison shows each line both ways
  • Change the mix at refresh

Three worked examples

These examples are illustrations. The cloud figures are Microsoft Azure South Central US list prices from Microsoft's public price list on November 3, 2026, and the owned figures are rounded from our own recent quotes. Your own comparison is based on your invoices.

About forty-five always-on Windows servers

A measured environment of about forty-five virtual machines on Windows Server: application servers, SQL Server, file services, domain controllers and remote desktop hosts, about 1 TB of memory in use and 12 TB of data.

The cloud side, per month

The cloud instances are sized to the memory the servers actually use, not to the hardware they run on today.

LinePay as you go3-year reserved
32 x D4s v5 Windows (4 vCPU, 16 GiB)Application servers, domain controllers, utility servers$9,671$6,424
8 x D8s v5 Windows (8 vCPU, 32 GiB)Remote desktop session hosts and larger application servers$4,841$3,212
5 x E8s v5 Windows (8 vCPU, 64 GiB)SQL Server and memory-heavy services$3,551$2,215
45 x 128 GB premium OS disksP10 managed disks$806$806
12 TB premium data disks12 x P30, 1 TB each$1,475$1,475
Backup of 45 instances, 15 TB storedAzure Backup: protected-instance fee plus stored data$794$794
5 TB a month of outbound dataInternet egress after the first 100 GB$437$437
Cloud, per month$21,600$15,400

The owned side

Hardware, onceFive Proxmox VE hosts with 384 GB and NVMe storage each, two firewalls, four 100 GbE switches, a backup server, optics and cabling. Refurbished, with one year of parts support.
$140,000
Spares reserve, once10% of the hardware price
$14,000
Licensing, every 3 yearsWindows Server Datacenter for the cluster's cores, 50 remote desktop user licenses and 50 user access licenses, bought once for three years.
$55,000
Support, per yearHypervisor support subscription for five hosts.
$2,000
Colocation, per monthA 12U secure cabinet with 1.5 kW on A and B circuits, two 2 Gbps blended transit connections, two fiber cross-connects, BGP with a block of addresses, and remote hands around the clock included.
$4,500
Colocation setup, once
$9,500

Three ways to own it, against the cloud

Bought outrightSupplied monthlyMixedCloud, pay as you go
Paid before the move$218,500$9,500$178,500$0
Per month after$4,700$10,500$5,800$21,600
Three-year total$386,500$386,500$386,500$776,700
Five-year total$553,500$637,800$580,200$1,294,500
Payback month, against pay as you gomonth 13month 1month 12–
Payback month, against 3-year reservedmonth 21month 2month 19–

Bought outright: hardware, spares and licensing paid before the move, licensing bought again at month 37. Supplied monthly: hardware, spares and licensing spread over 36 months with no finance charge, and the fee continues for as long as the hardware is used. Mixed: the servers bought, the rest supplied monthly. Figures round to the nearest hundred.

Assumptions

  • Cloud compute is priced at pay-as-you-go list rates, and in the 3-year reserved column with three-year reservations on the compute and the Windows license portion still paid by the hour.
  • Cloud instances are sized to the memory in use plus headroom, so they are smaller than the hardware they replace.
  • Owned hardware is refurbished with one year of parts support; a spares reserve of 10% of its price is added at purchase.
  • Hardware supplied monthly is spread, with its spares, over 36 months with no finance charge; a supplier's finance charge would be added to the monthly amount.
  • Licensing is bought again at month 37 in the five-year total.
  • Power use stays within the cabinet's allocation. Power above the allocation, which the facility bills at its utility rate, is not included.

Not included

  • Tax
  • Telnetrix management on the owned side and staff time on either side
  • Hardware refresh beyond five years
  • Workloads that stay in the cloud

Add 40 TB of files and 10 TB a month of egress

The same environment with a 40 TB file share added, read heavily from outside, with everything backed up.

This adds to the first example; only the extra costs are shown.

The cloud side, per month

This shows only the costs the extra storage adds to the first example. The reserved column applies a reservation to the file server only; disk and backup storage reservations, which the provider sells separately, are left out, and egress cannot be reserved.

LinePay as you go3-year reserved
1 x D8s v5 Windows file serverServes the share$605$402
10 TB premium disks5 x P40, 2 TB each, for the active data$1,178$1,178
30 TB standard HDD disks15 x S40, 2 TB each, for the rest$1,229$1,229
Backup of 40 TBProtected-instance fee per 500 GB plus stored data$1,718$1,718
10 TB a month of outbound dataInternet egress; the free 100 GB is already used above$891$891
Cloud, per month$5,600$5,400

The owned side

Hardware, onceTwo storage servers with seven 12 TB drives each in RAID 6, about 60 TB usable apiece: one serves the share, one holds its backup.
$24,000
Spares reserve, once10% of the hardware price
$2,400
Licensing, every 3 yearsServed from the cluster already licensed above.
$0
Support, per yearCovered by the cluster's support above.
$0
Colocation, per monthFits in the cabinet from the first example. Outbound data uses the cabinet's existing transit, with no per-gigabyte charge.
$0
Colocation setup, once
$0

Three ways to own it, against the cloud

Bought outrightSupplied monthlyMixedCloud, pay as you go
Paid before the move$26,400$0$26,400$0
Per month after$0$700$0$5,600
Three-year total$26,400$26,400$26,400$202,300
Five-year total$26,400$44,000$26,400$337,200
Payback month, against pay as you gomonth 5month 1month 5–
Payback month, against 3-year reservedmonth 5month 1month 5–

Bought outright: hardware, spares and licensing paid before the move, licensing bought again at month 37. Supplied monthly: hardware, spares and licensing spread over 36 months with no finance charge, and the fee continues for as long as the hardware is used. Mixed: the servers bought, the rest supplied monthly. Figures round to the nearest hundred.

Assumptions

  • Egress on the owned side is free because the cabinet's transit is unmetered.
  • The two storage servers add to the cabinet's power use; any charge for power above the allocation is not included.
  • Everything else is as in the first example.

Not included

  • Tax
  • Metered power overage
  • Drive replacements beyond the spares reserve

Replacing an existing two-cabinet environment with cloud

An established environment in two cabinets with 12 kW: a SQL data warehouse, application and database servers, identity services, 25 virtual desktops, firewalls and VPN, and backup of about 100 TB. Here the question runs the other way: what moving it to the cloud would cost, compared with keeping and refreshing it.

The cloud side, per month

A cloud provider's quote for the same environment, re-priced at 2026 list prices and grouped by service. Some of its servers are already on a three-year savings plan, and the rest is mostly services rather than hourly compute, so reservations would not change it.

LineAs quoted
SQL data warehouse servicesData integration and analytics services$9,900
Virtual machines, 10, with SQL ServerApplication and database servers, partly on a three-year savings plan already$22,100
Identity servicesDirectory and identity licensing for 250 users$4,000
Virtual desktops, 25 usersHosted desktops replacing the current remote desktop platform$9,700
NetworkingVirtual network, outbound and inter-region transfer, VPN, firewall, NAT, public addresses, monitoring$23,300
BackupServer, SQL and file backup of about 100 TB$17,600
SupportStandard support plan$100
Cloud, per month$86,700

The owned side

Hardware, onceA complete refresh budget for the environment's compute, storage and network, as an example figure; the actual quote depends on the design.
$1,000,000
Spares reserve, once5% of the hardware price
$50,000
Licensing, every 3 yearsAlready held. The cloud quote includes the identity and SQL Server licensing it bundles; renewing the licenses held today is not included.
$0
Support, per yearExcluded on both sides.
$0
Colocation, per monthTwo cabinets with 12 kW and two 10 Gbps cross-connects, already in place.
$6,700
Colocation setup, once
$0

Three ways to own it, against the cloud

Bought outrightSupplied monthlyMixedCloud, as quoted
Paid before the move$1,050,000$0$650,000$0
Per month after$6,700$35,900$17,800$86,700
Three-year total$1,291,200$1,291,200$1,291,200$3,121,200
Five-year total$1,452,000$2,152,000$1,718,700$5,202,000
Payback monthmonth 14month 1month 10–

Bought outright: hardware, spares and licensing paid before the move, licensing bought again at month 37. Supplied monthly: hardware, spares and licensing spread over 36 months with no finance charge, and the fee continues for as long as the hardware is used. Mixed: the servers bought, the rest supplied monthly. Figures round to the nearest hundred.

Assumptions

  • The cloud side is an actual provider quote for the whole environment, re-priced at list prices and rounded by service group; backup and networking together are close to half of the monthly total.
  • The owned side keeps the existing cabinets and adds a refresh budget, set at one million dollars as an example figure.
  • The monthly difference between the two pays for the refresh, so the payback month shows when the refresh has paid for itself.

Not included

  • Tax
  • Licensing renewals on both sides
  • Staff time on either side

Try your own figures

Enter your own monthly bill to run the same calculation as the examples. Change any figure and the result updates.

Your figures

As a percentage. The rest stays in the cloud and is not counted on either side.

A spares reserve of 10% is added automatically.

Result

The steady share of your bill, against the hardware bought outright and supplied monthly. Hardware supplied monthly is spread over 36 months with no finance charge.

Bought outrightSupplied monthlyCloud, steady share
Paid before the move$0
Per month after
Three-year total
Five-year total
Payback month–

These results are calculated from your figures and are not a quote. Send your figures with the form below and we will come back with a comparison built from your invoices.

Build the quote request

Choose the footprint, power, bandwidth and hardware model, and tell us what is moving and where. We will come back with a priced footprint and any questions we need answered to build your comparison.

See data center services for the footprints and markets.

Footprint
Hardware
What you are moving

Opens your email app with the request filled in, addressed to sales@telnetrix.com.

What stays in the cloud

Repatriation does not mean leaving the cloud altogether. When a workload should stay, we say so, and the data center connects to it privately.

  • Workloads that scale up and down by the hour or run in bursts
  • Services that need presence in many regions at once
  • Software you consume as a service, such as Microsoft 365, which is not infrastructure
  • Anything whose cloud-only managed features you depend on and cannot replace
Switches and structured cabling at the rack

How a move runs

Five steps, with the decision made on the numbers before anything is bought.

See data center services for the footprint, markets and network. If the servers are in an office room rather than the cloud, read moving out of an office server room.

  1. Bill analysis

    We read your cloud invoices and usage exports and sort workloads into three groups: steady, bursty and best left where they are. The steady workloads are the ones we price for the move.

  2. Footprint and network design

    The candidate list becomes a cabinet count, a power budget, a hardware list and a network design with the private WAN back to your offices and any cloud that stays.

  3. Comparison and decision

    We compare staying in the cloud with buying the hardware and with having it supplied monthly, cost by cost, with the assumptions shown. You decide what moves.

  4. Build and migrate

    Hardware is racked, cabled and tested in the data center. Workloads move in planned windows with a rollback plan ready, and the network is switched to the data center as part of the move.

  5. Operate and report

    Patching, monitoring, backups and remote hands from then on, with a monthly report that shows what the move is costing against what it replaced.

Common questions

Something not covered here? Call 817-207-8911.

What is cloud repatriation?

Cloud repatriation is moving workloads from a public cloud provider back to hardware you control, usually in a colocation data center, because steady workloads cost less to own than to rent by the hour.

Which workloads save the most when moved out of the cloud?

Workloads that run all the time with predictable load: virtual machines and databases that are never idle, large storage with frequent reads and egress, and virtual desktops for a stable headcount.

How is the saving proven before we commit?

Telnetrix builds a line-by-line comparison from your actual cloud invoices and usage against a priced colocation footprint, with hardware shown bought outright and supplied monthly, and every assumption shown so it can be checked.

Do I have to leave the cloud completely?

No. Bursty workloads, multi-region services and software consumed as a service usually stay. The data center connects to what remains over private cloud on-ramps where the facility offers them.

Who owns and maintains the hardware after the move?

Either you own it outright, with Telnetrix sourcing, installing and warranting it, or Telnetrix supplies it within a monthly fee. In both cases Telnetrix patches, monitors and backs it up and provides remote hands.

Do we lose elasticity by self-hosting?

For steady workloads, the cloud's elasticity was being paid for and not used. We design headroom into the footprint, add space as you grow, and keep burst capacity in the cloud over a private connection where you need it.

Contact Telnetrix

Send us a recent cloud invoice, or describe what you run. We will come back with the workloads that qualify and what the comparison needs from you.

Opens your email app, addressed to sales@telnetrix.com.