1. 4

Github - link


  2. 1

    Anyone able to compare this against Deis Workflow, Dokku, or some of the other open-source container-based PaaS systems?

    1. 2

      Hey, I’m one of the creators of Flynn.

      Obviously I’m biased, but here’s my take:

      Dokku is architecturally very simple, just a bunch of bash scripts, because it only focuses on single-host use cases.

      Flynn is natively highly available (though you can run it in a single-host configuration) and has a larger technical scope, covering everything from the details of how container are run all the way up to the user interface used to deploy applications. We also run highly available databases within the platform, in addition to stateless webapps. As a result of working to build an easy to use unified solution, we’ve ended up building many components from scratch specifically for Flynn and have very few dependencies.

      Deis is designed to use commonly used off the shelf components, and has a focus on stateless web apps. Currently Deis is built around the Kubernetes and Docker ecosystems.

      Flynn’s approach has given us more flexibility, but it has taken longer, so Deis has often reached various milestones faster.

      It’s a frequently asked question so hopefully in the future a well-informed user that has experience with various platforms can write a detailed teardown/comparison.