*Stupid question*: What is so hard about self hosting one's own repo? I get it must be difficult for a mega corporation, but for companies like us, who have hundreds of repos but only 20 of them are regularly used, and concurrent read/write is relatively light -- considering our largest team is less than 20 persons, so even if all of them are reading/writing from the repo, it doesn't seem to be a huge issue.
Even for a bigger company, say 5x developers (we have about 100+ SWEs and maybe 10-20 other titles who use GitHub), is it really a big thing to self host their own repos? External applications are definitely on another level because you could have hundreds of concurrent visits easily.
> What is so hard about self hosting one's own repo?
Maybe nothing! I was genuinely asking. I still don't know what Actually Good™ forges are out there these days, generally suitable for corporate use in place of the likes of GitHub or GitLab. Forgejo? Something not based on Git?
I guess self-hosting GitHub is the easiest second step for companies that use GitHub? It does have a lot of niceties built around git, which is very crude.
Even for a bigger company, say 5x developers (we have about 100+ SWEs and maybe 10-20 other titles who use GitHub), is it really a big thing to self host their own repos? External applications are definitely on another level because you could have hundreds of concurrent visits easily.
What did I miss?