I don't mean to be negative, but that's probably because it's pretty much the same thing. Codefloe is tiny. Some quick counting shows it has a grand total of 1012 registered users, including bots, and 1416 public repositories of which the top 3 with the most stars (I know this is a mostly meaningless metric, but for scale) have 27, 13, and 8. It's too small to run into scaling issues.

How does someplace like a GitHub/Gitlab go it? Are user accounts or repos sharded across different servers? Is there a different underlying scaling system? If one wanted to run Forgejo “at scale” what would it really require, or does this need to be factored into the design from day one?

Here's GitHub's policy:

> We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement.

https://docs.github.com/en/site-policy/github-terms/github-t...

Here's Atlassian's policy for BitBucket:

> 14. Limitations of Liability

> 14.1. Damages Waiver. Except for Excluded Claims or Special Claims, to the maximum extent permitted by Law, neither party will have any liability arising out of or related to this Agreement for any loss of use, lost data, lost profits, interruption of business or any indirect, special, incidental, reliance or consequential damages of any kind, even if informed of their possibility in advance.

https://www.atlassian.com/legal/atlassian-customer-agreement...

I also swear I've read that same "buy a hetzener dedi install forgejo" etc etc line before, but maybe it's just you're not the only person cynical about the situation.