There's also the dual-licensing model, where non-free licenses can be purchased which allow things that the FOSS license doesn't, like non/partial-contribution. AGPL seems even better suited to this than GPL, precisely because many companies would rather purchase such a license than expose the custom elements of their network services. IIRC that's precisely why Affero came up with this license for their software (in collaboration with the FSF, to ensure GPL compatability).
In other words, the risk is closer to the risk of a side project failing than the risk of a giant corporation failing, and the need for flexibility to pivot to different funding models is lower or nonexistent. There's no venture capitalists to appease.
Presumably, if the founder decided he could only profitably run sr.ht by turning it into "open core" like gitlab or proprietary like github, he would have simply given up the project.
Say for example GitLab was AGPL, their model of having a Community Edition and an Enterprise Edition would no longer be possible, because the EE directly links to and consumes software from the CE code.
Having a EE and CE version of a product is one of the few remaining models that still enable fruitful enterprise and FOSS combinations. The support-only or maintenance-only models are very rarely successful. The former isn't possible with the AGPL and the latter is, but is simply bound to so much risk and so few successes that it's basically bleeding to death or an existing enterprise, with nothing in between.