This might be the second time I've said this in two days but... So it's a git post-receive hook that parses a YML and starts your app? In all seriousness thou

This might be the second time I've said this in two days but... So it's a git post-receive hook that parses a YML and starts your app? In all seriousness though there have been a lot of businesses that are evolving out of this relatively easy to do push-to-deploy mentality. The ability spin up new servers on demand is kind of nice but ultimately doesn't save me much in the way of overhead when I can already set up a new AMI with the push-to-deploy mechanisms already built into it with just a few clicks. Why should I use your product when I can set up the same thing manually in under 10 minutes? I applaud your effort and I also think you've done a bang up job at packaging it and I really like that you support so many hosting environments (that is your key differentiator here) but I hate to see too many people dump a lot of time into heroku-style deployments. This was a solved problem even before heroku came around and it seems many of these new variations are just saturating the market which drives down the value. Although having said that, I'll be honest, I'm very jaded on this topic. Also I'm not your target customer at the end of the day because I have a decent understanding of how this works behind the scenes having built similar deployment mechanisms into just about every project I've worked on in the last 4 years manually. My advice is that you need to differentiate yourself with up front feature based value. Your compatibility with many hosting providers is a really nice feature, but all it gives me up front is the confidence to know I can move to a cheaper competitor if I don't like how it's going. Focus on some upfront feature based value differentials and I think you'll do pretty well in this market if you focus on private enterprise.