What self-hosting actually costs is metal plus backups plus loaded hours. Flexera 2025: 27 percent of IaaS and PaaS spend wasted. A $49 VPS with unpaid nights is a different bill, not a cheaper one.
What self-hosting actually costs is hardware plus backups plus the loaded hours of the person who patches, watches, and restores. Flexera's 2025 State of the Cloud Report estimated 27 percent of IaaS and PaaS spend as waste. A $49 VPS with unpaid nights is not a savings against that number. It is a different bill with a different name.
I am Amelia S. Gagne, CEO of Kief Studio. We self-host because we want the stack, the logs, and the restore drill on infrastructure we operate. This URL owns TCO. The product-choice essay is self-hosted vs cloud: the real tradeoffs.
Flexera's 2025 cloud survey still put wasted IaaS and PaaS near 27 percent. Self-hosting only wins if your labor plus metal is lower than the used portion of cloud, not the list price.
What does self-hosting actually cost?
Write four lines: compute and disk, network and DNS, backup storage that is not on the same box, and labor. Labor is the large one for a small team. A senior engineer at a fully loaded $150,000 who spends a quarter of their time on one platform is $37,500 a year before you buy a drive. That arithmetic is boring on purpose. Brochure TCO skips it.
Uptime Institute's 2024 Global Data Center Survey found 55 percent of IT workloads already off-premises, with respondents forecasting 58 percent by 2026. Hybrid is the default. Self-hosting a slice of that mix is a choice about which slice you want to operate, not a religion about all compute.
Uptime Institute's 2024 survey put 55 percent of workloads off-premises. The TCO question is which remaining 45 percent you can staff without turning nights into unpaid ops.
The invoice lie, in both directions
Cloud invoices hide labor inside a premium. Self-hosting invoices hide labor in your calendar. Flexera's 2026 State of the Cloud summary put wasted IaaS and PaaS back up to 29 percent after years of decline. Waste is not an argument against cloud. It is an argument against paying for unused capacity, wherever it lives.
A cheap VPS looks like a win against a $2,000 managed plan until you add patch windows, restore tests, certificate renewal, and the first disk that dies on a Saturday. Count hours at loaded cost. If you would not hire a person to do that work, you are volunteering.
The other lie is that self-hosting is always more expensive. At enough volume, reserved hardware plus a team you already pay can undercut per-unit SaaS. That is a spreadsheet with real utilization, not a tweet. Sticker price versus TCO is the same discipline for a CRM as for a rack.
A TCO table you can copy
Line
Self-hosted
Managed / cloud
Compute and disk
VPS, colo, or metal you can name
Instance and storage SKUs
Backup
Second location, tested restore
Snapshots plus export you have rehearsed
Labor
Patch, monitor, incident, docs
Ticket time plus your still-needed app work
Idle capacity
A box you bought too large
Flexera-style wasted IaaS / SaaS
Fill the cells with last quarter's numbers. If you cannot fill labor, you do not have TCO. You have a hope. The endowment effect is why teams defend the box they already love. Price it anyway.
A restore you have not run is not a backup. Put a quarterly restore drill on the labor line. That hour is cheaper than discovering the archive is empty.
When self-hosting is the cheaper honest answer
You already have someone who can operate the stack, and their calendar has room. Data residency or client contracts want a street address you can name. Utilization is high enough that the hourly labor amortizes. Those three together beat a managed SKU. One of them alone usually does not.
Owning the stack for client data is a jurisdiction and access story. Cost is this page. Do not mix them into one slogan. A cheap host in the wrong place fails the first story. An expensive host you cannot restore fails both.
Kief Studio's public work on kief.dev and managed ops at ltfi.ai is us taking the labor line onto our books. That is a product. It is not proof that your intern should run Kubernetes at 1am.
A 90-day check before you migrate either way
Log operator hours for the current platform for four weeks. Include evenings.
Price those hours at loaded cost. Add invoices. That is today's TCO.
Price the alternative the same way, including dual-run months.
Run one restore on the system you trust more. Time it. Put that time in the table.
If the alternative wins by a thin margin, stay. Migration has a failure rate the steady state does not. If it wins by a wide margin and you can staff the labor line, move. The case for self-hosted infrastructure is the "why we do it" sibling. This page is the bill.
A worked example at small-team rates
Suppose the VPS is $49 a month ($588 a year), object backup is $20 a month, and you spend six hours a month on updates, alerts, and a quarterly restore. At $100 loaded per hour, labor is $7,200 a year. TCO is about $8,000. A managed plan at $250 a month is $3,000 plus maybe two hours a month of your time ($2,400). That managed TCO is about $5,400. The VPS lost. Raise utilization, or drop your hours, before you call the VPS cheaper.
Flip the numbers. Ten busy sites on one box you already know, two hours a month, backups you already pay for: the same $588 plus $2,400 labor is $3,000. Managed per site would stack. Self-hosting wins because the labor amortizes. That is the whole trick. There is no universal winner. CISA's Secure by Design program is about how the software is built. Your TCO is about who operates it after it is built.
Write the example with your rate, not mine. If you do not know your loaded rate, use salary times 1.3 and move on. Precision theater is how these comparisons die in committee.
If you would not hire a person to do the night work, do not treat unpaid nights as a self-hosting discount. That is how a $49 VPS becomes the expensive option.
Only if labor plus metal plus backup is lower than the used portion of the cloud bill. Flexera's 27 percent wasted IaaS and PaaS in 2025 is unused cloud, not a reason to ignore your own hours.
What is the biggest line in what self-hosting actually costs?
For a small team, operator time. Hardware is visible. Patching, monitoring, and restore drills are the line that decides the spreadsheet.
Does hybrid change the TCO math?
Yes. Uptime Institute's 2024 survey had 55 percent of workloads off-premises. Price each slice. Self-host the slice you can staff. Leave the rest where the labor is already paid.
Should I move off a $49 VPS?
Not automatically. Add your hours. If the hours are real and you already have the skill, keep it. If the hours are fictional, you are subsidizing the invoice with sleep.
Customer acquisition costs have risen 222% in eight years. Free developer tools cut through that math by letting the work speak before the sales conversation starts. The tool is the proof. The proof is the pitch.
Non-compliance costs $14.82 million on average versus $5.47 million to maintain compliance, a 2.71x gap. Compliance engineering means building systems where evidence generates itself, not assembling it from memory before each audit.
Over 92% of the Western world's data sits on U.S.-owned servers, and the CLOUD Act lets authorities demand access regardless of location. Owning the stack is not ideological. It is jurisdictional, operational, and the difference between answering 'where is the data' with a street address or a vendor FAQ.