Some more details - you'll have the option to have phpVMS ready for install on the server once you get it. You will just have to setup the database and install it. I'm also thinking about making several scripts available to automatically download a fresh copy of phpVMS, and also to update. But these scripts will be available and uploaded to the forums/docs.
In terms of specs - probably about 10gb space and 50gb bandwidth. Those are soft limits - as comparison, vaCentral + phpVMS use about 5gb of space with the near 1 million records in the vaCentral tables, 20gb bandwidth a month -. So for a VA or whatever's hosted, that should be sufficient. But if you need more, it'll be available. I don't want to cram people into servers. phpVMS 2.1 is going to be much more optimized than even it is now, so it's impact to a web-server will be minimal. It is a 16-core server I believe, with 12gb of RAM. I've been watching the load on the server for several days now, and it's been near zero.
It will be cPanel, with SSH access. Not sure about git yet, working out something with the host, though in the end, there may not be support for it. No biggie, I'm not sure how many people in the end will use it. There will still be those scripts available. I believe it's reliable enough that I will also be setting up a mirror for the API server there. I've worked out pricing to be about $10 a month, and I'll include the nav data updates for free.
I think it might be at least a week or two till it's up. A few infrastructure things need to finish before then. It will be based off of fivedev.net, and possible a nameserver mirror at fscentral.net. Though I haven't quite decided to make it fscentral.net completely.