Disclosure: I've been working with Tutum since the initial team.
Tutum was actually a container hosting service at first but we found there were a ton of technical challenges in multi-tenancy with hundreds/thousands of containers and it's hard to build a level of trust that larger IaaS providers have like AWS.
Hosting puts you in direct competition with IaaS providers, while being a middle-man can provide more value-add and you get to work with the other providers to strengthen your solution.
Thanks for the mention! I'm part of the Tutum team, and we actually made an open source project called Boatyard.io
It's basically a web UI that builds images from tarballs, dockerfiles, and github repos. We use it internally all the time and we thought we'd contribute back.
How do you guys feel about the "Container-as-a-Service" providers (Orchard, Stackdock, Tutum) in relation to Elastic Beanstalk for Docker? IMHO AWS's solution appears complex and lacking compared to this: http://ow.ly/w63M6
Tutum was actually a container hosting service at first but we found there were a ton of technical challenges in multi-tenancy with hundreds/thousands of containers and it's hard to build a level of trust that larger IaaS providers have like AWS.
Hosting puts you in direct competition with IaaS providers, while being a middle-man can provide more value-add and you get to work with the other providers to strengthen your solution.