[boulos]

Having done this for friends and others in the past, you'll want to be cognizant of how to leave the nonprofit with something they can update. CMSes like Wordpress are okay, but come with pretty high "update pain" if you tell them "I'll just install this on a Digital Ocean droplet for you". While this is less true now that WordPress has auto updates, you've still got the security hassle of needing to update the Linux box (and the occasional "hey the server is dead").

If you can swing it, most nonprofits could get by with a simple App Engine based app and never have enough traffic to go beyond the free tier. There's at least no OS updates.

If the nonprofit just needs a static site though, something like hosting it on Github Pages, S3, or GCS is even better. But, again, then they can't update the content of they're not familiar with how to have done this themselves in the first place.

Disclaimer: I work for Google on Compute Engine (not App Engine).

[grimmfang]

Thanks boules, I will probably stick with static pages as I don't mind doing a little bit of maintenance in the future. I did actually consider something like compute engine, Firebase, or maybe Heroku.