> I help progressive nonprofits with their tech for a living
This is the primary perspective behind this post, and that's going to look much much different than the devops roles a lot of us have.
> Too many apps need a database, a cache, a background worker, a reverse proxy and a long config file before you see a login screen
These apps need a database/cache/proxy/config because creating a fault-tolerant, performant, flexible system needs these things. The author wants everything to be a single binary running on a $5-a-month server. A lot of these open source tools could be updated to run in this mode, but that's not the configuration that's sustainable when there's a disaster.
You need to look at why these nonprofits are using open source projects in the first place. They probably want something free, and they probably want something with clear documentation. Maybe it's something that they're already used to. I would argue that AI-assisted (or vibe-coded) apps are cheap enough to fill this niche. Documentation is less important if the features of the app are much more narrowly-scoped. If they're already used to another app, then the vibe-coded one could be designed to provide a similar experience.
I've worked with non-profits that have struggled under the weight of the software they're using. Most often the problem is the software being too general in a way that doesn't model the domain well. Cheap custom software would help a great deal.