We don't do horizontal scaling, correct. We have some great advantages of not doing that. We isolate your project, and give it as many resources as it needs.

The largest instance we can put you on is equivalent to 100 Heroku dynamos for instance. And we plan on growing that farther.

I have a blog on a popular host, and when I got hit by Hacker News my server fell over. Doing so caused me to lose a lot of the reads and garner plenty of complaints from here. It can be a total pain, and every time my posts appear on HN, I get scared inside if the project isn't on HN.

As for simplicity; it's not just the filesystem. The panel itself is easy to use, and we're continually adding more relevant features to help people just focus on staying in flow and working on their code.

If we can save devs any time, we've won. And I think we save them a lot of time.

There's a wide variety of skills and wants from developers. The fact is; we have a user base of developers who do want us. And I personally, as a developer want us.

We have git automated deployment being released this week. And if your database is 2TBs, you want an Enterprise Solution.

You can currently snapshot your projects, in the same manner we do for failovers.

But we'll definitely keep your opinion in mind, thank you.

I saw this. I have a lot of respect for Githubbers and Github but is Node really the language for a text editor? My text editor that's built natively to my OS often struggles, let alone if it's Node. Seems like they're shoehorning the wrong technology.

This was a worry to us. It'd be a big detriment to us if that happened. We're trying to keep the user the priority, rather than nasty captchas. So we've got our own implementations. The moment we see bots, we'll switch our strategy. :)

It's actually not. People click a tweet button, then review and post their tweet. :)

It's not a feature implemented yet, but we're going to add it. We need to adapt it to our architecture and make it scalable.

Many websites. I use it for me and my clients too. :) Which works out really nicely.

Just a personal website would probably fit nicely into the Free plan :)

Or I could host it in S3 for ~$15/year.

Sure, you could. But there's a ton of differences as you can see. It depends if you want automatic vs manual. And if you got the time to do manual, then I get that. But it's all about saving the users time, so they can focus on the core parts.

Dropbox could all be hosted on S3, but the ease is worth it. Etc.

We'll add it to our requests list but no ETA as of yet! :)

There's two reasons: 1) Ease 2) Tech

Our ease is worth it. If you save 1 hour of work, you've made your money back — and probably have even more. And honestly; not everyone has the skills to build stuff on Linode. Quite often they want to focus on just working on the client's website.

Our tech is very impressive. We've got a great development team working hard on building a very robust system. Using us you'd find that.

I can understand what you're saying though. But I can guarantee we're a different experience and result than plain old AWS or a blank Linode box.

Appreciate the response. Certainly going to give it a go. I tweeted, but could you point me in the direction of your definition of a request?

Our request model is http requests. I'll try and make that clearer on the homepage.

Under pricing, it says '10 million visitors' in the copy. There's quite a difference between 10 million requests and 10 million visitors.

Thanks for that spot. We had our metrics labelled as visitors but felt it was too confusing. It's definitely requests. Will change it :)

Right now, a badge. We're contemplating what exactly to give. I suspect there'll be discounts and special rewards in the future though.

A startups life is really given life by the early adopters. And we think we should recognise those people for believing in us :) Hopefully we can in this way.