In this talk we'll look at how Cockpit is designed. It's zero footprint and starts on demand, without a heavy backend, but just enough server-side logic to let a browser talk directly with system APIs. This also means that admins are not limited to Cockpit, but can use other tools, or the terminal, along side it.

Cockpit interacts heavily with all corners of the system. Because of that we rely heavily on continuous integration. In this talk we'll show how the Cockpit project boots and tests real operating systems many thousands of times a day, and does continuous delivery into distros as well.