Secondly, alot of your pricing package details are in very small fractions of GB. It would be easier for people to make comparisons, and thus realise you may be cheaper, if you used megabytes instead, no?
At first, we are in the process of refine the phrases on the Web with some native English speakers, and will clarify the description soon.
Second, we just use GB instead of MB because we will increase the free quota in future. Current quota is for temporal use to avoid paying too much unexpected infrastructure cost.
Thanks for your advice.
Otherwise, looks pretty damn cool. Definitely will watch this :)
edit: also, under that header, "applicatoins" in the second bullet
It may be the different issue, but some node hackers may disagree to use Node.js with Apache + FastCGI. However, it is our challenge to make the node technology available not only to geeks but also to light users who will take advantage of server side javascript.
We'll improve the performance and I welcome any advices!
Also, if you are using small or micro instances, you probably don't want to do that either. Don't use anything less than a large instance if you want even semi-decent performance.
Now you can install various popular applications with one-click. These applicatoins include Rails, Node.js, Coffee script, Django, Catalyst, Mojolicious, Lokka, Haskell and so on. Because we use GitHub on its backend, you can access to the source code easily, and fork it to start developing your original applications.
On ther other hand, if you have an existing repository on GitHub, you can automate the deployment process by specifying the reposity in a form on fluxflex.
As the result of these collaborations, I believe web applications development will become more pleasant.