[sjagoe]

I would say it's less about the compute resources, and more about possibly needing a team dedicated to maintaining quite a lot of infrastructure to replace the features that GitHub has, which is far more extensive than just git hosting.

[turbinerneiter]

GitLab, Gitea or others provide most, if not all, and in some cases even more features than GitHub. Theiy are fully or partially Open Source and they are easy to host.

You need to compare the cost of self-hosting to the cost of SaaS - INCLUDING the risk of getting locked out.

One downside of the SaaS model is that you are just a very small customer in the bigger scheme and they can't really justify spending money on servicing you. Let's say you are company of 5 people, paying 50 bucks a month for a service - how many hours per year can they spend on servicing you before you become a net-negative account? You much power do you have in a negotiation if you are a net-negative account?

[vinay427]

> Let's say you are company of 5 people, paying 50 bucks a month for a service - how many hours per year can they spend on servicing you before you become a net-negative account?

It probably isn't sustainable for a business to only consider this aspect. One thing that comes to mind with companies that thrive with a large number of small non-B2B customers, who individually don't tend to have much power, is that they understand that people love to talk about customer service when it's bad, and occasionally when it's very good as well. Word spreads, and nearly everyone places at least a little weight on this public perception of kindness or flexibility with customers especially when it isn't in the immediate financial interest of the company to do so.

[kavalg]

WRT self hosting, GitLab could be painful, but Gitea is really easy to host and keep up to date.

[risyachka]

I've been self-hosting gitlab for few years now in my company and never had a problem.

[sitkack]

You should clone your environment and then inject faults into the clone to cause yourself some simulated problems.

[kavalg]

How much resources does that consume (both compute and human)? Have you done upgrades?

[denton-scratch]

It's perfectly possible for a team of 10 devs to run on self-hosted source-code control, run an in-house CI system, and run application hosting, with just one tech (and one backup) working part-time on maintaining the system. You need a VM host for the CI; now you have a VM host, you can build git servers and so on (bring the email inhouse, perhaps?).

As far as maintaining the system is concerned: setups that are hosted by 3rd-parties also need maintenance. Someone has to understand how it all fits together, and how to fix it when it goes wrong. So you still need a team-member working part-time on SCC, CI and deployment.

[wolco2]

If you have developers that can use git they can setup and maintain a local git or source control.

If no one in your company can do that.. hire or outsource.

[chillfox]

Maintaining a self hosted solution like GilLab takes less than a day of work a year, and it has more features than GitHub.

(I have been doing it for years)