No matter what your product anticipates, it doesn't anticipate all the things I do, in fairly boring applications. I compile my own Python. I install postfix for some applications. I install a kernel module that increases the Linux entropy pool. You have not anticipated my set of problems.
What this means is that no matter how much great stuff your product brings to the table, I bring just as much, if not more, configuring your product and designing a deployment solution around it for my application.
If your product isn't open-source, that's a non-starter for me. Because now I'm worried that I could spend a lot of time configuring the product, and not being able to add that one feature that I need. I'm not sure if you can run a business with an open-source deployment product, but I know that I won't ever use a closed-source one.
Do a better job of explaining how these apps run. I took a look at your sample manifest files, and it wasn't clear to me if you are installing nginx or something? Or if you intend the apps to be daemon-like? So create a page that explains, in words, how to deploy a daemon-like app and how to deploy a webapp, and who is responsible for installing the web server and editing its configuration file(s) (do you clobber them?) and what web server it is supposed to be.
Finally, add a docker.io example. It's not production ready, but it looks like it's designed for people like me who have deployments involving heterogeneous payloads. I'm going to move to it eventually, so if I was to switch deployment stacks I would want good support for it.