Good questions both. We make money by offering support and services for Pachyderm. This includes a couple of things. Implementation services in which we help p

Good questions both. We make money by offering support and services for Pachyderm. This includes a couple of things. Implementation services in which we help people setup a working Pachyderm cluster on their own infrastructure, help train their engineers on how to use the system and establish a plan for getting the company's data and analysis running on the new system. Support, where we help people with any issues that arise using the system. And consulting, where we get a lot more involved and help people actually build things on top of Pachyderm that their company needs. If you're interested in these services feel free to drop me a line at jdoliner@pachyderm.io We totally agree that containers aren't a suitable interface for everyone. We see containers as the ideal interface for developers. Over time we're expecting developers to build simpler interfaces on top of it. We'll also be building a lot of those ourselves. For example one feature we have on our near term roadmap is a SQL layer. We're going to implement that in terms of our container API which means that it should be very possible for a developer to implement a totally new access pattern just by throwing some code in a container.