Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our company has several clients that run Wordpress blogs. Being that it's a small company, we (IT) are usually tasked with setting it up. Because our clients are typically not willing or able to maintain a VPS, shared hosting account, or dedicated box, we end up recommending they start a blog at Then, six months down the line they change their mind and decide they want this plugin or that theme, and we end up migrating their blog to a shared hosting account.

What we'd like is a (paid) provider that will offer just what offers, but with full access to Wordpress as though we were hosting it ourselves. Our clients should not have to ssh to the box, or update wordpress themselves, that should all be taken care of. FTP would be necessary to upload themes or plugins on occasion, but all maintenance should be taken care of.

Does anyone know of such a provider?

share|improve this question
up vote 0 down vote accepted

This can be done by having a box. Why don't you try amazon EC2 (Amazon Cloud), where you can have an instance of your own and decide on what to do with it.

share|improve this answer

You could also take a look at WordPress MU (same software that runs

This would likely give you the same environment your clients are currently used to, and if you combined this with EC2 or some similar service (Slicehost or RackSpace Cloud... they're all great), you can grant them the access to customize at the same time since you'll have full control of the hosting server(s).

share|improve this answer

What I do for my clients is fairly straight forward.

  1. I provision physical machines from OVH, because I can get them "spun" up rapidly, usually in a few minutes.
  2. Allocate a separate IP for either the client or client projects, as sometimes one client might like to have a separate IP for each project.
  3. Slice the machine up using LXC containers, so each container runs at machine speed.

This allows many different versions of Linux to be run on a one machine without the headache of running a heavy weight VM like VirtualBox.

Some of the $100/month machines I'm hosting client sites on are averaging 100,000+ uniques/hour (you read that right) + machine load runs around 5% of total CPUs.

If you take this approach you can run many sites on one low cost physical machine.

And if you'd like to use one single IP, then you can use haproxy to split all sites off one IP + route each request to the correct LXC container.

Caveat: If you use haproxy, you lose the ability to run Apache + mod_h2 for serving fast SSL (HTTP 2.0) sites.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.