While I'm pretty sure that it can run on a small budget, I'm less sure that the owners have the time to maintain the site (a static website still needs to update the server, domain and certificates and while this can be automated to a degree it's still a lot a work).
If they are static sites and mostly text, they could be hosted directly out of freaking S3 for a pittance. There is no way a service this niche and this intentionally minimal consumes enough bandwidth to make that painful.
It's called an invitation, just in case anyone who has more info, or the owner, wanted to reach out. If you assumed, apropos of nothing, that's a comment on HN were my only actions on the matter, well, maybe don't do that.
Perhaps in the future be less insulting and make fewer assumptions.
Step one: since all of the pages are single pages accessed by name, the source content is likely a batch of HTML files. So: create an S3 bucket and mass upload everything to the bucket.
Step two: enable public access and hosting on the bucket
Step four (optional): register a domain via Route 53 and create a simple record that points to the bucket so we have a better URL
Making the service writable again is a different story. The technical steps of getting it online be trivial for anybody that could do the above, but dealing with the abuse cases is something else entirely.
