But it is interesting to see straight hardware-hosting deals get so commoditized that the relationship, not the machine, is available on a deal-a-day site.
It shows how far downmarket even sophisticated IT operations have come. It used to be you used a hosting service so you didn't have to live with your own mainframe or the Cobol trolls who tended it with their evil magic and protected its unnatural life from any touch of the Sun or a client/server interface.
You can rent an obsolete server and have someone else take care of it; you can rent a chunk of Azure and run .NET apps on machines you don't own; you can lease micro-instances, storage blocks, I/O units and CPU cycles on EC2 and run a tiny data center on machines that, again, you don't own.
Capital expense? Save that budget for lunch with the CIO. Other than software -- which does what it wants, no matter what you or the programmers say about it -- and lusers, the biggest headache for IT is always getting the hardware to behave the way it's supposed to and not crash when you look at it twice. That's why network managers leave even the most fubared LAN plans in place because the rule is: if it's working, don't touch it.
In someone else's house you never have to touch it. You'll only be there to work with the software and mess with the lusers. Unless they cloudify that, too.
Then you won't have to bother fixing anything more complicated than TV and the remote control. Because if lusers can rent all the computing functions they need, why do they need you?