I've fallen into this same classic startup conundrum where I've justified over-complexity for future-proofing. If this project was architected in a way where you were cash positive every month 2k then I could see this rationale. There is a very slipper slope, one that I've fallen into many times.
I'm not sure what your future plans are, but at current state this could be static and cost you next to nothing to host.
One quick patch could be that you use a CDN to cache your assets. cloudflare.com is pretty good and very simple to use. The content isn't changing so you could set long TTL's which would reduce some load on your servers.
I've fallen into this same classic startup conundrum where I've justified over-complexity for future-proofing. If this project was architected in a way where you were cash positive every month 2k then I could see this rationale. There is a very slipper slope, one that I've fallen into many times.
I'm not sure what your future plans are, but at current state this could be static and cost you next to nothing to host.
One quick patch could be that you use a CDN to cache your assets. cloudflare.com is pretty good and very simple to use. The content isn't changing so you could set long TTL's which would reduce some load on your servers.