>I don't want to be bothered with installing various scripts, running through a UI whenever I want to upload a file or a new post in my blog/site, and I'd prefer to simply manage my site as if it was a local file system, no databases (well, maybe a little SQLite), a basic caching system (after parsing the files, we want to store them in some form that will not rape the server every time a new visitor arrives), and something that can be easily extendable.<p>You're going to fall between two stools. If you want something to be extendable, people are going to have to have a way to install their extension scripts; if you don't give them a way to do it, they'll copy and paste with all the problems that entails. "manage my site as if it was a local file system" is unpleasant for anything but the simplest of sites; usually you'll want to test locally before deploying, and restore changes from history - at which point, heroku is about as simple as possible.<p>Either make a super-simple system - no extensibility, no caching, no sqlite - or make something that can compete with heroku.