gabrtv is correct that Flynn is built on a scheduling framework (think Mesos, but based on the Omega paper), which allows us to support running stateful service

gabrtv is correct that Flynn is built on a scheduling framework (think Mesos, but based on the Omega paper), which allows us to support running stateful services (like databases) inside of the platform. Flynn develops most core technologies internally. We try to minimize our external dependencies, as the majority of instability we've run into has historically come from dependencies. Building modular, reusable, and repurposable components is also a major design goal of ours (for example, Deis uses a few Flynn components).