Maybe you could be a little more clear on what you need, because it's hard to imagine what are your requirements that fall in-between of "Google App engine is too limited" and "Amazon is too expensive"?
Also the phrase "I'm not much of an admin" makes it all sound really confusing... Rarely the cloud is the solution for one person's needs. Typically something like dedicated server or vps should be the answer. VPSes can be 6$/m including server's control panel so that you dont have to be "an admin".
Those are usually shared once, aren't they?
(1) ...except for the provider, but even Amazon has access to your files on EC2... (Tin-foil hat time.)
Cloudkick should support this provider.
Lock-in is bad for customers; long-term, lock-in can kill industries.
Pre-installed FreeBSD OS will not occupy your VDS disk space. Our experts will update all the pre-installed software regulary.
Pre-installed Linux OS takes up disk space allocated to your VDS. And we will not update the software - you will have to do it yourself.Xen, VMWare and Parallels are all examples of para-virtualisation, where multiple OS's share the underlying hardware, but have their own resource limits in terms of disk and memory access. And the hypervisor exists to manage the timesharing and access control, but the guest OS's are executing directly on the hardware.
From a hosting company point of view, jails on a BSD system are the most tractable and resource efficient, followed closely by any of the paravirtualisation solutions. UML as a hosting solution is kind of cheesy (it's great for networking simulations though). From a customer standpoint, a paravirtualisation solution offers more flexibility and power.
On xen, I don't have to worry about runaway user processes. Xen deals with the problem for me. this was not the case with Jails.
So yeah. I like Jails for cooperative environments, but there is a reason why I'm selling Xen VPSs now, not FreeBSD jails, and it's not 'cause I like linux more than FreeBSD.
or, you can pick something on http://www.lowendbox.com/, but be careful - their primary concern is price i.e. they list hosting services that are cheap, but not all of them are reliable.
I don't have a scaling problem atm, but if publishing things to the cloud is easier than going the traditional "set up a server" route, I thought it might be worthwhile to use "clouds" from the beginning (also to feel safe about potential traffic spikes). For example, using Heroku recently was pure bliss, because I really don't want to bother with configuring web servers, databases, firewalls, backups and so on for each of my projects. I would probably manage somehow, but admin stuff is not my main skill. Unfortunately Heroku does not do everything I need in other projects (ie more frequent cron jobs, other tech than Rails).
I suppose having a virtual image for every project would be perfect.
Edit: Re "Amazon is expensive": my projects don't earn money yet, so I am trying to save. My existing root server costs 20€/month, I think Amazon would cost quite a bit more, so it feels expensive. But of course my root server is old and can not handle much more modern stuff atm.
1. The "really?" set of questions: Is the cloud what you really need? If so, can you architect your system to exploit the advantages of the cloud?
2. The "how?" set of questions: do you outsource the cloud to AWS et al or do you build your own? The details of this are probably worth half a book, but there are many databases to choose from (CouchDB, MemcacheDB, Tokyo Products and LightCloud, thrudb, Project Voldemort, redis, and others) and build-or-manage-your-own cloud computing datacenter (EUCALYPTUS, AppScale, Enomaly, ELASTRA, 3tera, etc).
The answer to these questions starts with "what are you trying to do?" In many cases, the cheapest and fastest way to get going is to provision some virtual servers from Linode or Slicehost and have a go. If you grow too much, 1. congratulations and 2. look at the cloud options.
EDIT: I forgot about Linode since I haven't used them myself. Here's a comparison between the two from last November: http://journal.dedasys.com/2008/11/24/slicehost-vs-linode
You can learn more here: http://allmydata.org/~warner/pycon-tahoe.html You can download it here: http://allmydata.org/trac/tahoe
EDIT: How do I create proper hyperlinks?
Explain a bit what your app is and we can give your architecture advice.
You may not be ready to move production to the cloud but there is an opportunity for you to improve your development process.
Anyway, it depends on the specific AWS service.