Supergiant.io

@jezell thanks for bringing up the 404. First day launch problems :-). To answer your question, we wanted to managing stateful, distributed apps easier to manage out of the box. You can manage dockerized applications like one giant computer, and FINALLY make DevOps an afterthought.

@jezell Thanks. Following up Mark. We evaluated every container platform we could get our hands on, and we found Kubernetes solved a lot of problems for us; however, it's very hard to use Kubernetes to host distributed stateful database services on first blush. In fact, the Kubernetes documentation idealizes statelessness, which initially made it a hard case for us. So 1) we created our own product that makes it simple to set up Kubernetes, 2) we tackled the concerns you run into with databases: load balancing, clustering, volume management, etc., and 3) we made it easy to install, approach, and run on minimal hardware. The CLI can even be used to setup and manage Kubernetes clusters for you, even if you have no intention of using the Supergiant Dashboard or API. Of course, once Supergiant is running, if you still want to reach your Kubernetes cluster within Supergiant, you can. We don't obscure it after installation at all.