> Doesn't it cause more headaches? No. You update it on patch day (or when a big CVE comes out that you are actually impacted by) and know exactly what goes wr

> Doesn't it cause more headaches? No. You update it on patch day (or when a big CVE comes out that you are actually impacted by) and know exactly what goes wrong and when. If you can't solve it, you roll back. When Github (or a part of it) goes down, you know nothing and with persistent issues there's no way to solve it either. A company of the size where "but we have to scale" is an actual issue should self-host. A SaaS solution is a risk that you cannot mitigate.